Some additional info for this thread

Compromises between timing and clock speed

First of all, FSB or HTT has nothing to do with timing. The timing is for RAM only.


What's the benefit of low timing?
- memory controller can access the RAM chip faster
- It can access small and random data at faster rate.
- Hence, u can feel the responsiveness and smoothness when timing is lowered.

What's the benefit of high bandwidth (high clock speed).
- high bandwidth enabled more data to transfer to and from CPU in 1 second.
- benefit when dealing with big size data.


What software is better for low timing / high bandwidth
- eg. DDR600 at 3-4-4-8.
- The initial response might be a bit slow, due to high timing.
- However, once the RAM is accessed, the high bandwidth allows massive data transfer.
- Programs like Winzip doesnt randomly access the RAM too much.
- So once the RAM is accessed, the memory bandwidth is more important to complete the task quickly.
- Programs like MS words deal with very small piece of data.
- Hence lower timing has better benefit, bcoz it can access the data quickly.


What's the relation between timing and bandwidth

* note: this is js a rough estimation.

- eg. DDR400 2-3-3-7. <-- has CAS latency of 2.
"2" means the delay measured in clock cycles. So, at 200MHz, 2 Hz is wasted to 'wait' for CAS.

- The actual time delay per clock = 1/200MHz = 5 nanosecond (ns). When 2 Hz is wasted, that means the memory controller have to wait 2(5 ns) = 10ns to access the Column (CAS).

- Hence, the time delay is closely related to clock speed.

- Bandwidth also related to clock speed, with the formula (N-bit / 8) x clock speed

- Therefore, time delay is related to bandwidth.

- DDR400 (200MHz) with CL2.0 has the same CAS delay as DDR600 (300MHz) with CL3.0.

calculation:
1/200MHz x 2 = 10ns.
1/300MHz x 3 = 10ns.

you can put the info posted by others in another reserved post, or u can take my info and rephrase it in yr own way


Aikkss, wat a stupid mistake
thanx for the correction.