SETI and Cache

[Duner]

So, how much does Cache help on SETI projects?
The Answer is ALOT.

I just noticed something that I thought I'ds share.
I have an Imac on which I run bootcamp and Windows XP about 99% of the time. It has an Intel E8335 processor in it (special Mac only edition).

Its a Wolfdale running 2.66 GHz, but only a 1066FSB.
I was having some heat issues with it so I only had seti using 1 of the cores.
The normal 50pt units were being processed in about 45mins.
I have since sorted out the heat problems and am now running it on both cores. The process times have increased to ~65mins now.

The only thing I can think of is the shared L2 cache. When only 1 instance was running, the core got to use all 6MB of cache, and with 2 instances, each core only has access to 3MB of cache.

[benbaked]

Cache appears to be a significant factor, at least in my case. I have an E6600 at stock that is taking roughly 4600 seconds for a WU worth about ~75 points. My Conroe-L at 3.2 GHz is taking roughly 6400 seconds for WUs worth about the same points. They're both using the same Ak v8 optimized clients, so I assume it's a cache issue.