Ben
Ben
1. I've only noticed it being 1% or 99-100%. 2. It's still at that since my last reply (16 hours). 3. No but I plan to once out of beta....
Running with debug now and I'm running a script to gather the cpu % every 2 seconds. Will report here with data.
Gone up to 100% again, here's the cpu usage, pretty much instant, not gradual. Running in debug for 24 hours. ``` 2024-04-01 20:33:46 :: reverb:start --debug [2282066] CPU Usage: 1%...
I've set `REVERB_APP_PING_INTERVAL=3600` and I've restarted reverb. Back to 0-1% CPU and will run the monitoring for the process. Must be something to do with the amount of pings along...
Yep, I saw that and Soketi limit it too. I increased the limit on Soketi to 500 and the cpu usage was still below 10% even after a month of...
Gone up again. Shall I try a higher ping interval? It's weird it goes straight up 0-100% in 4 seconds. ``` 2024-04-04 19:28:00 :: reverb:start --debug [237336] CPU Usage: 2%...
@clue Looks very similar and relates to my use-case of high connect/disconnect events. In theory, all we'd need to do is replicate a lot of users (100+) connecting/disconnecting. It started...
Might have fixed an issue for you, but I believe mine was slightly different. I have no problems when running it under Soketi on the same machine/ulimit.