Page 1 of 1

Everest Cache and Memory Benchmark

PostPosted: Mon Jan 21, 2008 11:48 am
by raptorx
How do I get my memory write and copy up to where my memory read score is in Everest?  Here is my last run:

Image

E6850, 9 x 430, DDR2 1032 (5,5,5,15).

Re: Everest Cache and Memory Benchmark

PostPosted: Tue Jan 22, 2008 10:39 am
by raptorx
bump!

Re: Everest Cache and Memory Benchmark

PostPosted: Tue Jan 22, 2008 10:57 am
by NickN
I cant even read that chart the numbers are distorted


What you are asking is how to overclock a specific motherboard and its memory system.

I do not get into those conversations here.

Re: Everest Cache and Memory Benchmark

PostPosted: Tue Jan 22, 2008 9:26 pm
by raptorx
Sorry about the pic.  Put more simply, Why is my "read" score higher then my "write" and "copy" score?

Read is just over 9000Mb/s but the other two are around 7000Mb/s.

I'd just like to understand what is affecting these scores?  What factors influence the "read" score?  And what factors influence the other two?



I cant even read that chart the numbers are distorted


What you are asking is how to overclock a specific motherboard and its memory system.

I do not get into those conversations here.



Re: Everest Cache and Memory Benchmark

PostPosted: Wed Jan 23, 2008 1:38 pm
by NickN
The BIOS settings for the memory, the memory product itself and the motherboard memory controller are what make those numbers, and its not always normal to see equal values


I think mine sits around 11-12K read and 8900-10K write

Those numbers do not fully indicate real world speed although they are an indicator.

here is one I had in my doc from last year (around August) before upgraded the memory on that board

Image

Re: Everest Cache and Memory Benchmark

PostPosted: Wed Jan 23, 2008 8:22 pm
by raptorx
Thanks Nick.  I discovered last night that when I set my Performance Enhance function on my gigabyte P35 board to "turbo" from "standard", all my Everest scores went up, and the write/copy scores got closer to the read score

I'll bet that has something to do with setting different Northbridge latencies with that feature-of course Gigabyte won't elaborate on exactly what it does but that'as what I suspect.

-Jim