What conditions in the framework trigger cache scaling?

What conditions in the framework trigger cache scaling?

• A. Cache memory usage exceeding 100 GB.
• B. Operations per second exceed 1k.
• C. Memory exceeds 1 TB or ops/second exceed 100k.
• D. CPU usage exceeds 90%.

Answer: (C)

Cache scaling is driven by pressure on both memory capacity and workload demand. A well-designed framework watches how much data the cache holds and how fast requests are arriving. If memory usage grows beyond a large threshold, there’s a risk you’ll run out of space to store useful data, so scaling is triggered to add capacity. If the demand in requests per second grows beyond a high threshold, the current cache can become a bottleneck for serving data, so scaling is triggered to handle more load and maintain performance. The option that specifies either memory exceeding a very large limit or throughput exceeding a high limit captures both ways scaling might be needed, making it the best match. The other options focus on a single metric or on metrics (like CPU) that don’t directly indicate when the cache itself needs to scale.

Cache scaling is driven by pressure on both memory capacity and workload demand. A well-designed framework watches how much data the cache holds and how fast requests are arriving. If memory usage grows beyond a large threshold, there’s a risk you’ll run out of space to store useful data, so scaling is triggered to add capacity. If the demand in requests per second grows beyond a high threshold, the current cache can become a bottleneck for serving data, so scaling is triggered to handle more load and maintain performance. The option that specifies either memory exceeding a very large limit or throughput exceeding a high limit captures both ways scaling might be needed, making it the best match. The other options focus on a single metric or on metrics (like CPU) that don’t directly indicate when the cache itself needs to scale.