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
Is your feature request related to a problem? Please describe.
A clear and concise description of what the problem is. Ex. I'm always frustrated when [...]
Describe the solution you'd like
A clear and concise description of what you want to happen.
Describe alternatives you've considered
A clear and concise description of any alternative solutions or features you've considered.
Use case
Why is this important (helps with prioritizing requests)?
The text was updated successfully, but these errors were encountered:
Calculates the total exact series cardinality in the database.
Segments that cardinality by measurement, and emits those cardinality values.
Emits total exact cardinality for each shard in the database.
Segments for each shard the exact cardinality for each measurement in the shard.
Optionally limits the results in each shard to the “top n”.
The report-tsi command is primarily useful when there has been a change in cardinality and it’s not clear which measurement is responsible for this change, and further, when that change happened. Estimating an accurate cardinality breakdown for each measurement and for each shard will help answer those questions.
Syntax
cnosdb_inspect report-tsi --db-path [ options ]
Options
Optional arguments are in brackets.
--db-path
The path to the database.
[ --top ]
Limits the results to the top specified number within each shard.
Performance
The report-tsi command uses simple slice/maps to store low cardinality measurements, which saves on the cost of initializing bitmaps. For high cardinality measurements the tool uses roaring bitmaps, which means we don’t need to store all series IDs on the heap while running the tool. Conversion from low-cardinality to high-cardinality representations is done automatically while the tool runs.
Is your feature request related to a problem? Please describe.
A clear and concise description of what the problem is. Ex. I'm always frustrated when [...]
Describe the solution you'd like
A clear and concise description of what you want to happen.
Describe alternatives you've considered
A clear and concise description of any alternative solutions or features you've considered.
Use case
Why is this important (helps with prioritizing requests)?
The text was updated successfully, but these errors were encountered: