• 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.

Prescott 2.8 vs. Northwood 2.8 for my application

C

cmetz

Platinum Member
I have a specific application for which I think the Prescott might be the right choice. I know that there's a lot of anti-Prescott sentiment around here, so all I can do is ask that folks refrain from the "Presc0t sux0r" kinds of responses.

My application is mostly I/O. Single-threaded, not much control transfer. It is sensitive to FSB (800FSB = good) and to memory bandwidth. For the latter, I'm thinking that doubling the cache size is a very good thing. I am not overclocking.

Is there a good reason why Northwood would be better than Prescott for this application? I know that for general purpose and esp. games, benchmarks are showing that Northwood beats Prescott clock for clock, but that's not quite what my application's about.
 
for memory intensive applications, my guess would be to stick with the northwood, the slower cache will probably be your bottleneck... but this depends on your application's size... if active code can fit inside the 1MB L2 prescott Cache, but not the 512kB northwood cache, prescott might be right for you... but alas, i am still skeptical.
 
The northwoods shorter pipeline has an advantage in the case of a misprediction. The pipeline is shorter so the penalty isnt nearly as great. Without knowing the exact nature of the application i cant make a valid preidction though, as i can only speculate as to what kind of I/O youre running.
 
How much slower is the cache on the Prescott on a hit? One clock? That could be an interesting trade-off.
 
You must log in or register to reply here.

TRENDING THREADS

Back
Top