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

Q1: Specification - Compute Resources #7

Closed
mfansler opened this issue May 19, 2021 · 1 comment
Closed

Q1: Specification - Compute Resources #7

mfansler opened this issue May 19, 2021 · 1 comment
Assignees

Comments

@mfansler
Copy link
Collaborator

Create specification for Q1.

Working definition: Obtain execution time and memory usage in MiB for method execution. If multiple rules or samples for method: sum time and get max MiB.

@mfansler mfansler added this to the launch milestone May 19, 2021
@uniqueg uniqueg assigned uniqueg and unassigned uniqueg May 19, 2021
@dominikburri dominikburri self-assigned this Jun 3, 2021
@dominikburri
Copy link
Collaborator

What we need to think about to properly benchmark the methods:

  • Which dataset, resp. samples, to use?
  • How many replicates to use (if any) and how to report them? E.g. box plots for 10 executions.
  • On which platform should it be tested? This also influences how the results can be obtained, e.g. when using AWS there is propably a way to automatically obtain the compute usages.
  • The benchmark should be irrespective of the implementation of the workflow. That is, using a nextflow or snakemake specific approach could lead to systematic differences based on their implementation.
  • other?

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.

4 participants