• We’re currently investigating an issue related to the forum theme and styling that is impacting page layout and visual formatting. The problem has been identified, and we are actively working on a resolution. There is no impact to user data or functionality, this is strictly a front-end display issue. We’ll post an update once the fix has been deployed. Thanks for your patience while we get this sorted.

Why overclock and trade tight memory timings for a higher clock?

Huh? I'm not absolutely certain about what your question is but here it goes. Overclocking will help you out regardless of what you do with your memory unless you severely cripple it. Using a divider can, for the most part, allow you to keep your tight timings even when you overclock so going for a high-clock loose-timings setting on the ram is just a personal preference that some people have (I think it comes from the fact that back before the A64 not having your FSB 1:1 with the ram was horrible, now, since the A64s "FSB" runs at core clock it makes no difference). Bandwidth does help in some instances but having tight timings helps in others. Overall it's better to have high-clocks with tight timings (heh) but this is only achievable on some very high-voltage dimms.
 
I think you understood my question, however I should clarify by saying that I would OC my CPU and then OC my RAM unless for some reason (I really don't know what that would be) I thought it best to stick with the default memory speed and it's lowest timings or forget the timings and go for the roof on a ram overclock.
I suppose the correct benchmark would clear that up.
 
I've always noticed a great increase in performance when on looser timings and higher clock speed, especially with DC projects, but when clocked a little lower with really tight timings overall the system seems snappier. I think it depends on what you're looking for. I can sacrifice 4 seconds on a boot up time for 50 more PPD in a DC project.
 
Back
Top