Hallo Bellm,
Wie hast du denn upgedatet?
mit install-script.
Also ich habe noch über apt ein update gefahren und musste dann setip
ich denke, dass Problem 1 und 2 wohl Bedienfehler der NUtzer sind: da
Heute abend mal Server durchstarten…
Gestern Nacht gemacht …
Hat eigentlich mal jemand das hier durchgeführt?
offen 10:53AM - 20 Jan 21 UTC
geschlossen 12:01AM - 25 Feb 21 UTC
type: enhancement
target: performance
module: client
**Describe the issue**
We use 12-core AMD Ryzen CPUs (Ryzen 9 3900 @ ~4,1 GHz) … in a bunch of our BBB servers. Until recently, the bottleneck mostly was NodeJS hitting `120%` CPU usage and sticking there for a few minutes until load by users is reduced substantially again. This usually happened shortly after NodeJS reached `60%` average CPU usage in htop. After some code reading and debugging, we managed to improve performance of NodeJS by approximately 40%, so that our servers can now comfortably handle up to **600** concurrent users per server (mostly students, 50% have webcams enabled, typing indicator enabled but limited to one indicator update per second) instead of **425** users previously on the same hardware with the same settings.
Now the question is: how / what files should I change in the repository in a PR so that this will be part of the next BBB 2.2.x release?
**BBB version (optional):**
BigBlueButton Server 2.2.31
Recording disabled, very little amounts of logging, typing indicator updates limited to once every second, whiteboard mouse hover position updates limited to once every 150ms, 3 kurento processes.
**Changes applied:**
1. Open `/usr/share/meteor/bundle/systemd_start.sh`
2. Replace `development` by `production`
3. Replace the last line by `PORT=3000 /usr/share/$NODE_VERSION/bin/node --max-old-space-size=4096 --max_semi_space_size=128 main.js`
4. Wait for when no users are using the server any more, then execute `service bbb-html5 restart`
**Additional information**
Before we applied this change, NodeJS occasionally crashed every few days showing `FATAL ERROR: CALL_AND_RETRY_LAST Allocation failed - JavaScript heap out of memory` when trying to parse some JSON objects. Changing the max-old-space-size from the default 1,5GB to 3GB fixed those issues, but raising the limit to 4 GB helped reduce the total amount of time spent in Garbage Collection, while not raising the interruption time too much (the GC does stop-the-world garbage collection).
The `--max_semi_space_size=128` was the important key to improving the amount of concurrent users.
PS: If you currently use our [NodeJS CPU monitor/exporter](https://gitlab.senfcall.de/senfcall-public/nodejs-cpu-monitor), you'll have to update the package and then restart its service.
40% mehr Nutzer … das ist der Hammer.
LG
Holger