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

Collect execution metrics for each analysis #84

Closed
nellh opened this issue Sep 21, 2017 · 1 comment
Closed

Collect execution metrics for each analysis #84

nellh opened this issue Sep 21, 2017 · 1 comment

Comments

@nellh
Copy link
Contributor

nellh commented Sep 21, 2017

From @poldrack:

it would be useful to know what kind of instances are used for freesurfer, MRIQC, and fMRIPREP

That's something that can be saved but isn't at the moment. The metrics will need to be per-task since a given analysis can be scheduled over several host systems. Some ideas for what can be collected:

  • Instance used (type, EC2 ARN)
  • Real run time (CPU time, not wall clock)
  • Percent utilization (CPU/memory allocated vs used)

@poldrack Anything else you'd like to see for this?

@poldrack
Copy link

poldrack commented Sep 21, 2017 via email

@nellh nellh added the backlog label Nov 3, 2017
@nellh nellh closed this as completed Apr 18, 2019
nellh added a commit that referenced this issue Mar 10, 2020
Set a 60 second timeout on bids-validator runs
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants