Skip to content

Commit

Permalink
[rfc] Unresolved questions
Browse files Browse the repository at this point in the history
  • Loading branch information
didierofrivia committed Feb 9, 2024
1 parent 789db9e commit f9e8640
Showing 1 changed file with 5 additions and 3 deletions.
8 changes: 5 additions & 3 deletions rfcs/0000-limitador-multithread-inmemory.md
Original file line number Diff line number Diff line change
Expand Up @@ -220,9 +220,11 @@ that the service operates correctly and efficiently.
# Unresolved questions
[unresolved-questions]: #unresolved-questions

- What parts of the design do you expect to resolve through the RFC process before this gets merged?
- What parts of the design do you expect to resolve through the implementation of this feature before stabilization?
- What related issues do you consider out of scope for this RFC that could be addressed in the future independently of the solution that comes out of this RFC?
- How to balance the need for strict adherence to defined limits with the desire to maximize throughput in the
multi-threaded implementation of Limitador?
- What are the best concurrency control mechanisms and data structures to use for storing and updating counter data
across multiple threads?
- What would be the algorithm to use to balance the _Accuracy_ and _Throughput_ modes?

# Future possibilities
[future-possibilities]: #future-possibilities
Expand Down

0 comments on commit f9e8640

Please sign in to comment.