Skip to content
This repository has been archived by the owner on Mar 19, 2024. It is now read-only.

Evaluate new storage engine for Archive node data #64

Open
diaswrd opened this issue Jan 20, 2023 · 1 comment
Open

Evaluate new storage engine for Archive node data #64

diaswrd opened this issue Jan 20, 2023 · 1 comment
Assignees
Labels

Comments

@diaswrd
Copy link

diaswrd commented Jan 20, 2023

We're currently in the process to upgrade the RN key-value store from badgerdb/v2 to badgerdb/v3. However, it became apparent that the read latency of this library may be too high for the amount of read operations we need to perform on this node when it's under high usage.

Part of this work is to study key-value store alternatives that are more efficient than badger when performing many read operations, with pebble being the current top contender as it has been tested previously in our new event-indexer.

Definition of done

Replace badgerdb by other key-value storage engine and test results in a production-like environment (maybe staging RN would be ideal for this) with use of heavy scripts (like fraud worker).

@diaswrd
Copy link
Author

diaswrd commented Jan 20, 2023

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