[Kozmik]

I sped up my L2 cache on my iMac DV SE to 200MHz (2:1 ratio). SETI@Home depends heavily on the L2 cache. So why is it since I sped up the cache that SETI@Home units take longer than they did when the cache was at 160MHz (5:2)? Virtual PC also depends heavily on the L2 cache, and that does have a noticeable performance increase. Many other things seem a bit faster now, too. I just want to know why a program that needs a big and fast L2 cache should choke when it gets a faster one.

[wlonh]

well it doesn't, at least not on my Mac though it is not an iMac it is a G3 (466MHz/1M L2) i use xlr8's Mach Speed software to boost cache speed to 217.2MHz (that is what it reports)... my Mac crunches wu's at approx. 5.75 hrs on avg., without the cache acceleration it is a bit slower

this is just rough observational data, i have not felt the need to test things too closely with SETI because i am quite happy with the performance of my Mac running SETI