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
Badger can power the Storage interface, we should swap out the MemoryStorage, which is used in addition to Badger WAL store. This would decrease the RAM consumption of Dgraph.
The text was updated successfully, but these errors were encountered:
On Tue, 29 May 2018 at 00:25, Manish R Jain ***@***.***> wrote:
Badger can power the Storage interface, we should swap out the
MemoryStorage, which is used in addition to Badger WAL store. This would
decrease the RAM consumption of Dgraph.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
<#2417>, or mute the thread
<https://github.com/notifications/unsubscribe-auth/ACKSZpmraYLWGjeNSPI-oP6kzVPR_45hks5t3IdbgaJpZM4UQqyN>
.
Hard to say, but should be significant. I know the memory used by the MemoryStorage used to be a problem, so we have ways to avoid it growing too much. Those problems would go away if we don't use it.
Instead of using the default RAM based Raft Storage (MemoryStorage), build one based on Badger. This should significantly decrease the RAM usage by the Raft write-ahead log, potentially solving the replication OOM issue at #2424. This also fixes#2417 .
* Clean up the WAL API usage.
* Implemented the Storage interface.
* All raft storage tests work.
* Merge multiple txns into one.
* Optimize FirstIndex by using cache.
* Remove ApplySnapshot, because we no longer need it.
* Correct the order in which we store the Raft entries.
Badger can power the Storage interface, we should swap out the MemoryStorage, which is used in addition to Badger WAL store. This would decrease the RAM consumption of Dgraph.
The text was updated successfully, but these errors were encountered: