Optimize storage and usage of re-usable callback ids
Yury-Fridlyand opened this issue · 0 comments
Yury-Fridlyand commented
Describe the feature
List of freed callback IDs may grow up to 2e32 entries and occupy minimum 16 Gb of memory. We should optimize it to keep wrappers use low memory, but to be fast.
For example, we can store ranges of free callback IDs, instead of storing all numbers.
Also, existing python wrapper doesn't properly use _available_callbackIndexes as of now (524c084).
Use Case
No response
Proposed Solution
No response
Other Information
No response
Acknowledgements
- I may be able to implement this feature request
- This feature might incur a breaking change
Client version used
Environment details (OS name and version, etc.)
No response