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

RT_NAP statistics enhancement #1644

Open
amishscientist opened this issue Feb 9, 2024 · 0 comments · May be fixed by #1651
Open

RT_NAP statistics enhancement #1644

amishscientist opened this issue Feb 9, 2024 · 0 comments · May be fixed by #1651
Assignees

Comments

@amishscientist
Copy link

There at two places where the rt_nap is used in real time sims.

  1. Where it waits for all the child threads that are supposed to finish. This one can cause an overrun.
  2. When it is waiting for the wall clock time to elapse so it can start it's next frame. (This one can't cause an overrun, but can short change the start of your frame.)

I would like a small amount of stats for each of these rt_naps to be printed in the run summary.

  1. Number of rt_naps that were longer than 10% of the sims real time frame. If this number goes up a lot it might show that your box is starting to be over worked too much and you need to ether off load something or find a bigger faster box.
  2. Longest rt_nap. This gives the user a upper bound of the nap.
  3. Shortest rt_nap. This gives the user a lower bound of the nap.

This is all in an effort to help users find real over runs before they move on to the effort of tweaking the operating system to get better latency performance.

I have found as real time frame rates get smaller we are having to do more OS level tweaking to get the overruns to go away. That being said there are still a lot of overrun issues that can be solved before then. This is an attempt to help give the users and developers some prospective on how much noise the rt_naps introduces into their real time frame. The rt_nap is still very much needed because it helps sims play nice with Linux operating system fair scheduler.

@hchen99 hchen99 self-assigned this Feb 12, 2024
@hchen99 hchen99 linked a pull request Feb 20, 2024 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.

2 participants