Add crud storage metrics
Open
Nobody has claimed this yet.
3sp
customer
feature
- Dominant language
- Lua
- Stars
- 43
- Forks
- 17
- Avg merge
- 28m
- Merged PRs (30d)
- 2
Description
We have a problem finding queries that parse a lot of tuples on storage.
- It could be a problem if query is too long (netbox timeout raise error and router will get nothing if batch_size huge or not certain)
- Or there a lot of tuples are looked up on storage, but return a few on router
Reproducer with netbox timeout:
- Create space with non unique index (bad_index)
- Insert ~1_000_000 tuples with the same field value (bad_value) for non unique index (bad_index)
- Start fiber with requests by pk
- Run request with condition where
bad_index key == bad_value
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by tracing the CRUD request path for requests by primary key and the condition bad_index key == bad_value; the issue does not name files, tests, or an entry point. Use the provided million-tuple reproducer to investigate storage work versus tuples returned to the router, then confirm which metrics and completion criteria are agreed before implementing.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- lua
- Domain
- databases
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100