-
Notifications
You must be signed in to change notification settings - Fork 669
Closed
Labels
P:storage-optimizationPriority: Give operators greater control over storage and storage optimizationPriority: Give operators greater control over storage and storage optimizationstoragetrackingA complex issue broken down into sub-problemsA complex issue broken down into sub-problems
Description
Was tendermint/tendermint#9750
In order to simplify CometBFT's storage mechanism, we need to first establish what typical usage patterns look like. Given that we intend on offloading event indexing, this effort should focus on understanding and gathering data on what the storage workloads look like for specific use cases. This is a tracking issue for everything that needs to be completed in order to end up with a set of requirements for a database that will serve as CometBFT's storage mechanism.
The requirements can only be established if we have a testing setup with which we can measure the current performance and bottlenecks. This setup will also serve as a baseline to measure any improvements done to the storage layer.
- Write tests and build a testing environment to test the storage layer
- Understand the workload: What data are we storing, in what format
- Establish and implement the relevant metrics to understand storage workloads #46
- Storage evaluation baseline: measure and report current storage related behaviour of CometBFT #67
Metadata
Metadata
Assignees
Labels
P:storage-optimizationPriority: Give operators greater control over storage and storage optimizationPriority: Give operators greater control over storage and storage optimizationstoragetrackingA complex issue broken down into sub-problemsA complex issue broken down into sub-problems