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

Trigger: Performance tests #206

Open
MRiganSUSX opened this issue Apr 12, 2023 · 0 comments
Open

Trigger: Performance tests #206

MRiganSUSX opened this issue Apr 12, 2023 · 0 comments
Labels
enhancement New feature or request

Comments

@MRiganSUSX
Copy link
Contributor

Ideas for trigger performance measuring and monitoring:

  • Write an application to track CPU usage and RAM usage per trigger module and makes plot of that. This is to attempt a performance test without touching the trigger DUNE-DAQ while doing so.
  • Run the above application on a single APA with one link and one Maker and CRT. Then see how it scales (multiple links, multiple makers, multiple APAs)
  • Is the latency affected by the trigger rate?
  • Latency plots on Grafana: How long it takes for a TC to propagate through the system, calculated this way: TC received vs TC sent
  • Latency plots on Grafana: Comparing data times to wall-clock time
  • Standardise all latency measurements for all trigger modules from start to finish (buffer, zipper...), Grafana compatible
@MRiganSUSX MRiganSUSX added the enhancement New feature or request label Apr 12, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

1 participant