gproc global will create a bootleneck in my app?

Pablo Platt pablo.platt@REDACTED
Mon Nov 15 15:11:46 CET 2010


I'm using gproc to handle IM sessions on one node and it works great.
I want to use it with gen_leader to extend to several nodes.
Saving a global name will be slower because that leader has to coordinate 
Will it affect reads as well?
If one gen_server is responsible for everything, does writing a global name 
might block all reads?

What is a reasonable number of unique names and non-unique properties I can save 
with gproc?
Am I only limited by RAM?



More information about the erlang-questions mailing list