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 #65

Open
2 of 3 tasks
leostera opened this issue Mar 5, 2024 · 6 comments
Open
2 of 3 tasks

High CPU Usage #65

leostera opened this issue Mar 5, 2024 · 6 comments
Labels
bug Something isn't working
Milestone

Comments

@leostera
Copy link
Collaborator

leostera commented Mar 5, 2024

This issue got reported first here leostera/minttea#38 – but Github doesn't let me transfer an issue across organizations.

Possible culprits:

@leostera leostera added the bug Something isn't working label Mar 5, 2024
@tjdevries
Copy link
Contributor

Can confirm, I also have this problem:

Riot 0.0.8 from opam, OCaml 5.1.1, Linux (I can give more sys information if you need)

@tjdevries
Copy link
Contributor

I was also able to reproduce on OCaml 5.2.0~alpha (altho the memory usage looked better!)

@tjdevries
Copy link
Contributor

From what I can tell so far, something is happening with blink to make it happen (we can chat on discord more if you want)

@tjdevries
Copy link
Contributor

OK, maybe it's not blink, I'm very confused haha, i can send you link in VOD to watch if you have any ideas

@leostera leostera added this to the riot/phase-1 milestone Mar 21, 2024
@leostera
Copy link
Collaborator Author

Thanks @tjdevries for the context and comments! ✨ I've been digging and found 3 specific things that could've be responsible. 2 of those are now fixed.

If you have code examples that I could try that would help me narrow down on the 3rd or others.

@leostera leostera modified the milestones: riot/phase-1, 0.0.9 Mar 21, 2024
@charleslambert
Copy link

charleslambert commented Apr 25, 2024

Hey @leostera, I was looking into this, and from what I can tell it seems to be caused by having multiple schedulers, and one of the schedulers ending up with a list of skippable messages. It's non deterministic though.

I tested using 2 schedulers and 10 spawned processes. Every once and a while a scheduler gets stuck spinning on a mailbox full of skippable messages. I am trying to dig in more, but don't fully understand the architecture yet.

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

3 participants