From: Jorge Boncompte <jbonor@gmail.com>
To: pve-user@lists.proxmox.com
Subject: Re: [PVE-User] PBS : is dirty-bitmap really accurate ?
Date: Thu, 23 Jul 2020 11:00:55 +0200 [thread overview]
Message-ID: <3ce2e15f-9b92-64ce-af55-a21fa46dc5d6@gmail.com> (raw)
In-Reply-To: <141180690.77175.1595487181182.JavaMail.zimbra@fws.fr>
El 23/7/20 a las 8:53, Daniel Berteaud escribió:
> ----- Le 23 Juil 20, à 8:43, Fabian Grünbichler f.gruenbichler@proxmox.com a écrit :
>
>> possibly you haven't upgraded to pve-qemu-kvm 5.0-11 (or your VM hasn't
>> been restarted yet since the upgrade):
>>
>> https://git.proxmox.com/?p=pve-qemu.git;a=commit;h=f257cc05f4fbf772cad3231021b3ce7587127a1b
>
> I'm running pve-qemu-kvm 5.0.0-11, and all the implied VM have been either (cold) rebooted, or migrated.
>
>>
>> the bitmap has a granularity of 4MB, so depending on the activity inside
>> you can see quite a bit of amplification. also writing and then
>> zeroing/reverting again to the old content would leave a mark in the
>> bitmap without permanently changing the contents.
>>
>
> Yes, I'd expect some amplification, but not that much. For my Zabbix server, it's nearly canceling all the benefit of using a dirty bitmap.
> One thing I've noted, is that I get expected values at least for one guest, running PfSense (where I get ~150MB of dirty blocks each days). Most of my other VM are Linux, I'll check if it could be related to the atime update or something
Hi, does the dirty-bitmap take somehow into account block discarding
and zeroing? Because the other thing I would look for in this case is
for a fstrim firing every day.
>
> Cheers,
> Daniel
>
next prev parent reply other threads:[~2020-07-23 9:21 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-22 16:40 Daniel Berteaud
2020-07-23 6:43 ` Fabian Grünbichler
2020-07-23 6:53 ` Daniel Berteaud
2020-07-23 9:00 ` Jorge Boncompte [this message]
2020-07-23 9:34 ` Fabian Grünbichler
2020-07-23 9:40 ` Daniel Berteaud
2020-07-23 21:59 ` Roland
2020-07-24 7:02 ` Daniel Berteaud
2020-07-24 7:54 ` Ronny Aasen
2020-07-26 9:24 ` Mark Schouten
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=3ce2e15f-9b92-64ce-af55-a21fa46dc5d6@gmail.com \
--to=jbonor@gmail.com \
--cc=pve-user@lists.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox