Le 09/03/2023 à 12:34, Daniel Watford a écrit :
Difficulties experienced along the way:
The biggest problem we hit was a capacity issue on the OFBiz project's VM,
ofbiz-vm1.apache.org.
A good rule of thumb seemed to be that an OFBiz demo instance consumed
around 2GB of RAM. Judicious use of memory and cpu limits on the containers
to be deployed on ofbiz-vm1 mean we could squeeze a container instance of
OFBiz alongside the existing 3 demo sites and still fit into the total 8GB
of RAM available on the host.
Everything seemed to be going well… until! An OFBiz demo instance would
consume around 2GB of RAM, but to build that instance would take much more
- perhaps another 2GB. OFBiz demo instances are rebuilt daily at 03:00 UTC
and suddenly these rebuild processes - which would normally complete in a
few minutes - were taking hours to run. The system was under such heavy
load, presumably from all the garbage collecting and swapping, that it was
unresponsive to web requests and SSH connections.
On Friday 10th February INFRA-24185 was raised, requesting an additional
4GB of RAM for ofbiz-vm1. INFRA approved the request and plans were made to
shut down the VM to perform the upgrade the following Monday. However the
03:00 UTC scheduled rebuild didn't agree with the plan!
The next day (Saturday 11th February), due to the 03:00 rebuild, the VM was
unresponsive again (
https://lists.apache.org/thread/dh0dp8f3n8jyy8n3jbho7vsghy42f41f). INFRA
shut down the VM for us in response and performed the upgrade ahead of
schedule. They upgraded us from a 2vCPU 8GB VM to 8vCPU 32GB VM. A 4-times
increase in compute and memory - an unexpected and very much appreciated
upgrade!
Thanks Daniel,
I just want to add that we crossed another quite weird issue reported at
https://issues.apache.org/jira/browse/INFRA-24303
"brianb user (Brian Behlendorf) is weirdly running the trunk demo on
ofbiz-vm1.apache.org VM."
It's a random issue. We have no solution for now.
Jacques
