From: Greg KH <gregkh@linuxfoundation.org>
To: "taoyi.ty" <escape@linux.alibaba.com>
Cc: tj@kernel.org, lizefan.x@bytedance.com, hannes@cmpxchg.org,
mcgrof@kernel.org, keescook@chromium.org, yzaikin@google.com,
linux-kernel@vger.kernel.org, cgroups@vger.kernel.org,
linux-fsdevel@vger.kernel.org, shanpeic@linux.alibaba.com
Subject: Re: [RFC PATCH 0/2] support cgroup pool in v1
Date: Fri, 10 Sep 2021 08:01:50 +0200 [thread overview]
Message-ID: <YTr0zvythCIJk4Xb@kroah.com> (raw)
In-Reply-To: <a0c67d71-8045-d8b6-40c2-39f2603ec7c1@linux.alibaba.com>
On Fri, Sep 10, 2021 at 10:11:53AM +0800, taoyi.ty wrote:
> On 2021/9/8 下午8:37, Greg KH wrote:
>
> > Perhaps you shouldn't be creating that many containers all at once?
> > What normal workload requires this?
>
> Thank you for your reply.
>
>
> The scenario is the function computing of the public
>
> cloud. Each instance of function computing will be
>
> allocated about 0.1 core cpu and 100M memory. On
>
> a high-end server, for example, 104 cores and 384G,
>
> it is normal to create hundreds of containers at the
>
> same time if burst of requests comes.
So it is a resource management issue on your side, right? Perhaps
stagger the creation of new containers to allow the overall creation
time to be less?
thanks,
greg k-h
next prev parent reply other threads:[~2021-09-10 6:02 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-09-08 12:15 [RFC PATCH 0/2] support cgroup pool in v1 Yi Tao
2021-09-08 12:15 ` [RFC PATCH 1/2] add pinned flags for kernfs node Yi Tao
2021-09-08 12:15 ` [RFC PATCH 2/2] support cgroup pool in v1 Yi Tao
2021-09-08 12:35 ` Greg KH
[not found] ` <084930d2-057a-04a7-76d1-b2a7bd37deb0@linux.alibaba.com>
2021-09-09 13:27 ` Greg KH
2021-09-10 2:20 ` taoyi.ty
2021-09-10 2:15 ` taoyi.ty
2021-09-10 6:01 ` Greg KH
2021-09-08 12:35 ` [RFC PATCH 1/2] add pinned flags for kernfs node Greg KH
2021-09-10 2:14 ` taoyi.ty
2021-09-10 6:00 ` Greg KH
2021-09-08 12:37 ` [RFC PATCH 0/2] support cgroup pool in v1 Greg KH
2021-09-10 2:11 ` taoyi.ty
2021-09-10 6:01 ` Greg KH [this message]
2021-09-10 16:49 ` Tejun Heo
2021-09-13 14:20 ` Christian Brauner
2021-09-13 16:24 ` Tejun Heo
2021-09-08 16:35 ` Tejun Heo
2021-09-10 2:12 ` taoyi.ty
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=YTr0zvythCIJk4Xb@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=cgroups@vger.kernel.org \
--cc=escape@linux.alibaba.com \
--cc=hannes@cmpxchg.org \
--cc=keescook@chromium.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lizefan.x@bytedance.com \
--cc=mcgrof@kernel.org \
--cc=shanpeic@linux.alibaba.com \
--cc=tj@kernel.org \
--cc=yzaikin@google.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).