-
Type:
Task
-
Resolution: Unresolved
-
Priority:
Major - P3
-
None
-
Affects Version/s: None
-
Component/s: None
-
None
-
Workload Resilience
-
Workload Resilience 2026-03-16, Workload Resilience 2026-03-30, Workload Resilience 2026-04-13
-
None
-
None
-
None
-
None
-
None
-
None
-
None
One case we expect to be able to overload the server since we have independent ticketing pools for read/write operations:
- saturate the system with read (or write) operations
- perform a surge of writes (or read, whatever is opposite to above) to overload the server.
We should use this to demonstrate the effectiveness of consolidating the reader/writer queues
- is related to
-
SERVER-120252 Consolidate the reader/write ticketholders into one
-
- Closed
-