vacp2p
/
research
mirror of https://github.com/vacp2p/research.git
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity

updates a figure and the future work

This commit is contained in:
sanaz 2022-08-24 13:28:43 -07:00
parent 869b989dda
commit ad3e3cd464
No known key found for this signature in database
GPG Key ID: 00C8796A0446EDC2
2 changed files with 1 additions and 2 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

3
rln-research/membership-merkle-tree-storage-evaluation.md
View File

@ -102,5 +102,4 @@ However, the MT storage overhead may not be reasonable for mobile devices especi
3) If the maximum group size is known, then it would be more efficient to use FMT.
## Next Steps
- For scalable production usage, we would like to look into some disk-based tweaks for Merkle tree storage management to account for OOM possibility in worst case scenarios.
In light of the approximate per-app memory cap provided in this post and according to our experimentation result, the in-memory storage of the membership Merkle tree for a large group of size 1,000,000 members is feasible for almost all known devices. Nevertheless, for scalable production usage and as future work, we would still like to look into some disk-based tweaks for Merkle tree storage management.

BIN
rln-research/pics/max-storage-fmt-hmmt.png
View File

Binary file not shown.
Side by Side Swipe Overlay

Before

Width:  |  Height:  |  Size: 37 KiB

After

Width:  |  Height:  |  Size: 39 KiB