Folding@Home Client's Performance Impact Measured

EconolineCrush writes "Trying to convince your boss to let you run Stanford's Folding@Home client on the machines at work? Here's an article that measures the performance impact of running the Folding@Home client that might help. The article examines the client's impact on the performance of business applications, games, workstation applications, and more. When set up correctly, the Folding@Home client can be run transparently in the background with only a negligible impact on system performance, which means your boss has one less reason to turn you down."

Comments

And if your boss wouldn't let you do it before...

[aslagle]

this article isn't going to convince him.

Still not a guilt-free process...

[PseudoThink]

Don't get me wrong, I think distributed computing projects are great, especially those focused on legitimately useful research. However, running a distributed computing client on a machine at work will likely cause it to consume more electricity. A Pentium 4 has a maximum power consumption in the range of 65W, no? So every computer you install this on is like leaving a 60W lightbulb on 24-7, year-round. If you do this with many computers, I think that may add up to a nontrivial expense that you're essentially stealing from the company, no? Just playing devil's advocate...

Re:Still not a guilt-free process...

[kennylives]

No. The electricity used is not the issue within a company. The machines are on 24x7 anyway; the business has alreay accepted that cost of doing business.

What many businesses do not accept is the security and liability implications of running outside, unapproved code on their machines, expecially production boxen. "Who supports it when it crashes?", "What assurance do we have that it's not a trojan, gathering data?", "Why should we pay for their IT needs?" - these are just a few of the questions that a reasonably intellegent IT manager should/would be asking.

Of course, after all that, there's still the argument that "They're our machines, not yours. That's why." There's no easy way to answer that one and win.

Just maybe..

[JPelorat]

...there's more than one reason it's called "Folding@HOME" and not "Folding@WORK". Hmm?

If you can't get permission the first time around, repeated pestering will not help your case.

Re:And if your boss wouldn't let you do it before.

[gazbo]

But what about electricity usage? The recent case of the sysadmin who was fined a huge amount by the university for running a distributed client gave some figures:

• Electricity usage increases by ~60% when spare cycles are used.
  
• Logic switches in CPUs wear out up to ~15% sooner than if the idle cycles were left unused giving them time to cool down - we all know what a problem heat can be.
  
• Extra heat from the CPU can add an extra ~5% to the cost of electricity required to run an air conditioner.

OK, so I don't really believe the last one because it seems that most buildings have such variation in number of computers and people moving through etc. But that doesn't stop the other two for being equally accurate.

Performance impact is the least of your worries

[Kombat]

Managers and IT admins don't decline this sort of thing over something as pedantic as performance degradation - they decline it over much bigger issues, including but not limited to

• Risk of virus/worm infection
  
• Risk of inadvertently exposing a security hole
  
• Risk of compromising proprietary information
  
• Decreased employee productivity over installing/watching the client
  
• Lost time/money if this thing crashes an employee's machine, just as they were putting the finishing touches on the customer presentation due in 20 minutes
  

Does anyone really think that the reason these things are being rejected by management is because of performance???