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

Get rid of RTS mon threads #1430

Open
7 tasks
plajjan opened this issue Aug 15, 2023 · 0 comments · May be fixed by #2185
Open
7 tasks

Get rid of RTS mon threads #1430

plajjan opened this issue Aug 15, 2023 · 0 comments · May be fixed by #2185

Comments

@plajjan
Copy link
Contributor

plajjan commented Aug 15, 2023

I added in the RTS mon functionality early on. It's running as separate threads. I think this is now better implemented as functions in Acton that do C magic under the hood.

One of the reasons to run as a separate thread was to be able to report on the state of things regardless of what the RTS might be doing but the biggest impediment to anything right now is the GC, which stops all threads anyway.... so I think it's OK to fold this into Acton functions instead.

  • add functions in rts module to get RTS stats
    • just follow same structure as today, but return Acton objects (lists & dicts) rather than a JSON blob
    • do any conversion to JSON in Acton, if necessary
  • expose information over prometheus style HTTP interface
    • requires a HTTP server in stdlib
  • implement some simple prometheus CLI client
  • remove rts mon socket (replaced by prometheus interface)
  • add new rts monitor log actor that writes RTS stats to a file
  • remove rts mon log
@plajjan plajjan linked a pull request Mar 2, 2025 that will close this issue
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

Successfully merging a pull request may close this issue.

1 participant