From: Santiago Castillo Oli <scastillo@aragon.es>
To: linux-bcache@vger.kernel.org
Subject: Best strategy for caching VMs storage
Date: Fri, 21 May 2021 13:56:16 +0200 [thread overview]
Message-ID: <08e95aaf-a5e5-fb32-31ea-ca35cc028fac@aragon.es> (raw)
Hi there.
I have a host running 4 VMs using qcow2 storage on a ext4 fs over HDD.
Each VM has 3 qcow files (system, data and swap). I know I have an I/O
bottleneck.
I want to use bcache with an SSD to accelerate disk access but I´m not
sure where should I put bcache on storage stack.
Should I use bcache on host or in guests?
Just one bcache backing device for a single (ext4) filesystem with all
qcow files there, or different bcache and backing devices for each qcow2
file?
Right know, I prefer qcow2 over thin-lvm for storage, but i could change
my mind if thin-lvm is a much better combination for bcache.
What would be the best strategy for caching VMs storage ?
Any recommendation, please?
Regards and thank you
--
___________________________________________________________
next reply other threads:[~2021-05-21 12:06 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-21 11:56 Santiago Castillo Oli [this message]
2021-05-21 12:29 ` Best strategy for caching VMs storage Matthias Ferdinand
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=08e95aaf-a5e5-fb32-31ea-ca35cc028fac@aragon.es \
--to=scastillo@aragon.es \
--cc=linux-bcache@vger.kernel.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