You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Apr 4, 2022. It is now read-only.
I am actually trying to figure which kind of metadata we can expect to put in plumtree? Any limit for? I am currently asking myself if it could be use as a global key registry, to register some key attached to processes like gproc but without any leader. Thoughts?
The text was updated successfully, but these errors were encountered:
The only hard limit I am aware of are the DETS storage limit of 2GB, which would apply to a given {prefix, subprefix}. The storage subsystem in general should be the biggest bottleneck as the data size grows. The only other part of the system I can think of that would see performance degrade as the dataset gets larger is the building of the hashtrees (and perhaps the exchanges, but those should continue to remain leightweight.
Regarding the specific use-case, I think holding metatada for all Erlang processes in a cluster is definitely do-able. As for gproc specifically I'm not familiar enough with it anymore to know if its operations can be built on eventual consistency, but if thats the case I don't see why it would be problematic.
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
I am actually trying to figure which kind of metadata we can expect to put in plumtree? Any limit for? I am currently asking myself if it could be use as a global key registry, to register some key attached to processes like gproc but without any leader. Thoughts?
The text was updated successfully, but these errors were encountered: