hostname/port as an environment variable

[pix-as]

hostname/port as an environment variable

[olivierlambert]

Hi,

Before trying to go there, it might be interesting to know your setup and why you are hitting single-thread per limit, knowing that for backup, we are already using workers. So it shouldn't be a very common case to hit it.

[pix-as]

The setup is xen orchestra installed from sources (master) - with debian 11 and nodejs 18.
I can reproduce the issue with 2 tabs viewing 100 VMs with statistics at once and trying to browse with another tab.
The load is basically on one thread. This is a simulated environment:

The productive environment has at times very(!) bad response time.

[olivierlambert]

I suggest to open a support ticket for your production environment, so we can take a look remotely (via our support tunnel) and identify more easily your bottlenecks.

[julien-f]

If running with different system users, you can provide various configuration in ~/.config/xo-server/config.toml, and put the shared config in /etc/xo-server/config.toml.

But, just to let you know that xo-server is mainly intended to be run as a single service as root, you may need to tweak the config further and have some specific issues.

[pix-as]

Our current workaround is to run several docker container of that repository:
https://github.com/Ezka77/xen-orchestra-ce

We will introduce another workaround due to a slow-bug with mass-statistics on the server or vm page. The longer the server runs and the more often those statistics are generated, the slower that instance gets over days.

[olivierlambert]

AFAIK, this stat bug is now fixed.

[pix-as]

Thanks - I'll update our xen orchestra docker container accordingly.