Jump to content

Cache & Memory Benchmark - different results


Razvan

Recommended Posts

I am encountering this very strange bug. If I use Aida64 Cache&Memory Benchmark in Windows 10 I get a specific Ram benchmark result, let's say 48100 MB/s read / 53600 MB/s write /  47700 MB/s copy and 52 ns latency. However, if I am booting from an USB live Windows 10 CD (WinPE), I am getting drastically better results, such as 55000 MB/s read / 61300 MB/s write / 55000 MB/s copy / 45 ns latency.

I am not changing any bios / RAM XMP / Ram memory timings settings between reboots, only booting from either main Win 10 installation or WinPE 10 live usb.  I am using the same Aida64 version in both cases.

I am scratching my head, what can explain the huge difference between the results? In both cases, cpu usage is idle and no other background programs are running when doing the tests.

Link to comment
Share on other sites

17 hours ago, Razvan said:

I am encountering this very strange bug. If I use Aida64 Cache&Memory Benchmark in Windows 10 I get a specific Ram benchmark result, let's say 48100 MB/s read / 53600 MB/s write /  47700 MB/s copy and 52 ns latency. However, if I am booting from an USB live Windows 10 CD (WinPE), I am getting drastically better results, such as 55000 MB/s read / 61300 MB/s write / 55000 MB/s copy / 45 ns latency.

I am not changing any bios / RAM XMP / Ram memory timings settings between reboots, only booting from either main Win 10 installation or WinPE 10 live usb.  I am using the same Aida64 version in both cases.

I am scratching my head, what can explain the huge difference between the results? In both cases, cpu usage is idle and no other background programs are running when doing the tests.

Memory performance can change (usually, they get worse unfortunately) as you upgrade Windows 10 to a newer build.  I suppose your live CD has an older Windows 10 build than your main Windows 10 installation.

Link to comment
Share on other sites

I have noticed something else, when running Aida64 on WinPE (better results), the northbridge clock is correctly detected as 47x. However, on the main Windows 10 installation (slower results), the northbridge clock is detected as 36x. Could this influence results?

 

 

Link to comment
Share on other sites

On 10/9/2020 at 7:11 PM, Razvan said:

I have noticed something else, when running Aida64 on WinPE (better results), the northbridge clock is correctly detected as 47x. However, on the main Windows 10 installation (slower results), the northbridge clock is detected as 36x. Could this influence results?

No, since it's only an informational value.  Its value doesn't affect how our benchmarks behave or how the result is being calculated or shown.

Link to comment
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.

Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

×
×
  • Create New...