Quote Originally Posted by Drwho? View Post
I always said that Core 2 Quad does not need much mem Bandwidth, so, on real application, if memory is not important, you will see very little from Mem Bandwidth.
In the mean time, on application like SETI, Rosetta, folding@home, you got to feed 8 threads, the bandwidth will come handy. If you do H264 with profile level 4, you ll go and see 16 frames in both directions, this will get handy too.

Just remember, to keep 8 threads happy, you ll need the bandwidth, it is just a matter of time before the software use it 100%.
I heard people telling me that nobody will use MMX, it was so hard to use ... Today, you can t boot most of the OS without it.

and yes, I am very sure that 3 Dimms goes faster than 2 Dimms. (on mem test) If it does not, the proto is broken
Thanks for the reply.

If I understand correctly, we should all notice the difference between dual and triple channel, but it's very likely that if we use non-multicore applications that the difference will be very small. The bandwidth that is added because of the extra channel is to provide enough bandwidth to fully cover the 8 threads, but is 'overkill' when using in single/dual threaded applications.

Now, that only leaves the everest bandwidth problems. As far as I know, the Lavalys Everest program is quite accurate when it comes to calculating the memory bandwidth and latency, but in tests I've seen the difference still is only 500MB/s:



Maybe this is the problem:

Lavalys Everest 4.60 new features & improvements:

- Asus EPU and Gigabyte DES support
- Enhanced hardware monitoring capabilities
- Optimized benchmarks for Intel Atom and VIA Nano
- Preliminary support for Intel Core i7 and X58
- Support for the latest chipset and graphics technologies



Only two tests actually show the difference between dual and triple channel, which probably is the correct performance scaling.