Although it is nice that there is work arounds for the DNS spikes with either nscd or the in-process DNS cache, i think the DNS spikes are a symptom of a whole different issue.

I think we can safely assume that each DNS lookup is corresponding to one attempt at establishing a TCP connection then there is some code somewhere that spawns an awfull lot of short lived connections instead of reusing / pooling them - with all the issues that follows in that area (insufficient ulimit NOFILE, connections in TIME_WAIT/exhausting of client ports etc)

@lematz
In the first picture of "hostname and dns configuration":
It doesn't look like you have any double colon '::' in the first 2 entries but you have them in all fields on the last picture

@Andi79
Is the problem occurring both when the vm's are on HDD and on SSD storage or only on HDD ?

Seems like it's also reported upstream
https://bugs.xenserver.org/projects/XSO/issues/XSO-1021

Although it is nice that there is work arounds for the DNS spikes with either nscd or the in-process DNS cache, i think the DNS spikes are a symptom of a whole different issue.

I think we can safely assume that each DNS lookup is corresponding to one attempt at establishing a TCP connection then there is some code somewhere that spawns an awfull lot of short lived connections instead of reusing / pooling them - with all the issues that follows in that area (insufficient ulimit NOFILE, connections in TIME_WAIT/exhausting of client ports etc)

@lematz
In the first picture of "hostname and dns configuration":
It doesn't look like you have any double colon '::' in the first 2 entries but you have them in all fields on the last picture

https://github.com/ronivay/XenOrchestraInstallerUpdater has just added experimental support for provisioning a XO proxy

@jmccoy555 Could I pursuade you to make a post, describing your setup and summarizing any findings ?

@stormi whats the opinion on using the new gluster & ceph drivers for a hyper converged solution? Ok / should be ok but not tested / not recommended ??

You do need a lot of virtual memory for build but you can get by with 2GB ram + 4 GB swap if you tell nodejs to limit it self, by setting

 export NODE_OPTIONS='--max-old-space-size=3072'            

before starting the build process