Skip to content
This repository has been archived by the owner on Sep 22, 2022. It is now read-only.

VPack as block storage #221

Closed
dumblob opened this issue Jul 19, 2021 · 3 comments
Closed

VPack as block storage #221

dumblob opened this issue Jul 19, 2021 · 3 comments
Labels

Comments

@dumblob
Copy link

dumblob commented Jul 19, 2021

Has anyone thought about trying other low-level storage backends to experiment with efficiency & performance? Perhaps something like VPack could be interesting to test.

I'm asking despite seeing libmdbx's internals being rather more tightly bound to the current format (which seems nearly identical to LMDB).

@erthink
Copy link
Owner

erthink commented Jul 20, 2021

MDBX treat user's keys and data as opacity byte strings, except the MDBX_INTEGERKEY and MDBX_INTEGERDUP features. So nothing prevents you from using any serialization format, including noted VelocyPack.

On the other hand, using custom format for keys requires "custom comparators" which entails certain restrictions. Therefore, it is planned to implement minimal support for MessagePack.
However, I do think it is NOT reasonable to do same for VPack, since it is used rarely in comparison with MsgPack.

@dumblob
Copy link
Author

dumblob commented Jul 20, 2021

Oh, pardon me for not being clear with my question.

I'm asking whether someone has tried to exchange the memory layout (and thus also the on-disk data layout) libmdbx uses internally for VPack or anything similar.

@erthink
Copy link
Owner

erthink commented Aug 9, 2021

Suggest to close since no answer is expected.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
Projects
None yet
Development

No branches or pull requests

2 participants