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

-max-memory ignored #20

Closed
osowiecki opened this issue Feb 15, 2020 · 4 comments
Closed

-max-memory ignored #20

osowiecki opened this issue Feb 15, 2020 · 4 comments

Comments

@osowiecki
Copy link

In [DSK: Pass 1/1, Step 2: counting kmers ] the memory limit seems to be ignored. Minia went over the ram limit and entered SWAP.

@rchikhi
Copy link
Member

rchikhi commented Feb 16, 2020

by a lot? (thanks for the report anyhow)
DSK tries to aim for that memory usage but it's not a hard threshold, it may go higher due to hashing biases

@osowiecki
Copy link
Author

Told it to use --max-memory 180000 and it used up 189G/189G (htop) and moved to swap. Can't tell how much swap it used as other applications filled up some swap previously. I assumed GATB is using Megabytes, not Mebibytes for this option.

free --mega
total used free shared buff/cache available
Mem: 198027 2780 908 0 194338 19378

free --mebi
total used free shared buff/cache available
Mem: 193386 2716 900 0 189768 189246

@rchikhi
Copy link
Member

rchikhi commented Feb 16, 2020

I see. I'd say it's a bit risky to ask minia (or in fact, any big data program) to use close to the max memory of a system. If you significantly lower max-memory, all's fine?

@osowiecki
Copy link
Author

Waiting for new results. Will edit this reply.

@rchikhi rchikhi closed this as completed Dec 23, 2023
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

2 participants