Okay new version is out!
Key features:
- SHA1 & CRC calculation
- Compression ratio estimation (Compression prognosis)
Enjoy!
22CDEA23F5750D26CE45296218A535948D7B4BEC *chk102.zip
Okay new version is out!
Key features:
- SHA1 & CRC calculation
- Compression ratio estimation (Compression prognosis)
Enjoy!
22CDEA23F5750D26CE45296218A535948D7B4BEC *chk102.zip
I have two suggestions:
- make version for Linux
- make OpenCL-accelerated hash computation - Radeons excels at hashing,
or maybe multithreading..would speed up the hole process a lot and the gui is still usable while adding files =)
I like this programThere are some shortcomings though... CHK reads from my disk with only around 10 MB/s (one big file) and uses ~80% of one core, does it do both checksums from one disk read? When I copy that file on the same partition, explorer can do 50 MB/s disk traffic.
Feature request from me: Possibility to change column order, also probably different icon, this one doesn't seem as good as you usually do
EDIT: Clarifications
Last edited by Black_Fox; 24th July 2011 at 14:56.
I am... Black_Fox... my discontinued benchmark
"No one involved in computers would ever say that a certain amount of memory is enough for all time? I keep bumping into that silly quotation attributed to me that says 640K of memory is enough. There's never a citation; the quotation just floats like a rumor, repeated again and again." -- Bill Gates
It does all at one disk read - it read buffer and compute - SHA1, CRC and compression estimation at the same time. All that computations need some time - so it can't get full I/O speed.
That's good to hear, however why isn't even one full core of quad-core used then?
I am... Black_Fox... my discontinued benchmark
"No one involved in computers would ever say that a certain amount of memory is enough for all time? I keep bumping into that silly quotation attributed to me that says 640K of memory is enough. There's never a citation; the quotation just floats like a rumor, repeated again and again." -- Bill Gates
I guess due to memory access. The CRC/SHA1 need a small amount of memory, but my compression estimator uses about 18 MB which is randomly accessed (hash pointed).