From: Thomas Lamprecht <t.lamprecht@proxmox.com>
To: Christoph Heiss <c.heiss@proxmox.com>
Cc: Proxmox VE development discussion <pve-devel@lists.proxmox.com>
Subject: Re: [pve-devel] [PATCH installer 0/2] expose zfs arc size setting for all products
Date: Tue, 6 Feb 2024 14:41:35 +0100 [thread overview]
Message-ID: <0534e55b-9876-4ae1-ba32-db9174be038a@proxmox.com> (raw)
In-Reply-To: <qk6xzsxehkmiauqv3qhs2sdvpp3frchkkbhhjea2xwxgdmqyfk@zn4okyfrzjaw>
Am 06/02/2024 um 14:25 schrieb Christoph Heiss:
> On Tue, Feb 06, 2024 at 01:49:36PM +0100, Thomas Lamprecht wrote:
>> That way it would stay dynamic, e.g., if one increased the memory of
>> a PBS or PMG instance, but one could also interpret that as bad thing,
>> especially if the MiB number was shown.
>
> Should this behaviour only apply to the PBS/PMG installer then? Or to
> PVE as well?
No, I'd keep PVE at the lower limit.
There it makes sense more sense over the default 50 % and as PVE is
more likely to be installed on bare metal, at least for permanent
production installations, it's also less likely that the amount of
memory changes.
>
>> For GTK we could just go for a placeholder text showing the number,
>> but there isn't really such a UX-mechanic available for the TUI one
>> AFAICT.
>
> Yeah, we'd need to implement placeholders for the TUI ourselves.
> Shouldn't be too hard tho, I got a rough idea mind how it be fitted in
> there.
As long as one can somewhat easily understand the meaning behind
that, it should be fine.
prev parent reply other threads:[~2024-02-06 13:41 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-30 10:01 Christoph Heiss
2023-11-30 10:01 ` [pve-devel] [PATCH installer 1/2] tui: expose arc size setting for zfs bootdisks " Christoph Heiss
2023-11-30 10:01 ` [pve-devel] [PATCH installer 2/2] proxinstall: " Christoph Heiss
2024-01-24 9:52 ` [pve-devel] [PATCH installer 0/2] expose zfs arc size setting " Christoph Heiss
2024-02-06 12:49 ` Thomas Lamprecht
2024-02-06 13:25 ` Christoph Heiss
2024-02-06 13:41 ` Thomas Lamprecht [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=0534e55b-9876-4ae1-ba32-db9174be038a@proxmox.com \
--to=t.lamprecht@proxmox.com \
--cc=c.heiss@proxmox.com \
--cc=pve-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