msarnowicz

8 ms·

1. 1.▲
   by msarnowicz 1y ago

   I am glad you found this useful!
2. 2.▲
   by msarnowicz 1y ago

   I think so, too!
3. 3.▲
   by msarnowicz 1y ago

   This is a very valid scenario, however, one that is not yet fully baked into this implementation. But, as mentioned, this is a starting point. We want to hear feedback and see customers' workloads on Burstables first. The main challeng
4. 4.▲
   by msarnowicz 1y ago

   Thank you very much, I appreciate your comment.
5. 5.▲
   by msarnowicz 1y ago

   Thanks for the kind words. Even if you are not building a cloud service, I think it is good to understand how the underlying layer works and what are the knobs and the limits of the platform. I could see a use case where two or more proces
6. 6.▲
   by msarnowicz 1y ago

   Reading through the description of how cgroups are used in Kubernetes, I can see some similarities and some differences as well. It is interesting to compare the approaches. We chose not to use cpu.weight, and instead divide the host explic
7. 7.▲
   by msarnowicz 1y ago

   Thank you, that is a good perspective, too!
8. 8.▲
   by msarnowicz 1y ago

   Hey, author here. Please AMA. I came into the Linux world via Postgres, and this was an interesting project for me learning more about Linux internals. While cgroups v2 do offer basic support for CPU bursting, the bursts are short-lived, a
9. 9.▲
   Building Burstables: CPU slicing with cgroups(ubicloud.com)

   130 points by msarnowicz 1y ago|23 comments