archive mirror
 help / color / mirror / Atom feed
From: Miklos Szeredi <>
To: garyhuang <>
Cc: "" <>
Subject: Re: Overlayfs performance issue
Date: Thu, 21 Jan 2021 08:45:33 +0100	[thread overview]
Message-ID: <> (raw)
In-Reply-To: <>

On Wed, Jan 20, 2021 at 11:54 PM garyhuang <> wrote:
> Hi Miklos,
> Have you ever come into this?
> 1. dockerd with overlay2
>    a. Running nginx in container mounting the host directory which contains the file to be accessed (docker -v xxx:xxx)
>    b. Running nginx in container mounting the host file directly
>    The RPS varies too much (RPS(a) < RPS(b)), the more the workers are, the bigger the discount is
> 2. dockerd with devicemapper
>    Running nginx in container with both the same mounting scenarios, the RPS is not discounted
> 3. nginx on host, no performance discounted too. The RPS equals to container with devicemapper.
> It is kernel related with big extra spinlock consumption observed by perf when running dockerd with overlayfs even the file is mounted from outside host path.

It's not clear where the contention is coming from.  Can you get some
detail from the perf trace where we can see which overlayfs functions
are involved?


           reply	other threads:[~2021-01-21  7:47 UTC|newest]

Thread overview: expand[flat|nested]  mbox.gz  Atom feed
 [parent not found: <>]

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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to='' \ \ \ \

* 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).