You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Bug reason is not yet confirmed and this is opened to keep a track on it.
Describe the bug
There is an OBSERVATION raised by @mostoview and myself. CPU usage increases with time in v2.2.0<= , possibly due to changed wrtc library (last properly working version is v2.1.3)
I have noticed increased CPU usage as well with newer haxball.js versions, but not yet confirmed the reason.
CPU load rises with empty rooms with time, after one day increasing ~100x (e.g. from 0.4% to 40%).
To Reproduce
Run a room with haxball.js==2.1.3 and haxball.js@latest and observe the process CPU usage.
Expected behavior
Not increasing CPU load.
Device (please complete the following information):
node 18, node 20, node 22
ubuntu 24, ubuntu 22
Additional context
Benchmarking the process between versions will take some time, but Issue is opened to see if someone has a similar overview and could share more findings.
The text was updated successfully, but these errors were encountered:
Bug reason is not yet confirmed and this is opened to keep a track on it.
Describe the bug
There is an OBSERVATION raised by @mostoview and myself. CPU usage increases with time in
v2.2.0<=
, possibly due to changedwrtc
library (last properly working version isv2.1.3
)I have noticed increased CPU usage as well with newer
haxball.js
versions, but not yet confirmed the reason.CPU load rises with empty rooms with time, after one day increasing ~100x (e.g. from 0.4% to 40%).
To Reproduce
Run a room with
haxball.js==2.1.3
andhaxball.js@latest
and observe the process CPU usage.Expected behavior
Not increasing CPU load.
Device (please complete the following information):
node 18
,node 20
,node 22
ubuntu 24
,ubuntu 22
Additional context
Benchmarking the process between versions will take some time, but Issue is opened to see if someone has a similar overview and could share more findings.
The text was updated successfully, but these errors were encountered: