Creator here; it's worth pointing out that the current picking solution might suffer from its own (performance, not scalability) problems - it reads the pools i

Creator here; it's worth pointing out that the current picking solution might suffer from its own (performance, not scalability) problems - it reads the pools info from a shared ETS table and picks a random element from that list; mandatory, deterministic naming of the pools would limit this step to a simple concatenation / conversion to atom. Something I will consider.