Join us at ScyllaDB LIVE, instructor-led NoSQL training sessions | June 18
Register now

Multiple Isolated Workloads

9 min to complete

OSS Service levels don’t isolate workloads, having two sessions with different configurations will not work as expected
Batch workloads can enlarge the queues and overall latencies
Interactive workloads will be starved and have requests dropped
Multiple interactive workloads will compete for resources, and ones with lower timeouts will be starved.
It can still be used alternately however
Each service level has its own queue
Additional property for service levels: shares
Shares are relative to each other
Determine priority for resources in the presence of resource conflict:

  • CPU
  • Internal Concurrency
  • IO
  • Memory

Examples of Isolation scenarios:

  • A critical workload that can’t be starved by others
  • Different “classes” of users should get different SLAs (Service Level Agreement)
  • You would like to start another service whose effect on the system is unknown – gradually increase priority and find the sweet spot
  • Isolating table writes that have, Materialized Views (writes pressure, especially on memory, is roughly a factor of the number of views)