Using pool-based evolutionary algorithms forscalable and asynchronous distributed computing
If you can't read please download the document
description
Presentation for PPSN workshop
Transcript of Using pool-based evolutionary algorithms forscalable and asynchronous distributed computing
Using pool-based evolutionary algorithms for
scalable and asynchronous distributed computing
J. J. Merelo, A. M. Mora, C. M. Fernandes, M. G. Arenas, Anna I. Esparcia-AlczarU. Granada + S2 Grupohttp://geneura.wordpress.com
Imagen de fondo adaptada de http://www.flickr.com/photos/gregmarshall/767068353/ por Greg MarshallLa combinacin de color es ColorCombo2 http://www.colorcombos.com/color-schemes/2/ColorCombo2.html
What are the ingredients for a massively parallel evolutionary algorithm?
Foto subida por Texas_mustang a Flickr en http://www.flickr.com/photos/astros/3977731447/in/photostream/
How can you use a server/backoffice that does (almost) all the work?
La imagen procede de Corea del Norte y es de gr0uch0 http://www.flickr.com/photos/groucho/6227328244/in/photostream/
Can you achieve fault-tolerance and asynchrony?
Imagen de John Steven en http://www.flickr.com/photos/53966621@N05/5038005080/in/photostream/
Pool CRUD
Pools allow create, read, update and delete operations.
Pool == population
Pool == conveyor belt
Fault-tolerantScalable
Implementation matters
Object stores: RDMBSorNoSQL
File synchronization systems
Which frameworks can be used to implement pools?
- Latency+ Concurrency- Lack of control+ Locality of writes
Conclusions
Tradeoff fault-tolerance/scalability.
Difficulty of non-centralized non-asynchronous operation.
Advantages: Availability of frameworks.
Optimal CRUD operations.
Availability of clients.
Choice of languages.
Paradigm mix!
Thanks!
Any question?See you at EvoPar 2013http://goo.gl/LtTCL
@geneura
