Recent content by gz_jax

  1. G

    corosync modify jumbo problem

    The mtu of the current pve server cluster is 1500 by default. We want to change the mtu of the pve cluster to 9000. We migrate the virtual machines one by one in the test environment to modify the mtu. The cluster and ceph are all normal, but in the production environment we found the node after...
  2. G

    community version limits 32 nodes per cluster

    We found the desired answer through the link you shared, thanks.
  3. G

    [SOLVED] kvm read ceph single thread limit ?

    It ’s actually a misunderstanding, because it is found that the HDD disk is used, which is the case for random read performance
  4. G

    [SOLVED] kvm read ceph single thread limit ?

    Thanks, we found the problem ourselves
  5. G

    community version limits 32 nodes per cluster

    Regarding the pve community version, each cluster has a limit of 32 nodes. I tried more than 32 nodes and they can also be added to use. If it is used in this way, will there be failures or restrictions?
  6. G

    [SOLVED] kvm read ceph single thread limit ?

    Hello : I recently encountered a problem with random read iops when performing performance tests. The scene I built is: pve5.4 + ceph 12.2.12 3 hosts, each host 1ssd + 3hdd (ssd is used for db and wal, hdd is osd) KVM's disk will enable cache = write back mode, and select VirtIO SCSI single Zh...

About

The Proxmox community has been around for many years and offers help and support for Proxmox VE, Proxmox Backup Server, and Proxmox Mail Gateway.
We think our community is one of the best thanks to people like you!

Get your subscription!

The Proxmox team works very hard to make sure you are running the best software and getting stable updates and security enhancements, as well as quick enterprise support. Tens of thousands of happy customers have a Proxmox subscription. Get yours easily in our online shop.

Buy now!