Is trying to have the lowest and tightest timings better or is having a bigger bandwidth better? I know having lower timings allow the system to perform faster. I read someone's post of loosening the timing which allowed him to raise the speed of the memory to 270 mhz from the stock 200 mhz (or some number like that) which in turned gave him a bigger bandwidth from 4.6 gb/sec to 6.4 gb/sec (or some similar numbers I can't remember now).
That makes sense to me as there will be no bottle necking with the bigger bandwidth. The lower timings makes sense to me as well since it will take less clock cycles to perform a task. I'm sure there's a happy medium somewhere for a setting for the timing and speed to be working at optimum performance. Now comes the thought that the flow of data never uses the full available bandwidth, so the lower timings is in fact more important by cutting down the time it takes to complete a task. Is this statement correct?
If given the choice when overclocking, should you lean more towards trying to raise the speed of the memory as high as possible, or lower and tighten the timings as low as possible?
>:^/
That makes sense to me as there will be no bottle necking with the bigger bandwidth. The lower timings makes sense to me as well since it will take less clock cycles to perform a task. I'm sure there's a happy medium somewhere for a setting for the timing and speed to be working at optimum performance. Now comes the thought that the flow of data never uses the full available bandwidth, so the lower timings is in fact more important by cutting down the time it takes to complete a task. Is this statement correct?
If given the choice when overclocking, should you lean more towards trying to raise the speed of the memory as high as possible, or lower and tighten the timings as low as possible?
>:^/