From: Thomas Lamprecht <t.lamprecht@proxmox.com>
To: Proxmox Backup Server development discussion
<pbs-devel@lists.proxmox.com>,
Dominik Csapak <d.csapak@proxmox.com>
Subject: Re: [pbs-devel] [PATCH proxmox-backup 4/5] ui: datastore/Summary: change storage axis to power of two
Date: Tue, 17 May 2022 10:32:27 +0200 [thread overview]
Message-ID: <78792ee7-bea9-0d62-873e-7530b0032089@proxmox.com> (raw)
In-Reply-To: <ef082bbd-c673-3530-14fd-6fa73c68ea36@proxmox.com>
Am 5/17/22 um 10:20 schrieb Dominik Csapak:
> On 5/17/22 10:09, Thomas Lamprecht wrote:
>> Am 5/17/22 um 08:52 schrieb Dominik Csapak:
>>> so that the unit is the same as in the overview panel on the same page
>>>
>>
>> This missed the administration Server Status RRD for the root disk, but actually
>> this needs to be the other way around, I switched to power of two for all memory
>> graphs in PVE 7.0 and the storage one to power of ten, at least the pve storages,
>> the root HD one in the node summary is still wrong (will fix).
>>
>>
>
> yeah you're right, i forgot about the administration rrd panels.
>
> any reason why we use different units for disk vs memory?
because they're two different things usage wise, due to memory being tied to the CPU
a power of two address and thus size comes just naturally, and the industries tradition
is to advertised and base 10 for storage, where it doesn't really matter from a technical
POV but from a marketing (bigger number for SI)
> imho storage also often uses binary units.
cannot remember to see any disk sold with a advertised size formatted as power of
two, and users may be confused if they see less capacity than the disk promised.
>
> (`lvs`/`lsblk` uses that in it's default output, we use it
> for vm/ct disks, etc.)
we show SI units for the disk panel, it should rather fit that, also we nowhere
show LVM in PBS, nor will we ever be able to show the same thing that all filesystem/
olume manager techs do, IMO also a bogus goal, what's important is to be consistent,
which we never really had, it was always a weird mix of either, and especially the
base ten for memory, which results in values on axis that just don't line nicely
up has done it for me for the 6.4 release there.
next prev parent reply other threads:[~2022-05-17 8:32 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-17 6:52 [pbs-devel] [PATCH proxmox-backup 1/5] tape/pool_writer: give proper types to 'contains_snapshot' Dominik Csapak
2022-05-17 6:52 ` [pbs-devel] [PATCH proxmox-backup 2/5] ui: form/NamespaceSelector: show proper emptyText Dominik Csapak
2022-05-17 11:41 ` [pbs-devel] applied: " Thomas Lamprecht
2022-05-17 6:52 ` [pbs-devel] [PATCH proxmox-backup 3/5] ui: form/DataStoreSelector: show maintenance mode in selector Dominik Csapak
2022-05-17 8:53 ` [pbs-devel] applied: " Thomas Lamprecht
2022-05-17 6:52 ` [pbs-devel] [PATCH proxmox-backup 4/5] ui: datastore/Summary: change storage axis to power of two Dominik Csapak
2022-05-17 8:09 ` Thomas Lamprecht
2022-05-17 8:20 ` Dominik Csapak
2022-05-17 8:32 ` Thomas Lamprecht [this message]
2022-05-17 6:52 ` [pbs-devel] [PATCH proxmox-backup 5/5] ui: SyncView/SyncJobEdit: unify store/namespace gettext Dominik Csapak
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=78792ee7-bea9-0d62-873e-7530b0032089@proxmox.com \
--to=t.lamprecht@proxmox.com \
--cc=d.csapak@proxmox.com \
--cc=pbs-devel@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