Proposing Registry

Thank you both, that was very helpful!

There is a talk about the DHT plans here:

The project was briefly mentioned at the conference in Stockholm last year:

It’s the distributed hash table mentioned as an alternative to Global on the last slide of “News from the OTP team.

There was also this tidbit:

http://www.erlang-factory.com/sfbay2017/christopher-meiklejohn.html

Recently, attempts have been made to resolve the problems of Distributed Erlang: SD-Erlang and Ericsson’s planned port of global to the Kademlia DHT are focused on reducing the amount of information that each node in the global registry needs to replicate, but that only temporarily mitigates the problem.

That’s about all I’ve heard personally.

Doesn’t global predate the Elixir Registry and this whole thread by years? I think that @josevalim was referring to something else. Still, I couldn’t see reference to any new work in progress in the global docs.

Perhaps in the documentation of the global module

Does anyone know where can I find more info on the OTP Team’s plans on a distributed registry?

Because the name is not optional on this case.

No conventions as far as I know.

Hey José,

I was taking a look at the code and was puzzled over two things:

• First one is, why use a positional argument for the registry name, rather than using the convention of passing name in the keyword list options.
• The second one is the reasoning for defining multiple modules inside the same file? I was trying to locate Registry.Supervisor and it took me a while to understand it was in the file rather then in a Registry folder.

Is there a convention in place for cases like this?

The Registry has been merged into Elixir master.

Yes but it doesn’t mean having a partition per core is necessarily the way to go. If you don’t expect an intensive workload, using 4 or 8 partitions for 40 cores would be fine.

Being the most pessimistic, I would do a factor of 0.25 on the number of cores. So for 40 cores, I would do 10 partitions. Like this: System.schedulers_online |> div(4) |> max(1).