On the other hand, if you want to use the system for something while it’s processing, doing the work on a single core might be preferable ?Ģ. Have you checked to make sure that you’re actually using both cores properly? VB.NET is sometimes a bit single-core-focused, unless you work on splitting the workload into multiple threads. Those Intel leaf-blowers are just too loud for me :). Stock cooler? That’s one of the few things I always buy with a new CPU. How did you go? Did you achieve the same speeds? Are you doing better with an E8400 or E8500? How much better? Got any questions? I’m really keen to hear from you – leave a comment below!
RAM:FSB Ratio 1:1 (so effectively the Ram is matched to the CPU speed, running at around 490MHz – well, actually, 980 because it’s DDR – double data rate).
With a little trial and error, I’ve been able to get it stable at a pretty decent 3.92GHz with the stock standard cooler. Ok – so, the E8200 is rated at 2.66 GHz out of the box. Recommended Overclocking Settings for the E8200 Meh – what the heck – if you’re going to go all out, why not get the works – so I topped off my purchase with some Kingston HyperX PC8500 DDR2 RAM as well – which is rated to 1066MhZ.Īdd to that a nice little RAID 0 array of 2*500Gb 7.2K rpm hard drives for my data, and 1 10K RPM 160Gb WD Raptor, and you’re starting to shape up as a very speedy system.
With over 2 million data points, the process takes many days… SO… in the interest of speeding it up, I recently decided to buy and overclock one of the new generation ‘Wolfdale’ Intel 45nm Core 2 Duo Processors – the E8200, which is the little brother to the new e8400 and e8500 series.įirstly, the E8200 processor itself uses the same socket (775) as Intel has been using for quite some time now, but as I’ve been using AMD 64 processors up until now (socket 939), I needed to get a new motherboard as well – I chose the Gigabyte P35C-DS3R motherbard. Ok – so, if you read my last post about GIS systems and Sugarcane Yield Monitors you would be well aware that I’ve been labouring with a very processor intensive task called ‘Inverse Distance Weighted Yield Projections’.