-
Notifications
You must be signed in to change notification settings - Fork 53
New issue
Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? # to your account
Collect per-command resource usage data. #940
Conversation
When running under ODK_DEBUG=yes, instruct the shell to run every command through a small wrapper around the actual shell to capture resource usage (CPU time and memory consumption) for each command, in addition to capturing resource usage for the entire run. The resource usage data is written into `tmp/debug.log`.
@matentzn @anitacaron I’ve done only limited testing of this for now. I’ll do more when I’m back next week. |
This looks great! @anitacaron when you have an opportunity can you test this? |
I tested it, and it looks good. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
My main concern with this is that the ODK_DEBUG parameter gets extended to a potentially breaking feature (writing a, potentially large logfile), but I don't really think this is a realistic concern, as the logs in practice are not thaaaat big, and certainly not bigger than the associated ontologies times 20. I am happy with merging this.
When running under ODK_DEBUG=yes, instruct
make
to run every command through a small wrapper around the actual shell to capture resource usage (CPU time and memory consumption) for each command, in addition to capturing resource usage for the entire run. The resource usage data is written intotmp/debug.log
.