Edit (2012-Oct-31): My latest (and most versatile) test package is 34MB .ZIP file at:
http://www.sanmayce.com/Fastest_Hash/index.html#NightLightSky
For a long time looking on tests I couldn't find some answers to some very basic (but/and important) aspects of CPU/RAM performance.
Here I am talking about hashing performed by a console tool (written in C).
Hashing & Searching are FUNDAMENTAL in computer craft, not knowing some machine capabilities regarding these two aspects is a shame.
For example I have no opportunity to run my tests on some real powerhouse, this limits my quest of writing the fastest hasher (in C) function because i5/i7 have very different behavior (compared to Core 2) when comes to 1/2/4 bytes fetching and utilizing (auto parallel execution) with several hash lines.
You all are welcome to use my latest benchmark at:
http://www.sanmayce.com/Fastest_Hash/index.html#Yoshimitsu
Of course in order to obtain decent results stop all the concurrent processes before running the test.
I am a humble owner of mainstream laptop with Core 2 T7500 2200MHz and DDR2, the results on my machine:

Also I would be glad for some feedback and results on your machines (especially on monsters with 40+GB/s bandwidth).
Edited by Sanmayce - 10/31/12 at 8:22am
http://www.sanmayce.com/Fastest_Hash/index.html#NightLightSky
For a long time looking on tests I couldn't find some answers to some very basic (but/and important) aspects of CPU/RAM performance.
Here I am talking about hashing performed by a console tool (written in C).
Hashing & Searching are FUNDAMENTAL in computer craft, not knowing some machine capabilities regarding these two aspects is a shame.
For example I have no opportunity to run my tests on some real powerhouse, this limits my quest of writing the fastest hasher (in C) function because i5/i7 have very different behavior (compared to Core 2) when comes to 1/2/4 bytes fetching and utilizing (auto parallel execution) with several hash lines.
You all are welcome to use my latest benchmark at:
http://www.sanmayce.com/Fastest_Hash/index.html#Yoshimitsu
Of course in order to obtain decent results stop all the concurrent processes before running the test.
I am a humble owner of mainstream laptop with Core 2 T7500 2200MHz and DDR2, the results on my machine:
Code:
//OS: Windows XP 32bit
//Motherboard Name: Toshiba Satellite L305
//CPU Type: Mobile DualCore Intel Core 2 Duo T7500
//CPU Alias: Merom
//CPU Clock: 2194.7 MHz (original: 2200 MHz)
//CPU Multiplier: 11x
//CPU FSB: 199.5 MHz (original: 200 MHz)
//Memory Bus: 332.5 MHz
//L1 Code Cache: 32 KB per core
//L1 Data Cache: 32 KB per core
//L2 Cache: 4 MB (On-Die, ECC, ASC, Full-Speed)
//Memory Timings: 5-5-5-13 (CL-RCD-RP-RAS)
//Instruction Set: x86, x86-64, MMX, SSE, SSE2, SSE3, SSSE3
//Transistors: 291 million
//Process Technology: 8M, 65 nm, CMOS, Cu, Low-K Inter-Layer, 2nd Gen Strained Si
//Front Side Bus Properties:
// Bus Type: Intel AGTL+
// Bus Width: 64-bit
// Real Clock: 200 MHz (QDR)
// Effective Clock: 800 MHz
// Bandwidth: 6400 MB/s
//Memory Bus Properties:
// Bus Type: Dual DDR2 SDRAM
// Bus Width: 128-bit
// DRAM:FSB Ratio: 10:6
// Real Clock: 333 MHz (DDR)
// Effective Clock: 667 MHz
// Bandwidth: 10667 MB/s
//
//And the results:
//
//Hashing a 64MB block 1024 times i.e. 64GB ...
//FNV1A_Yoshimitsu: (64MB block); 65536MB hashed in 16875 clocks or 3.884MB per clock
//FNV1A_Yorikke: (64MB block); 65536MB hashed in 16782 clocks or 3.905MB per clock
//CRC_SlicingBy8K2: (64MB block); 65536MB hashed in 66390 clocks or 0.987MB per clock
//
//Hashing a 10MB block 8*1024 times ...
//FNV1A_Yoshimitsu: (10MB block); 81920MB hashed in 20610 clocks or 3.975MB per clock
//FNV1A_Yorikke: (10MB block); 81920MB hashed in 20546 clocks or 3.987MB per clock
//CRC_SlicingBy8K2: (10MB block); 81920MB hashed in 82938 clocks or 0.988MB per clock
//
//Hashing a 5MB block 8*1024 times ...
//FNV1A_Yoshimitsu: (5MB block); 40960MB hashed in 9562 clocks or 4.284MB per clock
//FNV1A_Yorikke: (5MB block); 40960MB hashed in 9531 clocks or 4.298MB per clock
//CRC_SlicingBy8K2: (5MB block); 40960MB hashed in 41110 clocks or 0.996MB per clock
//
//Hashing a 2MB block 8*1024 times ...
//FNV1A_Yoshimitsu: (2MB block); 16384MB hashed in 2578 clocks or 6.355MB per clock
//FNV1A_Yorikke: (2MB block); 16384MB hashed in 2657 clocks or 6.166MB per clock
//CRC_SlicingBy8K2: (2MB block); 16384MB hashed in 16156 clocks or 1.014MB per clock
//
//Hashing a 16KB block 1024*1024 times ...
//FNV1A_Yoshimitsu: (16KB block); 16384MB hashed in 2437 clocks or 6.723MB per clock
//FNV1A_Yorikke: (16KB block); 16384MB hashed in 2547 clocks or 6.433MB per clock
//CRC_SlicingBy8K2: (16KB block); 16384MB hashed in 16078 clocks or 1.019MB per clock
Also I would be glad for some feedback and results on your machines (especially on monsters with 40+GB/s bandwidth).
Edited by Sanmayce - 10/31/12 at 8:22am














