perf: use ets table for client ID registration #57
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This is a performance optimization incorporated with a refactoring.
Performance fix
supervisor:which_children(wolff_client_sup)
becomes quite expensive when there are many clients started (thousands).Main caller is
wolff:check_conectivity/1
.The fix is to store client ID -> Pid in a ets table.
Refactoring
1.9.0 made use of the producer name as ETS table key for producer process registration.
However that lead to two minor problems:
{ClientId, Topic}
uses the same producer name.the fix is to use
{ClientId, Topic}
as the ID, and the old "name" is only used as process registry (when it's an atom) for backward compatibility.