• Some users have recently had their accounts hijacked. It seems that the now defunct EVGA forums might have compromised your password there and seems many are using the same PW here. We would suggest you UPDATE YOUR PASSWORD and TURN ON 2FA for your account here to further secure it. None of the compromised accounts had 2FA turned on.
    Once you have enabled 2FA, your account will be updated soon to show a badge, letting other members know that you use 2FA to protect your account. This should be beneficial for everyone that uses FSFT.

Question for LABs

J

Jon855

[H]ard DCOTM January 2008
2FA
Joined
Aug 25, 2005
Messages
12,132
My borging has been delayed once again and this Thursday or Friday depending on the manager will allow me to borg total of 6 computers as a test run for a week before I can borg the rest of the systems to make sure that nothing is causing problems and so on forth as they're all new computers... He told me that he was grateful that it didn't cause any problems last year.

Now the question begs - should I install SMP on them or run regular console clients on them? Thirty of them are C2Ds and 12/13 of them are P4s. I'm asking this because of the expiration date on the SMP client... Will it still get work units even after it expires because I'm looking forward to set it up only once and let it run for the rest of the year...

Inputs please.

 
Regular.

SMP isn't ready for lab-wide installation yet. Every time they lose network connectivity, you're screwed. Every time they release a new version (even just to push back the expiration date), you're screwed. Every time one of them hangs (knock on wood, but still), you're screwed. Plus, even though it's supposed to be invisible, the SMP client isn't 100% reliable at releasing CPU cycles yet.

I think you see a pattern.
 
Jon855 said:
My borging has been delayed once again and this Thursday or Friday depending on the manager will allow me to borg total of 6 computers as a test run for a week before I can borg the rest of the systems to make sure that nothing is causing problems and so on forth as they're all new computers... He told me that he was grateful that it didn't cause any problems last year.

Now the question begs - should I install SMP on them or run regular console clients on them? Thirty of them are C2Ds and 12/13 of them are P4s. I'm asking this because of the expiration date on the SMP client... Will it still get work units even after it expires because I'm looking forward to set it up only once and let it run for the rest of the year...

Inputs please.

Click to expand...

I put the SMP client on my lab computers before because it's being used only a few days in 6 months so it's not a biggie to come back and restart when the lab is finished or there are issues (I check them with FahMon remotely).

However, for a truly painless borging, I suggest you use console clients so it will do their stuff no matter what happens to the computers. This may produce less points but it will be more stable...

 
I casted my vote in your other thread. Use the regular console client for painless operation. SMP is beta and I doubt we keep getting 1700 points per unit after the beta is over.


 
If it a test run so the boss can see how stable it is then the console client is the only way to go.

More stable client, smaller footprint on the computers, smaller download, etc, etc.
Once its up and running then maybe swop a couple of the less used C2D's, if there are any, to the SMP client.

So another vote for the console client.

Luck........ :D
 
Console client 100%. If for no other reason than the SMP client doesn't "really" work as a service, has a huge memory footprint, crashes often, and has somewhat frequent client updates making it a PITA to keep up and running with consistancy. Look at my PPD. That comes from 99% console clients. I think I have 4 total running SMP (maybe 5 but I am counting the Dual quad I have running as 2). I NEVER have issues with the console client, it just chugs along and behaves itself. The SMP client I have to keep checking on pretty much constantly (except on the mac oddly enough which I never look at) not to mention it is a bandwiddth killer when it sends WU back to stanford (seems like they run around 5MB or so to send in..it is noticable when it is happening for internet speed)
 
Tormond said:
Console client 100%. If for no other reason than the SMP client doesn't "really" work as a service, has a huge memory footprint, crashes often, and has somewhat frequent client updates making it a PITA to keep up and running with consistancy. Look at my PPD. That comes from 99% console clients. I think I have 4 total running SMP (maybe 5 but I am counting the Dual quad I have running as 2). I NEVER have issues with the console client, it just chugs along and behaves itself. The SMP client I have to keep checking on pretty much constantly (except on the mac oddly enough which I never look at) not to mention it is a bandwiddth killer when it sends WU back to stanford (seems like they run around 5MB or so to send in..it is noticable when it is happening for internet speed)
Click to expand...

SMP uploads is almost always above 20 Mb per result :eek: That's why I took down SMP clients from the lab :(

 
I've always run the console in the labs that I manage - it's the most sureproof way of avoiding problems and ensuring that you can keep using them for the F@H project.

 
plus people generally frown on deploying beta software, go with the regular console
 
Agreed - Thought I would ask and also the lab manager said that he is willing for the SMP Client only if it would have to be set up once but it does not seems like that will occur in the academic year so console it is :)

 
Two regular clients have been installed on the lab computers (2 of them) for a test trail before lab wide borging...

Here's to the goodness :)
 
BLUEFISH44 said:
about time, I was starting to think you had forgotten about our little contest.:p
Click to expand...

:) I just have begun to OC my 6600 as well :) Just mounted my new heatsink and the load temps is the same from 2.4 to 3.0 @ stock temps and stable... up and higher I go :)
 
mavalpha said:
Regular.

SMP isn't ready for lab-wide installation yet. Every time they lose network connectivity, you're screwed. Every time they release a new version (even just to push back the expiration date), you're screwed. Every time one of them hangs (knock on wood, but still), you're screwed. Plus, even though it's supposed to be invisible, the SMP client isn't 100% reliable at releasing CPU cycles yet.

I think you see a pattern.
Click to expand...

So to summarize -
If I run the SMP I'm sure to get screwed?

Sounds great to me :)

 
Jon855 said:
:) I just have begun to OC my 6600 as well :) Just mounted my new heatsink and the load temps is the same from 2.4 to 3.0 @ stock temps and stable... up and higher I go :)
Click to expand...

What cooler did you get for it? I'm kinda in the new cpu market myself.
 
Looks pretty good, so that sucker could run without a fan at stock speeds. Not that fans are all that noisy these days.
 
I realize you are going to put a fan on it, But isnt that cooler desined to run fanless?
 
I was only thinking to keep things quiet, Like if i had a little farm going it would be one less thing pumping out noise.
 
You must log in or register to reply here.
Back
Top