Hi,
Our production server seems to have some Mysql performance issues since migrating to Proxmox 1.8, Kernel 2.6.32. Mysql is version 5, and we have a database with millions of records in innodb with file per table.
As you can see here, our raid 5 (SAS) array is apparently not performing as it should do, particularly for fsyncs/second:
CPU BOGOMIPS: 85119.26
REGEX/SECOND: 986372
HD SIZE: 66.93 GB (/dev/mapper/pve-root)
BUFFERED READS: 49.66 MB/sec
AVERAGE SEEK TIME: 10.79 ms
FSYNCS/SECOND: 4.92
DNS EXT: 140.23 ms
I read somewhere that pveperf does not support LVM, yet the default install of Proxmox uses LVM on the root partition, which is what we have, so this doesn't make too much sense to me.
Can pveperf be relied upon when the root partition is LVM? If it is a reiliable measure, then has anyone seen such a remarkably low value for fsyncs per seconds, and if so, how did you fix it?
Thanks,
James
Our production server seems to have some Mysql performance issues since migrating to Proxmox 1.8, Kernel 2.6.32. Mysql is version 5, and we have a database with millions of records in innodb with file per table.
As you can see here, our raid 5 (SAS) array is apparently not performing as it should do, particularly for fsyncs/second:
CPU BOGOMIPS: 85119.26
REGEX/SECOND: 986372
HD SIZE: 66.93 GB (/dev/mapper/pve-root)
BUFFERED READS: 49.66 MB/sec
AVERAGE SEEK TIME: 10.79 ms
FSYNCS/SECOND: 4.92
DNS EXT: 140.23 ms
I read somewhere that pveperf does not support LVM, yet the default install of Proxmox uses LVM on the root partition, which is what we have, so this doesn't make too much sense to me.
Can pveperf be relied upon when the root partition is LVM? If it is a reiliable measure, then has anyone seen such a remarkably low value for fsyncs per seconds, and if so, how did you fix it?
Thanks,
James