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

loop interval and time interval priority #504

Closed
dyokelson opened this issue Sep 13, 2023 · 0 comments · Fixed by #505
Closed

loop interval and time interval priority #504

dyokelson opened this issue Sep 13, 2023 · 0 comments · Fixed by #505

Comments

@dyokelson
Copy link

dyokelson commented Sep 13, 2023

Hi, while running a loop_monitor with the following command we found that if the time interval is not set, it will use a default setting and override the iteration interval.
For example, when measuring LULESH, running:
CALI_SERVICES_ENABLE=loop_monitor,memstat,trace,recorder CALI_LOOP_MONITOR_ITERATION_INTERVAL=20 ./lulesh2.0 -i 100 -s 45
results in somewhat unexpected behavior - where we actually get more frequent data than we want. A current workaround thanks to @daboehme is to set the CALI_LOOP_MONITOR_TIME_INTERVAL=0 which will turn it off and make the iteration interval the prioritized frequency. So running:
CALI_SERVICES_ENABLE=loop_monitor,memstat,trace,recorder CALI_LOOP_MONITOR_ITERATION_INTERVAL=20 CALI_LOOP_MONITOR_TIME_INTERVAL=0 ./lulesh2.0 -i 100 -s 45
has the expected behavior of producing data every 20 iterations.

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