Using dropbox for distributed evolutionary computation
•Download as ODP, PDF•
1 like•653 views
paper presented at th
Recommended
More Related Content
Viewers also liked
Viewers also liked (14)
Similar to Using dropbox for distributed evolutionary computation
Similar to Using dropbox for distributed evolutionary computation (20)
More from Juan J. Merelo
More from Juan J. Merelo (20)
Recently uploaded
Recently uploaded (20)
Using dropbox for distributed evolutionary computation
- 1. Assessing Speed-ups In Commodity Cloud Storage Services For Distributed Evolutionary Algorithms Maribel García-Arenas, Juan-J. Merelo Antonio M. Mora, Pedro Castillo, Gustavo Romero, JLJ Laredo GeNeura group University of Granada (Spain) Http://geneura.wordpress.com http://twitter.com/geneura
- 2. What do clouds smell like?
- 3. How can I use cloud storage for distributed evolutionary algoritms? If possible, for free!
- 4. We will find out in this paper
- 6. How we implement a distributed evolutionary algorithm over this system
- 7. Raw speedup measures over several computers
- 8. Differences between connection modes.
- 10. Gigabit Ethernet or WiFi + WPA connection
- 11. Dropbox updated to latest version
- 12. MMDP and Trap
- 13. Dropbox
- 14. Cloudy, with a chance of evolution Single individual Evaluations/node
- 15. Trapped in the clouds Ethernet WiFi
- 18. Load balancing is automatic.
- 19. Network matters
- 20. Good scaling
- 21. Will it mean a better algorithm?
- 22. Thanks for your attention Any questions? Http://geneura.wordpress.com Http://twitter.com/geneura
Editor's Notes
- Background picture from http://www.flickr.com/photos/coyote-agile/1578404172/in/photostream/
- Describe basic working principles of Dropbox as a free file synchronization service, how it monitors certain files and how they are copied when modifed under its own schedule. It's got a permission system that regulates who's got access to which resources; it's usually done per directory, and you can also make directory results publicly available.
- Every node runs independently, although they are started (roughly) at the same time. After an appointed number of generations, an individual (the best) is logged into the common directory, and another one is taken. A file with the total number of evaluations is also created, and the sum of all evaluations is checked as a termination condition. To speed up processing and reduce overhead speeding up synchronization, the individual is codified into the filename, so that the only thing that is read is the directory, not the content of the file itself. We use different kinds of codifications depending on the chromosome length, but lengths of several hundreds are not a problem. As it can be seen, the fitness is also codified into the name.
- Picture from Andrew Rivett, Veggiefrog