• Competitor rules

    Please remember that any mention of competitors, hinting at competitors or offering to provide details of competitors will result in an account suspension. The full rules can be found under the 'Terms and Rules' link in the bottom right corner of your screen. Just don't mention competitors in any way, shape or form and you'll be OK.

New memory benchmark comp (aida64 alternative)

Associate
Joined
15 Jun 2012
Posts
185
1) Download the benchmark here:
MicrobenchmarkGui.zip

2) Extract files to a local directory

3) Run the program (MicrobenchmarkGui.exe):

Rectangle Parallel Font Circle Magenta



4) Disregard SmartScreen filter and run it anyway

Product Azure Rectangle Font Electric blue


5) For bandwidth benchmark, be sure to max out your thread count. Limited to 64 threads, FYI. So for very high core count machines, you will lose some bandwidth potential if you have over 64 threads.

6) The bandwidth number you will be scored on is highlighted below. Please take a snip like this for your submission:

Font Parallel Screenshot Rectangle Number

7) Please also include CPUz screenshots of CPU and memory tabs, like this...
Also include your windows version with your submission, thank you!
Product Rectangle Azure Font Line


8) For latency test do the same. Once again, the result is listed at the very bottom of your result window:
Font Screenshot Parallel Rectangle Software


There will be two leaderboards for this completion. Latency and bandwidth. We can look at L1 L2 and L3 cache numbers later... here is the breakdown:
This is how latency looks for me:

Yellow square is L1
Orange square is L2
Red square is L3

Dark red square is System RAM
1668030445095-png.2581867




Additional reading here:

AMD’s Zen 4, Part 2: Memory Subsystem and Conclusion – Chips and Cheese

Thanks to @domdtxdissar for recommending this one.

Additional reference materials:
Font Rectangle Circle Magenta Number


Font Number Screenshot Document Parallel










Attachments​

 
It crashes and the interface becomes garbled. There are mistakes in the assembly code. QueryPerformanceCounter no longer works in Windows and should be avoided.
L1 latency is easy to measure yet its gone wrong. It should be 5/X ghz ns =~1ns


badmemtest1.jpg

That's because you havn't selected the number of threads in the Mem Bandwidth button before running the Mem Latency. If you do that, it runs fine, with the expected results.
 
Back
Top Bottom