Linux-EROFS Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: GRANGER Nicolas <nicolas.granger@cea.fr>
To: "linux-erofs@lists.ozlabs.org" <linux-erofs@lists.ozlabs.org>
Subject: Slow concurrent reads on mounted loopback images
Date: Thu, 21 Mar 2024 17:49:12 +0000	[thread overview]
Message-ID: <894a823bf73641e1a2f177cefea83dbd@cea.fr> (raw)

[-- Attachment #1: Type: text/plain, Size: 555 bytes --]

Hi erofs team,


I'm working on a small daemon that caches and mounts disk images containing datasets based on usage (https://github.com/CEA-LIST/scratch_manager).

My understanding is that this is a good use-case for EROFS. However, in my experience concurrent reads on loopback mounted disk images are rather slow.

I tested both squashfs and erofs images so I don't think it is specific to erofs, I just can't figure out where the bottleneck is. By any chance would you have any any tips to share on that subject?


Best,

Nicolas Granger

[-- Attachment #2: Type: text/html, Size: 1076 bytes --]

             reply	other threads:[~2024-03-21 18:16 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-03-21 17:49 GRANGER Nicolas [this message]
2024-03-22  2:49 ` Slow concurrent reads on mounted loopback images Gao Xiang

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=894a823bf73641e1a2f177cefea83dbd@cea.fr \
    --to=nicolas.granger@cea.fr \
    --cc=linux-erofs@lists.ozlabs.org \
    /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