since the mobile ui shares the Utils code with the desktop web ui, (but
not the proxmox-widget-toolkit) all methods used in constructors, etc.
there must be available in the mobile ui too.
We don't have any notification configuration options in the mobile ui,
and AFAIK we don't plan to add those t
On 9/19/24 16:57, Thomas Lamprecht wrote:
Am 19/09/2024 um 14:45 schrieb Dominik Csapak:
On 9/19/24 14:01, Thomas Lamprecht wrote:
Am 19/09/2024 um 11:52 schrieb Dominik Csapak:
by default libfuse2 limits writes to 4k size, which means that on writes
bigger than that, we do a whole write cycle
--- Begin Message ---
Hi Dominik,
For now the best course of action would be to post a message on our forums
(forums.veeam.com) in this subsection:
https://forums.veeam.com/kvm-rhv-olvm-proxmox-f62/
I am in the process of arranging some external bug-tracker (we don't have one
right now). If yo
On 9/23/24 14:00, Friedrich Weber wrote:
On 23/09/2024 11:17, Dominik Csapak wrote:
[...]
so i did some benchmarks (mostly disk writes) and wrote the short script
below
(maybe we can reuse that?)
8<
use strict;
use warnings;
use PVE::Tools;
my $size = shift;
sub get_bytes_written {
On 23/09/2024 11:17, Dominik Csapak wrote:
> [...]
> so i did some benchmarks (mostly disk writes) and wrote the short script
> below
> (maybe we can reuse that?)
>
> 8<
> use strict;
> use warnings;
>
> use PVE::Tools;
>
> my $size = shift;
>
> sub get_bytes_written {
> my $fh
Am 23/09/2024 um 13:27 schrieb Lukas Wagner:
> pve-manager has been bumped in the meanwhile, I guess we could now merge the
> remaining patches for pve-docs and proxmox-widget-toolkit?
> They still apply cleanly and a quick test also showed that everything still
> works as expected.
thanks for the
Changing the way we write files, can eliminate the exponential growth of
write amplification with files of up to 128KiB in size.
Right now we are using `PVE::Tools::file_set_contents`, which itself
uses `print`. And looking at the debug output we can see that this ends
up writing the file content
I also ran some benchmarks with the same script.
I created a VM with two virtual disks, (both on an LVM Thin storage)
installed PVE on one disk and set up an ext4 partition on the other.
I stopped pvestatd and pve-cluster,
```
systemctl stop pvestatd
systemctl stop pve-cluster
```
moved the pm
On 2024-07-22 19:36, Thomas Lamprecht wrote:
>> Lukas Wagner (5):
>> api: jobs: vzdump: pass job 'job-id' parameter
>> ui: dc: backup: allow to set custom job id in advanced settings
>> api: notification: add API for getting known metadata fields/values
>> ui: utils: add overrides for tra
