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
When sending a lot of notifications on low powered hardware the CPU gets hammered and notifications get delayed.
Steps to reproduce
First I send a lot of notifictaions (several a second) on a small CPU
Then monitor the incoming notifications and the time they were sent
And then spot the delay in receiving.
Expected behavior
Not to hit the CPU too hard
Screenshots
RSA operations seem to be the culprit for every notification
Smartphones
Device: Pi 3
Were you using an atApplication when the bug was found?
No response
Additional context
I would have expected an RSA operation perhaps once but not for every notification. CPU profiler lead me to this conclusion I will upload the screen shots.
The text was updated successfully, but these errors were encountered:
Describe the bug
When sending a lot of notifications on low powered hardware the CPU gets hammered and notifications get delayed.
Steps to reproduce
Expected behavior
Not to hit the CPU too hard
Screenshots
RSA operations seem to be the culprit for every notification
Smartphones
Were you using an atApplication when the bug was found?
No response
Additional context
I would have expected an RSA operation perhaps once but not for every notification. CPU profiler lead me to this conclusion I will upload the screen shots.
The text was updated successfully, but these errors were encountered: