Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

High CPU usage when not all repeaters are connected. #1293

Open
lupettohf opened this issue Feb 5, 2025 · 0 comments
Open

High CPU usage when not all repeaters are connected. #1293

lupettohf opened this issue Feb 5, 2025 · 0 comments

Comments

@lupettohf
Copy link

I've found a bug where if you have a large number of not connected hotsposts the server will still make a listner and try to fetch the data from redis, resulting ina choppy audio experience for all the user due to a high cpu usage when this happens.

Console is getting spammed with
2025/02/05 15:21:25 [internal/dmr/servers/hbrp.(*Server).subscribeRawPackets@server.go:173]: Error getting repeater UNCONNECTED_REPETAER_NUMBER from redis 2025/02/05 15:21:25 [internal/dmr/servers.(*RedisClient).GetRepeater@redis.go:109]: Error getting repeater from redis: redis: nil 2025/02/05 15:21:25 [internal/dmr/servers/hbrp.(*Server).subscribeRawPackets@server.go:173]: Error getting repeater UNCONNECTED_REPETAER_NUMBER from redis 2025/02/05 15:21:25 [internal/dmr/servers.(*RedisClient).GetRepeater@redis.go:109]: Error getting repeater from redis: redis: nil 2025/02/05 15:21:25 [internal/dmr/servers/hbrp.(*Server).subscribeRawPackets@server.go:173]: Error getting repeater UNCONNECTED_REPETAER_NUMBER from redis

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant