Bryce writes:
I was trying to think what I would use a cycle market for. The only thing that I wait for more than a minute on currently is compiling.
Tasks which are inherently parallel (preferably ones where the various processes are loosly coupled and the need for inter-task communication is low) are the first things that come to mind, because advances in the speed of CPUs does not give you the same advancement increment in solving these problems. Some examples: -rendering and ray tracing -simulation -analysis of large datasets -genetic algorithms and genetic programming (something I am working on creating a "cycle market" for in my spare time) The other class of tasks which could use such a market are those which are limited more by bandwidth than by processor speed. If the server can be given many "heads" which can provide the service (with the back-end processing done by cycle markets) then it is possible to make significant gains in distributing the I/O load and getting around network latency by creating server which is "virtually omnipresent." jim