From: Gao Xiang <hsiangkao@linux.alibaba.com>
To: GRANGER Nicolas <nicolas.granger@cea.fr>,
"linux-erofs@lists.ozlabs.org" <linux-erofs@lists.ozlabs.org>
Subject: Re: Slow concurrent reads on mounted loopback images
Date: Fri, 22 Mar 2024 10:49:50 +0800 [thread overview]
Message-ID: <6e58615b-b06e-4144-9a13-eea61c358a8f@linux.alibaba.com> (raw)
In-Reply-To: <894a823bf73641e1a2f177cefea83dbd@cea.fr>
Hi GRANGER,
On 2024/3/22 01:49, GRANGER Nicolas wrote:
> 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 <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?
Thanks for the information. I don't know more about "scratch_manager",
but does "scratch_manager" really use loopback devices? if yes, which
kernel version are you using, and could you try with loop direct-io
mode?
Later the EROFS project will land native solutions for dataset and AI
models and we will evaluate this use cases formally.
Thanks,
Gao Xiang
>
>
> Best,
>
> Nicolas Granger
>
prev parent reply other threads:[~2024-03-22 2:50 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-21 17:49 Slow concurrent reads on mounted loopback images GRANGER Nicolas
2024-03-22 2:49 ` Gao Xiang [this message]
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=6e58615b-b06e-4144-9a13-eea61c358a8f@linux.alibaba.com \
--to=hsiangkao@linux.alibaba.com \
--cc=linux-erofs@lists.ozlabs.org \
--cc=nicolas.granger@cea.fr \
/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 read-only IMAP folder(s) and NNTP newsgroup(s).