• Competitor rules

    Please remember that any mention of competitors, hinting at competitors or offering to provide details of competitors will result in an account suspension. The full rules can be found under the 'Terms and Rules' link in the bottom right corner of your screen. Just don't mention competitors in any way, shape or form and you'll be OK.

Q6600 or E8400?

Associate
Joined
27 Nov 2007
Posts
1,051
Location
Manchester
hi guys

I plan on building a rig in the next week or two and I want it to be as futureproof as possible.

Other components include 2x2gb corsair dominator 1066mhz, Asus P5E, Thermalright Ultra 120 Extreme, OCZ Thermal Paste, Corsair 650W TX.

I will be overclocking also, with the view of going xfire 4870's in the future, thus the PSU and X38 mobo.

To be used mainly for gaming but occasionally picture editing etc. (occasionally)

So, do I go E8400 or Q6600!?

cheers!

mitch
 
No worries :D


I would choose the E8400 there cracking cpus :)

I was all set to but then I started thinking about these games coming out which utilise all core ie. farcry 2 and Alan Wake and I really want this to last as long as possible without having to upgrade again!
 
IMHO there is a good post on games and cores on this thread:

http://forums.overclockers.co.uk/showthread.php?p=12024853#post12024853



Funny how people post things like 'oh, they should start supporting multiple cores in games already'. Unless your workload is quite easily parallisable, and each chunk is distinct and separate from the rest, SMPing code is difficult and would require extensive locking and code alteration. For those of you who aren't computer scientists, locking and synchronisation are expensive operations.

If you take as an example an OS like FreeBSD, at version 4 they were UP (UniProcessor) only. This meant that all the kernel code would run in a single program, and wouldnt take notice of multiple processors, and consequently needed no locking or synchronisation.
FreeBSD 4 could forward around 800k packets per second (pps, a good metric for measuring network/OS performance). From version 5 onwards, they embarked on SMPifying the kernel, they got there finally with a good performing version in version 7.
FreeBSD 7 can forward around 700-750k pps running in UP mode, or about 500k pps running in SMP mode.
Obviously, there are efforts to improve this, but it clearly shows that sometimes, the quickest and simplest way through is top to bottom, one thread. This, coincedentally, happens to be the way us programmers tend to think and program in, which is why most code is written this way.

There are lots of efforts these days, mostly led by Intel and Sun, who coincedentally have released a whole slew of multicore products, to make developer tools and language extensions to encourage MP (google openmp), but that should clearly indicate the breadth of this problem. Games that do take advantage of multicore chips typically do so by offloading as many non core parts of the engine into separate threads, whilst running the main engine in a single thread/process.

(E8400, overclock the crap out of it, enjoy your games)
 
Last edited:
Back
Top Bottom