From: "DERUMIER, Alexandre via pve-devel" <pve-devel@lists.proxmox.com>
To: "pve-devel@lists.proxmox.com" <pve-devel@lists.proxmox.com>,
"f.ebner@proxmox.com" <f.ebner@proxmox.com>,
"f.gruenbichler@proxmox.com" <f.gruenbichler@proxmox.com>
Cc: "DERUMIER, Alexandre" <alexandre.derumier@groupe-cyllene.com>
Subject: Re: [pve-devel] [PATCH qemu-server] qcow2: increase cache-size to 1GB
Date: Fri, 3 Oct 2025 14:05:23 +0000 [thread overview]
Message-ID: <mailman.640.1759502306.390.pve-devel@lists.proxmox.com> (raw)
In-Reply-To: <afb7881b-1e9d-4446-bf9e-5783902b90eb@proxmox.com>
[-- Attachment #1: Type: message/rfc822, Size: 13292 bytes --]
From: "DERUMIER, Alexandre" <alexandre.derumier@groupe-cyllene.com>
To: "pve-devel@lists.proxmox.com" <pve-devel@lists.proxmox.com>, "f.ebner@proxmox.com" <f.ebner@proxmox.com>, "f.gruenbichler@proxmox.com" <f.gruenbichler@proxmox.com>
Subject: Re: [pve-devel] [PATCH qemu-server] qcow2: increase cache-size to 1GB
Date: Fri, 3 Oct 2025 14:05:23 +0000
Message-ID: <7fc8439e1fb61c341e637daae60362ecf0a36f79.camel@groupe-cyllene.com>
> >
>>But the max value might even be reached for relatively small disks.
>>And
>>there are users that have a lot of VMs with rather small disks. For
>>them, the increase in memory consumption would be quite big I
>>suppose!
Currently the qemu default cache size is 32MB , enough to handle 256 GB
images.
so, I'm not sure It'll make so much difference. even if user have a lot
of 512GB images (100images for example), 50TB, it'll add an extra
100x32MB = 3GB memory .
sure, if user have 100 imagesx8TB, 800TB stockage on 1 host, It'll
increase memory to around 100x1GB = 100Gb memory. ^_
>>Yes, I'd also be in favor of using something calculated from the
>>size.
>>We could additionally add a drive configuration option to override
>>the
>>value if we really want to.
and if we use something calculated from the size of the disk, it'll not
help to limit global memory usage.
[-- Attachment #2: Type: text/plain, Size: 160 bytes --]
_______________________________________________
pve-devel mailing list
pve-devel@lists.proxmox.com
https://lists.proxmox.com/cgi-bin/mailman/listinfo/pve-devel
prev parent reply other threads:[~2025-10-03 14:38 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-08-13 13:46 Alexandre Derumier via pve-devel
2025-08-13 14:25 ` Fabian Grünbichler
2025-08-14 11:10 ` DERUMIER, Alexandre via pve-devel
2025-08-14 14:14 ` DERUMIER, Alexandre via pve-devel
2025-10-02 9:39 ` Fiona Ebner
2025-10-03 8:20 ` Fiona Ebner
2025-10-03 14:05 ` DERUMIER, Alexandre via pve-devel [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=mailman.640.1759502306.390.pve-devel@lists.proxmox.com \
--to=pve-devel@lists.proxmox.com \
--cc=alexandre.derumier@groupe-cyllene.com \
--cc=f.ebner@proxmox.com \
--cc=f.gruenbichler@proxmox.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.