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

Memory issue when running taxprofiler with Kaiju #408

Open
albatalavera opened this issue Jan 20, 2025 · 2 comments
Open

Memory issue when running taxprofiler with Kaiju #408

albatalavera opened this issue Jan 20, 2025 · 2 comments
Assignees

Comments

@albatalavera
Copy link

Description

A memory issue has been identified when running taxprofiler with Kaiju to analyze whole metagenomes. The process fails with the current memory allocation of 72GB. Doubling the memory to 144GB does not resolve the issue. Only when the memory is tripled to 216GB, the process completes successfully.

It is necessary to determine the appropriate memory allocation to ensure the process runs efficiently without exceeding resources.

Environment

  • Tool: Taxprofiler
  • Software used: Kaiju
  • Data type: Whole metagenomes
  • Tested memory allocations:
    • 72GB: Failed
    • 144GB: Failed
    • 216GB: Completed successfully

Tasks

  1. Perform incremental memory tests to identify the minimum required allocation for successful execution.
  2. Update the bu_isciii/templates/taxprofiler/DOC/taxprofiler.config file to reflect the optimal memory allocation.
@albatalavera albatalavera self-assigned this Jan 20, 2025
@victor5lm
Copy link
Contributor

This issue might not be of interest anymore since we are going to skip Kaiju when launching Taxprofiler from now on? @saramonzon

@saramonzon
Copy link
Member

you could be interested in running kaiju if the service focus is metagenomics, so it's interesting although not really a priority :)

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

No branches or pull requests

3 participants