๊ฐ€์ž… ํ›„ ์ดˆ๋Œ€ ๋งํฌ๋ฅผ ๊ณต์œ ํ•˜๋ฉด ๋™์˜์ƒ ์žฌ์ƒ ๋ฐ ์ดˆ๋Œ€ ๋ณด์ƒ์„ ๋ฐ›์„ ์ˆ˜ ์žˆ์Šต๋‹ˆ๋‹ค.

cv usk
@cv_usk
AI / Software Research Notes AI Agent, LLMOps, MLOps, Software Architecture ๆŠ•็จฟใฏๅ€‹ไบบใฎๆ„่ฆ‹ใงใ™ใ€‚
๊ฐ€์ž… May 2026
258 ํŒ”๋กœ์ž‰ ์ค‘    228 ํŒฌ
๐Ÿ’ฐ Don't size caches for peakโ€”let them stretch and shrink with demand to cut cost. Google applies the classic ski rental problem to a production database. Title: Optimizing cloud economics with linear elastic caching URL: ๐Ÿ“ฆ Overview Linear elastic caching treats memory footprint as a variable cost that integrates over time, dynamically growing and shrinking cache size to match the workload. ๐ŸŽฏ The problem Cloud memory is expensive (serverless can charge up to $3/day per GiB). Fixed-size caches hit a "Goldilocks dilemma": too small hurts performance, too large wastes thousands on idle memory during low demand. ๐ŸŽฟ Method Each page faces a choice: "rent" (keep in RAM, paying continuous memory cost) or "buy the miss" (evict, risking latency/I/O later). A ski rental algorithm sets each page's TTL. The key result: eviction policy and rental duration can be optimized separately. ๐ŸŒฒ Implementation For Spanner, a lightweight shallow decision tree (compilable to C++) predicts the optimal TTL from data size, miss cost, and operation typeโ€”no heavy inference in the cache path. ๐Ÿ“‰ Results In production on Spanner: memory down 15.5%, misses up only 5.5%, TCO down ~5%, I/O impact a mere 0.5%. On public traces it consistently beat fixed-size (GDSF) baselines. #CloudComputing# #Algorithms#
๋” ๋ณด๊ธฐ