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 sending notifications (both atKey or forText) #894

Open
cconstab opened this issue Jan 23, 2023 · 1 comment
Open

High CPU usage when sending notifications (both atKey or forText) #894

cconstab opened this issue Jan 23, 2023 · 1 comment
Assignees
Labels
bug Something isn't working

Comments

@cconstab
Copy link
Member

cconstab commented Jan 23, 2023

Describe the bug

When sending a lot of notifications on low powered hardware the CPU gets hammered and notifications get delayed.

Steps to reproduce

  1. First I send a lot of notifictaions (several a second) on a small CPU
  2. Then monitor the incoming notifications and the time they were sent
  3. 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.

@cconstab cconstab added the bug Something isn't working label Jan 23, 2023
@gkc
Copy link
Contributor

gkc commented Feb 20, 2023

I'm addressing this within the larger piece of work re encryption future-proofing.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

2 participants