We seem to be having problems with QB getting into a state where it keep crunching numbers using 1700% of cpu on a 24 cpu machine, then losing gui (nginx reporting bad gateway).
We have 40 agents, some 3000 configurations of which about 500 are active but at the time it happens the use is very light, maybe 1 or 2 builds running. It appears that there is some cumulative effect taking place. It looks as though it is running out of memory and does not garbage collect. The decline comes quickly, once slowness is noticed, it takes about 15min to lose gui after several day of normal operations.
We have:
wrapper.java.initmemory=2048
wrapper.java.maxmemory=12216
There is 24G memory on the machine, we could allocate more to QB but we're wondering if it would only delay the problem without fixing.
We run qb 8.0.11