Skip to content

Conversation

@bgruening
Copy link
Member

@bgruening bgruening requested a review from cat-bro December 22, 2025 09:03
@cat-bro
Copy link
Collaborator

cat-bro commented Dec 24, 2025

We have this for quast on AU and it’s mostly OK:

    cores: 16
    mem: 62
    rules:
    - id: quast_small_input_rule
      if: input_size < 0.01
      cores: 2
      mem: 10
    - id: quast_medium_input_rule
      if: 0.01 <= input_size < 1
      cores: 4
      mem: 16

Every now and then there is an OOM for the 62GB case. I have looked into parameters used for these OOM jobs and often either use_ref or large is not set to true, so these jobs would only be getting 12GB under this new scheme.

AU unfortunately cannot run quast with more than 100GB or so*, so if this is merged I’ll put in a rule in AU’s config to override this one and give the big jobs 100 instead.

*quast cannot run on pulsar because the icarus link from the html does not work. I haven’t figured out whether it’s pulsar or the wrapper at fault in this case.

@bgruening
Copy link
Member Author

If you like we combine your rules with the proposed here. You would still.need to overwrite it until the pulsar issues is figured out.

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 this pull request may close these issues.

3 participants