@george1421 said in High load average when capturing image:
Lets start debugging this by changing the fog client check in time from 300 seconds to 900 seconds. This will change the check in time from 5 minutes to 15 minutes. This is done under the fog settings -> fog configuration menu. Wait about 30 minutes and see if your static load on the fog server decreases.
Do you still want me to try this solution?
Now you said this was a VM. with 8 vCPU and 16GB of ram. How does that compare with the physical machine the VM is running on? Over committing vCPU is bad for the VM’s performance too. I would think that 2 vCPU should be adequate for 100 client computers. I understand with your high cpu usage you might think adding more vCPUs would help, but it looks like from your first screen shot only 2 cores are really taking the load.
The VM uses all of the hypervisor’s RAM and CPUs. It is a hypervisor dedicated to the Fog server. We have a Proxmox cluster of Fog servers which allows us to have high availability.
I reduced the vCPUs to 2 (1 socket, 2 cores) but it requires a restart to be effective. I will keep you informed.
Tell me a bit more about your hypervisor server. How many network interfaces does it have. Are they teamed 1 GbE or a 10GbE network interface.
It has two 1Gb/s network interfaces. One is used for the administration of the proxmox server itself and the other is used for VM traffic.
On your NAS is that a single 1GbE interface or do you have them teamed also?
It has 2x10Gb/s teamed network interfaces.
How many other VMs are running on this hypervisor host?
How many hypervisor hosts are using this single NAS?
On the NAS, what is the disk subsystem? raid-10, raid-6?
During a fog image capture, what does the nas CPU and disk usage look like?
A Fog capture does not significantly affect the resources of the NAS.