bigbluebutton-Github/build/packages-template/bbb-webrtc-sfu/bbb-webrtc-sfu.service

[Unit]
Description=BigBlueButton WebRTC SFU
Wants=redis-server.service
After=syslog.target network.target freeswitch.service bbb-webrtc-recorder.service kurento-media-server.service redis-server.service
PartOf=bigbluebutton.target

[Service]
WorkingDirectory=/usr/local/bigbluebutton/bbb-webrtc-sfu
ExecStart=/usr/bin/node server.js
Restart=always
SyslogIdentifier=bbb-webrtc-sfu
User=bigbluebutton
Group=bigbluebutton
Environment=NODE_ENV=production
Environment=NODE_CONFIG_DIR=/etc/bigbluebutton/bbb-webrtc-sfu/:/usr/local/bigbluebutton/bbb-webrtc-sfu/config/
Environment=ALLOW_CONFIG_MUTATIONS=true
CPUSchedulingPolicy=fifo
Nice=19

[Install]
WantedBy=multi-user.target bigbluebutton.target
initial public version 2021-08-13 18:53:18 +08:00			`[Unit]`
			`Description=BigBlueButton WebRTC SFU`
			`Wants=redis-server.service`
build: add bbb-webrtc-recorder 2023-04-19 04:02:26 +08:00			`After=syslog.target network.target freeswitch.service bbb-webrtc-recorder.service kurento-media-server.service redis-server.service`
Introduce bigbluebutton.target 2022-02-15 01:49:11 +08:00			`PartOf=bigbluebutton.target`
initial public version 2021-08-13 18:53:18 +08:00
			`[Service]`
			`WorkingDirectory=/usr/local/bigbluebutton/bbb-webrtc-sfu`
			`ExecStart=/usr/bin/node server.js`
			`Restart=always`
			`SyslogIdentifier=bbb-webrtc-sfu`
			`User=bigbluebutton`
			`Group=bigbluebutton`
			`Environment=NODE_ENV=production`
			`Environment=NODE_CONFIG_DIR=/etc/bigbluebutton/bbb-webrtc-sfu/:/usr/local/bigbluebutton/bbb-webrtc-sfu/config/`
fix(bbb-webrtc-sfu): add ALLOW_CONFIG_MUTATIONS to service After node-config was bumped to 3.3.9 (from 3.3.6), it started throwing errors if configurations are mutated without the ALLOW_CONFIG_MUTATIONS env var set. We mutate some configs directly, but I every time I added one of those I made sure that they are always deep cloned. However, we hit an issue with kurento-client mutating a config input, which is an indirect mutation. So, to prevent further surprises I'm allowing mutations on production while prohibiting them in dev envs until I'm 100% sure nothing, direct on indirect, improperly mutates configuration values. 2023-03-13 23:20:00 +08:00			`Environment=ALLOW_CONFIG_MUTATIONS=true`
build: use FIFO scheduler in bbb-webrtc-sfu bbb-webrtc-sfu (and mediasoup) are running in the CFS scheduler which means it has to compete with (much) lower priority tasks like presentation conversion, recording processing, [...] Since it encompasses an RTC application which also handles audio, it should be _at least_ on the same scheduling policy as FS/bbb-html5 - and that should be safer now with mediasoup which has a lower footprint (and generates lower CPU noise overall). This commit puts bbb-webrtc-sfu in the FIFO scheduling policy (same as bbb-html5). Also bumps bbb-html5 nice level up to 18 and sets SFU to nice 19 (so bbb-html5 has some advantage when push comes to shove). This can be improved further by using per-process priorities in SFU. Ideally we'd want mediasoup audio workers and mcs-core to be the same priority as FS (so higher than bbb-html5), but the rest of them (video/screen workers) to be the same or lower than bbb-html5. For future reference: - https://github.com/bigbluebutton/bbb-webrtc-sfu/commit/3e245122dfa155ecb77b536eeadac1e4607cee - https://github.com/bigbluebutton/bbb-webrtc-sfu/commit/66d443d2047fe4fd9872404904b91e0fab4e6948 2022-08-26 22:08:24 +08:00			`CPUSchedulingPolicy=fifo`
			`Nice=19`
initial public version 2021-08-13 18:53:18 +08:00
			`[Install]`
Introduce bigbluebutton.target 2022-02-15 01:49:11 +08:00			`WantedBy=multi-user.target bigbluebutton.target`