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
In order to reduce unpredictable disk seeks, my intuition is that the ability to create namespaces englobing databases would help.
For example, creating the namespace mynamespace would actually create a leveldb backend on the disk with that name. And then creating a db mydb inside mynamespace would make every operations over mydb being written in mynamespace physical backend with a mydb: prefix key.
The text was updated successfully, but these errors were encountered:
Note that Plyvel provides transparent support for the 'sub-databases' you describe using its PrefixedDB API. It handles all operations (get, put, delete, iterators, and so on).
I saw that feature pass yes, but Elevator has been completely rewritten in Go language, so I'm not using plyvel anymore. I guess I will have to code it myself :D 👯
In order to reduce unpredictable disk seeks, my intuition is that the ability to create namespaces englobing databases would help.
For example, creating the namespace
mynamespace
would actually create aleveldb
backend on the disk with that name. And then creating a dbmydb
insidemynamespace
would make every operations overmydb
being written inmynamespace
physical backend with amydb:
prefix key.The text was updated successfully, but these errors were encountered: