Open vweevers opened 2 years ago
rave-level
is shaping up, iterating (as a follower) at twice the speed of level-party
, bringing it closer to classic-level
:
Published many-level
.
@vweevers any indication on many-level vs local redis perf?
Depends on what functionality you need. Without iterators, simple GET
and SET
commands suffice and can easily be benchmarked against Level modules. For iterators, you need hashes and/or sorted sets, or perhaps Redis Streams which I'm not familiar with, but either way the performance characteristics will be different. Buffer support will slow it down. Etc.
I got side tracked by a Node.js bug on Windows (https://github.com/nodejs/node/issues/42496) but that seems to be an edge case so I went ahead and published rave-level
.
abstract-level
(replacement forabstract-leveldown
and more)memory-level
(replacement formemdown
andlevel-mem
)level-mem
andmemdown
inLevel/community
level-read-stream
memory-level
for tests)engines.node
inpackage.json
classic-level
(replacement forleveldown
)nextv()
and_landed
logic should interactleveldown
inLevel/community
browser-level
(replacement forlevel-js
)level-js
inLevel/community
level
rocks-level
(replacement forrocksdb
andlevel-rocksdb
)leveldown
, copyclassic-level
, apply diffmany-level
(replacement formultileveldown
)rave-level
(replacement forlevel-party
, depends onlevel@8
)Side tasks:
level-web-stream
)