I notice in our environment when having lots of vms using "client" mode,
vSPC.py very quickly starts to use up more and more memory and eventually
crashes (after minutes). Using the forked version of vSPC.py below it lasts
a lot longer but still eventually crashes (a few hours). Top output shows
both increasing memory usage.
I have also mentioned this at the vSPC.py fork issues page here
Would anyone know how to stop vSPC.py constantly increasing memory usage
when vms are set to "client" mode. I assume theres a memory leak in there
somewhere. Of course we could go through and set all vms set to "server"
mode but would be great if vSPC.py was able to handle this situation also
for robustness reasons.
Hi,
I notice in our environment when having lots of vms using "client" mode,
vSPC.py very quickly starts to use up more and more memory and eventually
crashes (after minutes). Using the forked version of vSPC.py below it lasts
a lot longer but still eventually crashes (a few hours). Top output shows
both increasing memory usage.
I have also mentioned this at the vSPC.py fork issues page here
https://github.com/isnotajoke/vSPC.py/issues/19
Would anyone know how to stop vSPC.py constantly increasing memory usage
when vms are set to "client" mode. I assume theres a memory leak in there
somewhere. Of course we could go through and set all vms set to "server"
mode but would be great if vSPC.py was able to handle this situation also
for robustness reasons.
Regards,
Mark