E2140

Associate
Joined
2 Oct 2006
Posts
657
Got a new dell for work today and it came with the super budget E2140 "pentium" class core. Basically a severely pwned C2D which gives each core 512k cache and runs at a meagre 1.6ghz (no overclocking possible here!)

I stuck SMP client on it last night to see how fast it could fold, it got a 2652 and is folding at a PPD of just over 400 :(

I know these CPU's can OC a lot, there's many reviews where people have got a 100% speed increase to 3.2ghz+ with absolute ease, unfortunately I have not go this choice, so at stock this cpu is a very poor SMP folder unfortunately (from my single experience anyhoo)

As its going into the office today i have replaced win SMP with 2 standard clients which are both getting ~120PPD with 3403 WU's. Not sure how this compares but I guess the tiny cache and low stock speeds really kills this one off, i'd have liked to OC it just to see its potential with a higher clock but no tools i know of can seem to handle the custom dell motherboards (plus the cooling system in dell optiplexes uses 1 low RPM fan to cool the entire PC, the cpu and everything else)

*EDIT*

Also I am now monitoring the 2 clients via fahmon but very often i get one client go red and say it has "hung" when it obviously hasn't and the log below is still showing the steps etc. I am not sure whether it is how i have set the client, I set the client to write every 10 mins and set fahmon to update every 10 mins as well. (Don't know if this would help fahmons accuracy but whatever, it seemed neat at the time :p )
 
Last edited:
120PPD with a p340x WU is pretty good going really, could try turning off -advmethods and see if you get something better

That 400PPD isn't very surprising - my [email protected] gets 550PPD at best on a p2652 thanks to the 512KB L2 per core
Shame to see it so crippled but I guess they are only really meant to do spreadsheets and word process normally :o :p


mikeymike said:
Also I am now monitoring the 2 clients via fahmon but very often i get one client go red and say it has "hung" when it obviously hasn't and the log below is still showing the steps etc. I am not sure whether it is how i have set the client, I set the client to write every 10 mins and set fahmon to update every 10 mins as well. (Don't know if this would help fahmons accuracy but whatever, it seemed neat at the time :p )

Are you using the latest FahMon? v2.2.2 has the option to ignore state detection for machines with unsynched clocks which might be what's happening.
You should be able to just overwrite the old v2 FahMon with the latest stuff - be sure to backup the original just incase though. Oh and make sure it doesn't end up Read Only as happened to me recently for some odd reason :o :p
 
Last edited:
Yes in theory, in reality, who knows! If the user leaves it on every night (as they have been told so the server can send them windows updates blah de blah) then it should fold 24/7, however they love turning things off here, must all be tree hugging energy saving hippies or something :p
 
Back
Top Bottom