In the experimental studies it is usually cost effective to run simulations instead of performing the actual experiments (think of modeling a nuclear explosion instead of using the actual A-bomb, simulating the protein interactions instead of giving the experimental drug to an actual patient, etc.). While having practical benefits over experimenting, modeling is usually computationally intensive and few companies could afford a super computer. At the same time there is abundant CPU power available. There are millions of computers idling at night, while the user is in a meeting, at home, etc. SETI is one example on how to use this power. However, it is a very specialized solution.The idea is to create a base platform for distributed computing and build it into a screensaver. Companies could use it internally or to lend their resources. For example Disney could distribute the screensaver to all its workstations and use them at night to render Shrek 3. Or third parties could earn revenue by lending their free resources.
I agree
No opinion
I disagree
Add your comment
I like this idea, there is a vast amount of CPU time that just goes up in smoke. I think Apple has this technology in place but have not heard of its real use in a corporate environment. How do you control the the vast traffic that comes across the public users computer? Does the CPU owner pick and choose what project they want to lend their CPU time to or does some central server decide what units will be offered the opportunity to sign on?
The details of the implementation could be worked on. Most DC systems have centralized dispatcher; however, the virus community proved that decentralized approach is also possible. In any case, the owner of the CPU should consent to the tasks that are running on it.
This is a great idea and is currently used at almost all visual effects studios. There are a dozen or so different software packages that distribute computing. In the visual effects industry, the software is called "Render Queing Software" and Rush (http://seriss.com/rush) is probably the most popular publicly available package. In the past 10 years, in the visual effects industry there have been a few companies that have rented "render farms", vast arrays of computers connected to a high bandwidth network connection that are used as supplimental computing power. I am not aware of any that are still in business.
One of the difficulties in using distributed technology to render CGI is the large data sets (input images) that are required to render the final output image. All of the input data would need to be transimitted to the machine doing the rendering. Another issue is security of images (or data). The studios wouldn't like the possibility of millions of frames being distributed on unsecure machines.
Apple's XCode IDE also offers distributed compiling. FCP and Shake come with the QMaster render queue software and the MacOS ships with XGrid, another Apple distributed technology.
The breakthrough product for this area will be the one that makes distribution simpler, more generic, and transparent to the end users.