TE
科技回声
首页24小时热榜最新最佳问答展示工作
GitHubTwitter
首页

科技回声

基于 Next.js 构建的科技新闻平台,提供全球科技新闻和讨论内容。

GitHubTwitter

首页

首页最新最佳问答展示工作

资源链接

HackerNews API原版 HackerNewsNext.js

© 2025 科技回声. 版权所有。

Memory inside Linux containers (2014)

65 点作者 aburan28超过 7 年前

3 条评论

njs12345超过 7 年前
CPU also causes a similar problem - for instance Java (and lots of runtime Java libraries) use the number of available CPUs to decide how many threads to use for various tasks, which can cause terrible performance if you're giving a container 1 CPU of a 48 CPU server and it thinks all 48 are available - we encountered this at work recently and eventually bodged around it, but definitely a gotcha that this stuff isn't handled properly by runtimes yet.
评论 #15582096 未加载
评论 #15581915 未加载
评论 #15581979 未加载
评论 #15581913 未加载
tyingq超过 7 年前
&gt;Or why don’t free and top work in a Linux container?<p>You can use the lxcfs fuse filesystem to get that and a little more: <a href="https:&#x2F;&#x2F;github.com&#x2F;lxc&#x2F;lxcfs&#x2F;blob&#x2F;master&#x2F;README.md" rel="nofollow">https:&#x2F;&#x2F;github.com&#x2F;lxc&#x2F;lxcfs&#x2F;blob&#x2F;master&#x2F;README.md</a>
lgunsch超过 7 年前
I definitely don&#x27;t think systemd should be the go-to system for memory info. It already has too many functions, and does way too much.