Harvesting & Reusing Idle Computer Cycles

Hustler writes "More on the University of Texas grid project's mission to integrate numerous, diverse resources into a comprehensive campus cyber-infrastructure for research and education. This article examines the idea of harvesting unused cycles from compute resources to provide this aggregate power for compute-intensive work."

Comments

electricity

[TedCheshireAcad]

Does anyone realize that running a CPU at 100% takes more electricity than running a CPU at 10%?

"wasted compute cycles" aren't free. I would assert they're not even "wasted".

Re:electricity

[Anonymous Coward]

The point is that they're not being used, and that they can be used for research. From the point of view of the researchers, who need these cycles, they are wasted.

Re:electricity

[TERdON]

Yeah, but it still draws a lot less letting a some computers burn some cycles, than you would have to use if you built a shiny, new, cluster. And you don't have to pay for the hardware either, because you already have it...

Re:electricity

[ergo98]

"wasted compute cycles" aren't free. I would assert they're not even "wasted".

No doubt in the era of idle loops and HLT instructions unused processor capacity does yield benefits. However from the perspective of a large organization (such as a large corporation, or a large university), it is waste if they have thousands of very powerful CPUs distributed throughout their organization, yet they have to spend millions on mainframes to perform computational work.

Re:electricity

[hotdiggitydawg]

That's a very valid point, we should not assume that this usage comes at no cost to the environment. However, the cost of building and running a separate CPU dedicated to the same purpose is even higher - twice the hardware infrastructure (motherboards, cases, power supplies, what else? monitors, gfx cards, etc.), twice the number of cycles wasted loading software infrastructure (OS, drivers, frameworks eg. Java/Mono). Add to that the fact that hardware is not easily recycled and the "green" part of me suggests that cycle-sharing is a better idea than separate boxes.

The next question is - who pays for the electricity then? University departments are notorious for sqabbling over who picks up the tab for a shared resource - and that's not even considering the wider inclusion of home users...

Re:electricity

[antispam_ben]

Does anyone realize that running a CPU at 100% takes more electricity than running a CPU at 10%?

Yes, I do, the same for RAM being accessed and for a hard disk drive when it's seeking. But this is insignificant compared to the overhead of the power supply, fans, hard disk drive spindle motors, other circuitry that runs continuously, and dare I mention all those fancy-dancy computer case lights that are popular now.

The incremental cost of these otherwise-unused cycles is so low that they can be considered free.

So someone prove me wrong, what's the electricity cost of running a CPU at full cycles for a year vs. running at typical load? What's the cost of the lowered processor life due to running at a higher temperature. Chip makers will tell you this is a real cost, but practically, the machine is likely to be replaced with the next generation before the processor has a heat-related problem.

Regardless, the cost is MUCH lower, in both electricity and capital, than buying other machines specifically to do the work assigned to these 'free cycles'.

Re:electricity

[Profane MuthaFucka]

First, figure the (Watts fully loaded) - (watts at idle) and call it something like margin watts. Then, figure out how much a kilowatt hour of electricity costs in your area. Say 7 cents.

Since a watt is a watt, and for rough purposes you can either choose to ignore or treat power supply inefficiency as a constant, you can get an idea of what it costs.

Chip: 2.2Ghz Athlon 64
Idle: 117 watts
Max: 143 watts
difference: 25 watts
Kilowatt hour / 25 watts = 40 hours.

It takes 40 hours for a loaded chip to use a kilowatt hour more electricity than an idle chip. Over a year, this will cost you $15.34 in electricity. Since your power supply isn't 100 percent efficient, it'll be more. Say 20 bucks a year.

Re:electricity

[Jeff DeMaagd]

My questions are in relation to the public distributed computing projects.

Who pays for that extra electricity? What if the program was poorly written and destabilizes the computer?

Few to none of the distributed computing projects don't factor this in. It's a nice way of cost-shifting, I think.

I think it is a good way for an organization to make better use of their computers though, I really don't want any part of it.

Re:electricity

[Smiffa2001]

What would be amusing was if global warming research was being done with the 'spare' cycles:

"Sir, we've completed the study and all the results are in. It's pretty shocking..."
"Go on..."
"Well, since we started, it's gotten much worse compared to before. The rate of change increased. We think it's the increased power use..."
"D'Oh!!!"

NOTE: Scientific accuracy might be impaired during the length of this feature. Thank you for reading.

Re:electricity

[hazem]

What all of you working from the electricity cost issue are missing is that at most universities, money for capital is different than money for operations. Capital money is hard to get. An increase in your operations cost just kind of get ignored if they're not too big.

This has political ramifications.

The goal: get a great, powerful, cluster of compute power.

You can't go to the administration and say, "We need to spend $150k on a compute cluster". The answer will be "we don't have one now, and everything's just fine. No."

So, you, being resourceful, implement this campus-wide cluster system that taps spare resources. Power bills go up a bit - nobody cares.

Now, a couple years later, lots of projects are using the cluster. But the thing isn't working well because the power's not there during normal peak usage.

At his point you go the administration, "we're losing tuition-paying students, and several grants are at risk because our compute cluster is not powerful enough. We need to spend $250k on a new compute cluster.

And THAT is how you manipulate your operations budget to augment your capital budget.

Re:electricity

[seanadams.com]

You forgot the bit where you sell the cluster, and then lease it back from the company you sold it to - that way it comes out of the monthly current budget, and not the capital account!

Re:electricity

[Jeet81]

I very much agree with you. With summer electricity bills soaring I sometimes think of shutting down my PC at night just to save a few dollars. With higher CPU usage comes more electricity and more heat.

--
Free Credit Report

Re:electricity

[arivanov]

Besides wasting more electricity you also drastically increase the speed at which the system deteriorates:

• On a cheap white box systems without thermally controlled fans the power supply fan is usually driven of non-stabilized voltage prior to it being fed into the 12V circuit. This voltage is higher when consumption is higher and the fan runs at higher revs and dies faster. The more power the system eats the quicker the fans dies. Result - dead computer and possible fire hazard.
• On more expensive "branded" systems with thermally controlled fans the speed of all fans is proportional to the power dissipation in the case. As a result on some brand machines the fan dies in less then 6 months at 100% CPU (Compaq P3 DeskPro) or the CPU is thermally throttled (Compaq P3 Prosignia and many P4 Evos). Result - performance at around 20% of the expected or computer requiring repair in around a year or less
• Nearly all modern motherboards have 20+ high quality electrolitic capacitors. If these blow up the bus gets noisy and the motherboard becomes useless. This is especially pronounced on miniITX and other small factor systems which tend to heat up very quickly to 45-50C inside. Running them at 100% round the clock causes the capacitors to start leaking in 6-9 months and the motherboard is a dead hunk of metal in a year or so.
• Ad naseum

If you add up all the numbers using spare CPU from desktops on an average campus does not make sense. You lose on the average 150+£ or so per system per year in electricity, repairs due to thermal failures and accelerated depreciation. Once you add helldesk and IT staff hours caused by the failures the numbers add up to 200£+. There is no way on earth you can get 200£ per year worth of computing power back so the numbers do not add up (at least for Compaq desktop gear).

Re:electricity

[AtrN]

Typically large organizations spend millions on mainframes to do I/O not compute and trying to move those types of things to PC clusters doesn't work without (a) adequate network infrastructure and (b) a distributed I/O system that scales. Some tasks can move, e.g. the obvious example is Google but they have rather unique constraints that make it possible, i.e. trivially parallelizable, no need to guarantee total correctness and a willingness to expose details of the distribution to applications (ref. GoogleFS API, MapReduce and Pike et al's language atop MapReduce).

People who do need lots of compute cycles need problems and, more importantly, solutions that are amenable to distribution over a cluster made from the office PCs, with its relatively slow and high latency comms. I.e. you need tasks with large amount of compute over relatively small amounts of data which don't need to communicate with each all that much. Not everything falls, or can be pushed, into that model.

Play fair on the resources

[Mattygfunk1]

I think it's great as long as they're careful not to impede on the user working. Done badly these applications get annoying if they are too pushy about beginning their processing before a reasonable user timeout.

Google's desktop search is one example where the timing and recovery back to the user is really done well.
__
Laugh daily funny adult videos

GridMP is a commercial distributed computing impl.

[ReformedExCon]

There are several non-commercial distributed computing systems, so the GridMP system isn't anything particularly new or groundbreaking. However, in companies that run very resource intensive applications and simulations, such a distributed system that uses unused CPU cycles has some serious applications.

However, the most critical aspect of this type of system is not just that the application in question is just multithreaded, but that it be multithreaded based on the GridMP APIs. To do such would require either a significant rewrite of existing code or a rewrite of it from scratch. This is not a minor undertaking, by any means.

If the performance of the application and every cycle counts, then that investment is definitely worth it.

Sure about that?

[brwski]

REusing idle cycles? Really?

Spambots

[HermanAB]

are harvesting spare cycles all the time. I don't think there are much cycles left over anymore!

"Compute" should only be used as a verb.

[Anonymous Coward]

"Compute" as an adjective is just weird. Keep your creepy clustering terms to yourself kthx

Electricity vs cost of more machines and labor

[G4from128k]

Does anyone realize that running a CPU at 100% takes more electricity than running a CPU at 10%?

This is a very insightful post, but has two crucial counterarguments

1. Does anyone realize the cost of buying extra computers to handle peak computing loads?
2. Does anyone realize the cost of idle high-tech, high-paid labor while they wait for something to run?

The proper decision would balance these three (and other factors) in defining a portfolio of computing assets that can cost-effectively handle both baseline and peak computing loads. Idle CPUs aren't free, but then neither are idle people or surplus (turned-off) machines.

Re:Electricity vs cost of more machines and labor

[Alwin Henseler]

"The proper decision would balance these three (and other factors) in defining a portfolio of computing assets that can cost-effectively handle both baseline and peak computing loads."

You're probably right, but oh what a beautiful line of marketing-speak... If you happen to work in management or sales somewhere, write this baby down!

Re:Electricity vs cost of more machines and labor

[Poltras]

Worse, they contribue to global entropy, thus reducing universe lifetime... What are we doing?

Re:Electricity vs cost of more machines and labor

[bcrowell]

There are costs that fall on the person who's donating the cycles, and costs that fall on the person who's getting the benefit of them. Unless both people are in the same organization, operating under the same budget, it's not just a question of minimizing the total cost. In the typical situation, the cost to the donor needs to be almost zero, otherwise the donor isn't going to do it. Even in a university environment, one department may have a separate budget from another department. Or electricity may be provided from the campus without a budget charge to the departments, but other costs, like paying sysadmins, may be specific to the department.

Personally, I ran the SETI@home client and the Golomb ruler client for a while, but stopped because of a variety of factors:

1. It makes my configuration more complicated, and any time I buy a new computer or do a fresh install, it's one more chore to take care of.
2. I ran SETI@home for a while at work (on my own desktop hardware I brought from home, hooked into the network at the school where I teach), but I got scared when I heard stories about people getting fired for that kind of thing at other institutions. The network admins at my school are very uptight about this kind of thing, and don't have the same ethic of openness and sharing that most academics have.
3. If I run it at home, I'm paying for the extra electricity.
4. Most of the clients are closed source. I'm very reluctant to run closed-source software on any machine I maintain. You might say that the people who wrote the clients are trustworthy, well-known academics, not malicious Russian gangsters, but in my experience, most academics are actually pretty piss-poor, fly-by-night programmers. What if there's a security hole? Sure, the client described in TFA is supposed to be sandboxed, but how sure can I be that the sandboxing is really secure? I'm not normally particularly paranoid about security, but the rational approach to security is to weigh costs and benefits, and here the benefits to me are zero.

I think if grid computing is ever going to take off, it needs to become a capitalist enterprise. If someone would pay me a few bucks a day for my spare cycles, and the client was open-source, and there was close to zero hassle, I'd gladly do it. Remember, one of the good things about a free market is that it tends to be an efficient way to allocate resources.

Re:Electricity vs cost of more machines and labor

[haakondahl]

Huh? Whatever, sign me up for two.

Reused???

[LemonFire]

Does anyone realize that running a CPU at 100% takes more electricity than running a CPU at 10%?
"wasted compute cycles" aren't free. I would assert they're not even "wasted".


And neither are the computer cycles reused as the slashdot article would have you believing.

How can you reuse something that was never used in the first place?

Re:Reused???

[codeguy007]

Now say that we get about 3.4 GHz worth of cycles each second (that's what AMD tells you)

You should have used your mod points and not made a fool of yourself.

An Athlon64 3400+ does not run at 3.4GHz but 2.2GHz. Thus you're whole calculation of computer cycles is wrong. 3400+ is a PR rating comparing the performance of the Athlon64 to a Pentium4 of 3.4GHz.

Re:Reused???

[ZosX]

Who's the fool now? The 3400 rating is actually based upon the performance of a 1ghz Thunderbird IIRC. So a 2000 would be roughly the equivavelent of a 2ghz Thunderbird, NOT a 2ghz Pentium 4, even though the processor is actually running at 1.6ghz.

But don't take it from me. From the horses mouth:

Section 2 The Model number

The model number is fairly straight forward the numeric code of the Core ID will give you the model number. In the case of the newer Athlon XP's it will be the PR rating of the CPU. For example the AMD Barton 3200+ would have 3200 as its model number and not its operating MHz. The older CPU's such as the Thunderbird and the Duron which do not have PR ratings will have their operating speed in the model number section. A Thunderbird 1.4Ghz will have a model number of 1400.

Re:Reused???

[codeguy007]

So what makes the wikipedia the be all and end all of information? A collection of user contributed information. I would hardly use it as proof in an argument.

Suffice to say however AMD calculates it's PR rating really doesn't change the fact that it's to provide a comparison between Athlons and P4. I can guarrantee you if intel released a P4 processor that changed that correlation, AMD would change their PR rating on new processor to match it. Of course now that Intel itself is going to a PR rating of sorts that all changes.

GridEngine

[Anonymous Coward]

http://gridengine.sunsource.net/

Free and opensource, runs on almost all operating systems.

Spyware, Adware & Malware

[Krankheit]

I thought that was what spyware was for? When you are not using your computer, and while you are using your computer too, let your computer send out e-mail and perform security audits on other Microsoft Windows computers! In exchange, you will get free, unlimited access to special money saving offers for products from many reputable companies, such as Pfizer.

Wrong

[imsabbel]

What you are saying was perfectly correct even 3 years or so ago.

But case in point: My Athlon64 computer doubles its wallplug powerdraw (including everything:PSU, Mainboard, HD, ect) at 100% load compared to idle desktop (ok, cool%quite helps pushing idle power down).

The cpu IS the biggest chunck besides some high-end GPUs (and even those need MUCH less power when idle), and modern cpus need 3-4 times as much power under full load compared to idle.

Re:Wrong

[big tex]

Using the Lap-Burn-O-Meter (TM) as a gauge of overall power consumption with my Powerbook G4, I can definitely say that higher cpu cycle activities (encoding 1hr AAC files, for instance) increase power usage.

I could probably do something fancier by monitoring power draw with it unplugged, but my balls would be fried before I could tabulate the accurate data.

Re:Wrong

[kesuki]

What you are saying was perfectly correct even 3 years or so ago.
Hrm no.
no need to repeat myself

Running cpus at full load has made a huge difference in the cost of operation since the early pentium days. His point is that the cost of the 'electricity' is less than the cost of buying/powering new hardware specifically designed to do the work. Remember the electrical cost of the systems that are idle doesn't go away. those systems are on, anyways. Computer lab access is generally 24 hours a day, so the systems always need to be on, thus they always need to use power.

You are right that running under load can double or even triple electricity consumption (the CPU isn't the only piece of electronics in a desktop that has a 'power saving mode') the motherboard shuts down whatever it can, the PSU especially lowers rotational speeds on fans to reduce power, the PSU itself wastes less power on conversion etc etc.. but all that was just as true 5 years ago.

The fact of the matter is your main savings is on the hardware cost. Even if you consider that a true cluster is going to be more efficient than a distributed cluster, the fact that you're increasing electrical draw by buying said cluster without being able to reduce the number of idle systems is enough to offset the slightly greater electrical draw/mips ratio of distributed computing.

A big cluster has way more fans, and cpus, and many many high power server class PSU's, unless you're running it directly from a DC power generating station.

1st Grid Design: GNU Jet Fighter

[reporter]

Let's do something really interesting with this grid technology. Instead of participating in SETI, let's use this grid to design the first GNU jet fighter (GJF). Our target performance would be the Phantom F-4J, modified with a gattling cannon. We could design and test the GJF entirely in cyberspace. The design would be freely available to any foreign country.

Could we really do this stunt? I see no reason why we could not. Dassault has done it.

Dassault, a French company, designed and tested its new Falcon 7X entirely in a virtual reality. The company did not create a physical prototype. Rather, the first build is destined for sale to the customer.

CPU power consumption

[ergo98]

http://www.tomshardware.com/cpu/20050509/cual_core _athlon-19.html

60-100W difference between idle and full power consumption. That is not an insignificant amount of power.

Re:CPU power consumption

[Anonymous Coward]

Great link!

FTA: there is something that we can't really tolerate: the Pentium D system manages to burn over 200 watts as soon as it's turned on, even when it isn't doing anything. It even exceeds 310 W when working and 350+ W with the graphics card employed! AMD proves that this is not necessary at all: a range of 125 to 190 Watts is much more acceptable (235 counting the graphics card). And that is without Cool & Quiet even enabled.

end quote.

Bottom line, if you care about energy conservation at all, buy an AMD and don't sweat letting it run full-bore.

Re:CPU power consumption

[Xandu]

But it isn't that expensive. Let's call it 100W extra. 24 hours in a day gives us 2.4 kWh per day. For a year, call it 876 kWh. Approximate cost of electricity (in Texas) is about 10 cents per kilowatt-hour. That's $87.50 per year. Let's assume that you can extract half of the computer's horse-power for your cluster (the rest is lost in overhead of the cluster software etc, and of course, whatever the actual user of the PC does, which is often just word processing, email, and surfing the web). For an extra ~$175 per year you get the equivelant of another computer.

If you wanted to get that computing power in a stand alone system, you'd not only have to purchase the PC (up front capital), but you'd have to pay more for electricity. From the reference link, only about 30% of a computer's power is used by the CPU, the rest is doing nothin'. The computers referenced, at full bore use 185W (best case). That's $162 per year at my 10 cent per kilowatt hour quote. Cheaper, sure, but by the cost of a computer? Not even close.

Of course, there are other (hidden) costs involved in both methods, of which I'm not including in my (overly?) simplified model. And I'll just brush under the rug the fact that this kinda assumes that the average secretary has a top of the line system to surf the web with.

Don't invent your own mouse trap

[mi]

It is almost a 'meme' -- when people start on projects like this, they tend to think, off-the-shelf software (free and otherwise) is not for them and they need to write their own...

PVM offers both the spec and the implementation, MPI offers a newer spec with several solid implementations. But no, NIH-syndrom prevails and another piece of half-baked software is born.

Where I work, the monstrosity uses Java RMI to pass the input data and computation results around -- encapsulated in XML, no less...

It is very hard to fight -- I did a comparision implementing the same task in PVM and in our own software. Depending on the weight of the individual computation being distributed, PVM was from 10 to 300% faster and used 5 times less bandwidth. Upper management saw the white paper...

Guess, what we continue to develop and push to our clients?

Re:Don't invent your own mouse trap

[Coryoth]

MPI is great. I used to work at a shop that had a lot of Sun workstations. After doing some reading I managed to recode some of our more processor intensive software to run distributed across the workstation pool (automatically reniced to lowest priority) using MPI. As long as you managed to get a large enough workstation pool (which wasn't that hard, given how many people had one sitting on their desk) the distributed version was every bit as fast as standard version running on high performance servers.

In effect, using MPI and a bit of recoding effort, I managed to double the number of available servers.

Jedidiah.

Re:Don't invent your own mouse trap

[iamnotaclown]

I'm surprised no one has mentioned Condor. It can run serial or parallel jobs (PVM and MPI are supported), does checkpointing, scales up to massive compute farms, can talk to the Globus Toolkit, is multi-platform (Windows, Linux, Mac, Solaris, HPUX to name a few) and is open source.

Support contracts are available, but not mandatory.

Not affiliated, just a happy customer.

Parallels to the ethanol debate

[mc6809e]

How much energy does it take to harvest the energy?

How many cycles does it take to harvest the idle cycles?

Is the balance positive or negative?

Distributed computing less efficient

[imstanny]

Everyone is saying that the cost of making a machine to do the same process that can be distributed to a computer is overlooking a very crucial point.

Distributing computing processes to third parties is much more inefficient. The workload has to be distributed in smaller packets, it has to be confirmed & rechecked more often, and the same workload has to be done multiple times due to not everyone runs a dedicated machine or always has 'spare cpu cycles.'

I would agree that distributing the work load is cheaper in the long run, especially with an increase in the amount of participants, but it is not a 1 to 1 cycle comparison, and therefore it is not necessarily 'taht much cheaper', 'more efficient', or 'more prudent' for a research facility to rely on others for computing cycles.

sunsource.net

[Jose-S]

This seems to be a new site, right? Found this in their FAQ:

Q: Will Sun make Java Technology Open Source? A: Sun's goal is to make Java as open as possible and available to the largest developer community possible. We continue to move in that direction through the Java Community Process (JCP). Sun has published the Java source code, and developers can examine and modify the code. For six years we have successfully been striking a balance between sharing the technology, ensuring compatibility, and considering the needs of a growing installed base of more than 2.5 million Java developers who depend on us. We are certainly evolving Java through the JCP to a model that works for all involved but that also ensures compatibility. Cross-platform compatibility has always been the key to Java's success and integrity; a notion we feel was protected by Microsoft's agreement in January 2001 to settle the lawsuit regarding Java technology.

I take it that's a 'no.'

Re:If I could only use this to improve rendering t

[SlamMan]

If you have extra Macs, you can with DVD studio and Shake. Look up qmaster.

Heterogeneous Hardware & mathematical accuracy

[mosel-saar-ruwer]

Heterogeneous Hardware - This is a major issue.

The kinds of things that interest high-end computing geeks tend to be extremely sensitive to round-off error.

If you're trying to get accurate results by spreading calculations around among disparate machines that might deploy e.g. IEEE 64-bit doubles, IEEE 96-bit doubles [Intel & AMD], IEEE 128-bit doubles [Sparc], or various hardware cheats [MMX, SSE, 3dNow, Altivec], then trying to make any sense of the results will drive you absolutely bonkers.

PS: A good place to start in understanding the uselessness of e.g. 64-bit doubles is Professor Kahan's site at UC-Berkeley; you might want to glance at the following PDF files:

Matlab's Loss is Nobody's Gain

How JAVA's Floating-Point Hurts Everyone Everywhere

etc

wear & tear associated with running at 100% cy

[espek]

Is there "wear and tear" associated with running a computer at 100% CPU cycles all the time via one of these distributed computing programs like Folding@Home?

Will running these programs make my computer less reliable later? Shorten it's productive life (2-3 years)?

I have a Dual 2.0 Mac that I leave running all the time because it's also acts as my personal web server, and because it's just easier to leave the computer on (not asleep) all the time. I run Folding@home because I believe in the science and research and know that my contributions actually help good science. But the idea of wear and tear of the machine has crossed my mind and want to know what the negatives are to doing this to the machine (besides having to pay for the electricity).

Re:GridMP is a commercial distributed computing im

[Smart Teapans]

Good point. Having to rewrite the application to make use of a parallel MPI can be a pain. Condor is a free full-featured batch system that allows you to run apps on remote machines without having to recompile them

Green fancy-dancy!

[TheStonepedo]

The voltage from my idle memory cycles goes through a series of capacitors and ICs to make my fancy-dancy lights blink so I won't have to buy new computers and waste power - and all of this is within a 133 MHz underclocked pentium box with 32 MB ram running linux.

I'm saving the world!

Re:1st Grid Design: GNU Jet Fighter

[DigiShaman]

Ya, let's countries such as China and N. Korea have such access to free engineering. After all, we want oppressive regimes to have as much power over their own citizens. I mean, when was the last time YOU could fly your own jet? Such gaps between non-democratic governments and it's citizens make much-needed revolutions that much harder to achive.

laptop cores are much better

[steve_l]

I saw some some posters from the fraunhofer institute in germany on the subject of power, with a graph of specint/watt.

0. all modern cores switch off idle things (like the FPU) and have done for some time.

1. those opteron cores have best in class performance

2. intel centrino cores, like the i740, have about double the specint/watt figure. That means they do their computation twice as efficiently.

In a datacentre, power and air conditioning costs are major operational expenses. If we can move to lower power cores there -and have adaptive aircon that cranks back the cooling when the system is idle, the power savings would be significant. of course, putting the datacentre somewhere cooler with cheap non-fossil-fueled electicity (like British Columbia) is also a good choice.

Re:laptop cores are much better

[hazzey]

and have adaptive aircon that cranks back the cooling when the system is idle

You mean like a thermostat?

Re:1st Grid Design: GNU Jet Fighter

[nbritton]

How about we do something that's a little more pratical and useful such as finding new drugs that will cure cancer.

And the Pentium M??

[Grendel Drago]

Err, not precisely. Intel's Pentium M can create a system that draws 132 watts at maximum CPU load, and runs nearly as fast.

I've been buying AMD for about five years, but I think my next system will be a Pentium M. Just as soon as they're a bit cheaper...

--grendel drago

Sorry. This is hardly news

[Moderation abuser]

Seriously. We're talking about literally a 30 year old idea. By now it should really be built into every OS sold. The default configuration for every machine put on a network should link it into the existing network queueing system that you all have running at your sites.

You're Missing the Point

[kf6auf]

Your choices are:

1. Use distributed computing to use all of the computer cycles that you already have.
2. Buy new rackmount computers which will cost additional money up front for the hardware and then they have their electricity and cooling costs.
3. Spend absolutely no money and get no more computing power.

Note that the solution in this article is obviously not free due to electricity and other support costs, but it is undoubtedly cheaper than buying your own cluster and then paying for electricity and the support costs.

Re:wear & tear associated with running at 100%

[Zendra Thon]

There is increased wear and tear associated with running a computer. However - in university environments, this may not matter. At the university where I did my undergrad work, and now at the current one where I work, all general student-use computers in labs are replaced on a three-year basis. At any one time, there is a huge glut of just-barely-not-newest computers to be had. So shortening the lifespan of these machines really won't matter. The lab boxes are on most of the time anyway, and will be rotated out before they break.

Wisconsin Condor

[mrm677]

The Wisconsin Condor Project has been harvesting unused compute cycles for over a decade. The software is free to use and deploy, and is used by various corporations including Western Digital and others.

Wow, I've never heard of this idea before...

[Jugalator]

Hmm, where have I heard about this before again?
Exciting to read a paper on this fanastic new idea.

How about extra GPU cycles?

[davidwr]

When I'm doing pedestrian things - read anything but games, videos, or high-end graphics work - my graphics card is underutilized.

Wouldn't it be cool to utilize it to its full potential?

Even better, when the screen saver would normally in, just turn over the graphics card completely to the background process.

Imagine Seti@home running on your GPU.

PS: Ditto some other processors that aren't being used to their full capacity.

Re:How about extra GPU cycles?

[Duncan3]

Wow, why didn't we do that... oh wait, we did, years ago in fact. (everyone else thought of it too)

GPU don't have real math... yet. So instead of Folding@home you get "tossed on the bed"@home. Which is unfortunately useless.

Stay tuned tho. :)

BUAhahahaha... poor suckers...

[jnelson4765]

Our new buses are the exact same - designed in CAD - no prototype phase - first production models were sold.

And they are shit.

Flimsy, awkward, handle like a drunken whale, weak brakes, and parts you *physically cannot get to*.

There is a very good reason for prototypes - you get to see what breaks *before* you invest in production tooling and large material and parts purchases.

They're gonna lose their ass on that...

I am a sinner

[exp(pi*sqrt(163))]

So a while back our company shut down. For the last couple of months a bunch of us worked 3 days a week on making a graceful shutdown. During that period we had about 1500 2-3GHz CPUs sitting idle. I had about 2 days spare to work on writing code, and even on the days I was working there wasn't much to do. At the start of the shutdown period I thought "Wow! A few teraflops of power available for my own personal use for two months. And the spare time to utilize it. I could write the most amazing stuff." And what did I do? Nothing. I am a sinner. I have some excuses: I had to look for a new job 'n' all that. Even so, I could have done something.

So what should I have done with that CPU power?

Re:If I could only use this to improve rendering t

[ToasterofDOOM]

BURP is a project of a similar concept built off of BOINC. I'd link to it but I don't have it. Just Google it.

Re:Heterogeneous Hardware & mathematical accur

[greg_barton]

How JAVA's Floating-Point Hurts Everyone Everywhere

That presentation was done in 1998.

That'd be seven years ago...

Ever heard of java.lang.StrictMath? Didn't think so. Been around since Java 1.3. Current version is 1.5.

Do read the article

[roystgnr]

This isn't just about parallel computing - in fact if you'll read the article you'll see that they're using MPI for handling parallelism! Grid computing isn't about reinventing inter-node communications - it's more about inventing inter-node scheduling.

Your cluster - is it so fast that you're never stuck waiting for jobs to finish? If not, then you could probably benefit from being able to borrow time on someone's larger system. Is your cluster so well-utilized that the load's always around 1? If not then you've probably got spare capacity that someone else could benefit from. The fact that both you and those others are using MPI is necessary but insufficient to allow you to cooperate.

Really, no. A cycle is not a cycle is not a cycle

[arete]

First, I completely agree with you that it does depend a lot on what you're doing. For instance, last I heard _cycle for cycle_ the Pentium is still the king of integer - such as chess. But the crown is different for flops... Raw clock is meaningless and you are highly misguided. Furthermore, MANY operations are multicycle, and I guarantee you they are used on anything mathmatically intense enough to be worth sending out over the network.

Interestingly, you don't have to leave Intel to see this: the Celeron, "vanilla" P4, Xeon and Pentium M have a lot of good differences just within the current Intel x86 line. The Pentium M is awesome, for instance.

But I'll provide just a few examples of how a cycle is NOT a cycle.

Many of these only help you if you compile for that architecture or it does something fancy in the background to compensate - but you could certainly distribute a mixed exe that ran the appropriate binary for the platform.

- First, bitwidth:
64 bit addition requires 1 cycle on a 64 bit cpu, but at least about 3 on a 32 bit. 64 bit multiplication is MUCH worse on a 32bit machine. Similarly, 128 bit vector math is much cheaper on a G4 ("altivec") than on a CPU limited to 64 or 32 bits in that arena.

- registers: A CPU can only actually DO operations on values in registers. If you have more registers you can do much more complicated (longer-chained) operations without having to go to RAM or cache. This is intensely true on highly serial but complicated math and amazingly significant if the operation data actually fits in registers in one CPU and not in another.

- branch prediction and shorter pipeline depth. All other things being equal you want the shortest pipeline possible because it means you have the lowest branch prediction penalty. Coupled with the quality of your branch predictor, this makes a big difference. (Of course, things _aren't_ equal, and longer pipelines make it easier to physically build faster CPUs) Even if branch prediction is meaningless, the pipeline depth is still important.

- parallelization: _All_ modern computers let you run some multiple commands in parallel using multiple CPUs, cores, hyperthreading and/or multiple processing units. Many computers come with two CPUs. Some newer CPUs comes with two cores. Hyperthreading decreases the process switching penalty. Modern CPUs have separate integer and flop units, often more than 1. Clearly the quantity and efficiency of these multiple units would make a big difference.

At an absolute minimum, all of these things help you run the OS without interfering too much with your actual work. But since we're talking about stuff that's already being distributed over a wide network to multiple computers, on some level this work is clearly parallelizeable. Even if your second core can't help on your first 'chunk' you could likely be executing two chunks at nearly the same speed (barring other constraints listed here)

- cache(L1/L2/L3), cache prediction, RAM, bandwidth, chipsets. I'm not going to go into all the details, but suffice to say that the cores need data and code to function and unless your entire process fits in registers, they have to get it from somewhere. The arrangement of memory has a big impact on 1) how much work the CPU has to do to get information and 2) how much the CPU has to wait for that information.

- I/O - I know this is out of our case, but the CPU efficiency of IDE has increased dramatically, but there is still some variance from system to system and driver to driver. Furthermore, different network cards/drivers use significantly different amounts of CPU time to send large amounts of data. This is true even if the speed of execution is not I/O bound - it still takes some main processor clocks and the quantity varies.

Furthermore, this arbitrary driver code and any OS code - for instance - is definitely susceptible to traditional branch prediction, cache hits, etc - even if your main crunching loop did fit in registers.

I'm sure there's more, but I'm done for now.