Grid Computes 420 Years Worth of Data in 4 Months 166
Da Massive writes with a ComputerWorld article about a grid computing approach to the malaria disease. By running the problem across 5,000 computer for a total of four months, the WISDOM project analyzed some 80,000 drug compounds every hour. The search for new drug compounds is normally a time-intensive process, but the grid approach did the work of 420 years of computation in just 16 weeks. Individuals in over 25 countries participated. " All computers ran open source grid software, gLite, which allowed them to access central grid storage elements which were installed on Linux machines located in several countries worldwide. Besides being collected and saved in storage elements, data was also analyzed separately with meaningful results stored in a relational database. The database was installed on a separate Linux machine, to allow scientists to more easily analyze and select useful compounds." Are there any other 'big picture' problems out there you think would benefit from the grid approach?
Wikipedia? (Score:3, Interesting)
Ok, how does this apply to patents? (Score:5, Interesting)
Re:Ok, how does this apply to patents? (Score:5, Interesting)
How about open source, distributed search (Score:3, Interesting)
http://www.majestic12.co.uk/ [majestic12.co.uk]
Grid Computing Projects (Score:2, Interesting)
Re:Wikipedia? (Score:3, Interesting)
P2P isn't a good model, but I can think of one:
Data, as it is created, is stored in the users' shared folder. As other users go to access it, a copy is made from the cloud (as long as filename/size/hashes match) and that copy is used so long as the creator's copy hasn't been modified. When writes are done, they're done locally, and a patch is sent to the original copy. If the creator can't be contacted, or his copy doesn't exist, the last-writer becomes 'creator'. The file's creator is identified by his DC user name.
Backing up is simple. For every creation/update that is made, a patch is queued or sent to a backup server. The server ONLY queues the originals and patches, so that past-versions are accessible. As space becomes unavailable (say, below 10%), the backup server alerts the IT guys that it needs to offload some stuff, and condenses changes of the oldest files in the local copy. When a delete is made, that is considered a write and handled accordingly.
In the event of a reinstall (ie: the local copy of the files are deleted, but the world hasn't been notified), the user, upon connection would query the backup server to see where his stuff has gone, and get it back.
One could create this system to act like an SMB share, with access levels and program-independent drive/directory mapping, but with one added benefit: user-creation and auto-mapping. The DC would automatically tell the system which peer-shares are available to him upon login. The user can then filter out what he needs as he uses it, but can index-search it all (a query is sent to the backup server, which, like a good little machine, has been indexing as backups are made).
Lastly, for reverse compatibility, the backup server could provide SMB access to its copies, ensuring that non-updated systems can still access their stuff.
I don't know about most organizations, but I work at Penn, and a system like this could work admirably.
Re:Grid Computing Projects (Score:3, Interesting)
I'm afraid that that will take quite some time to realize. Rendering CG, besides taking a lot of processing time, also requires enormous amounts of data, which restricts the rendering to render farms, the data being pumped over a high-speed LAN.
Actually the amount of problems solvable by using Grid Computing over the internet isn't very high. You need computationally-intensive problems that can be easily parallized, besides requiring limited amounts of data. There's little point in distributing a problem if it takes longer to distribute the data than that you gain by using multiple nodes.
Re:Malaria? (Score:4, Interesting)
Where malaria flourishes, luxuries are scarce.
Travel as much as you can in your life, preferably to the poorer countries. They are often the happier ones.