
Originally Posted by
mstp2009
F@H isn't that cache sensitive. I have run it on a E2160 (1MB) and an E6600 (4MB) clocked at the same speed (2.4GHz) and the results on the same WUs were within 4-5% of each other. I would not call that cache dependent.
What F@H is optimized for is SSE2/3 code. AMD X2 CPUs used to get trounced compared to C2D at the same clock in F@H, and with AMD's improvements to the SSE performance of K10 they are now up to par with C2D/C2Q. They didn't take the lead it looks like, but it is encouraging that they are competitive again.
Bookmarks