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

Running HexSE eats a lot of RAM #141

Open
WilliamZekaiWang opened this issue Oct 10, 2024 · 0 comments
Open

Running HexSE eats a lot of RAM #141

WilliamZekaiWang opened this issue Oct 10, 2024 · 0 comments

Comments

@WilliamZekaiWang
Copy link

I ran HexSE on a tree with 100 tips, of which, the respective fasta has 9000 NT each. The config file was the same as the readme, except that there was no orfs, and false for circular.

At 16% completion, this was the following output from top (the command being python3 from internal HexSE functions, ran on crowly):

    PID USER      PR  NI    VIRT    RES    SHR S  %CPU  %MEM     TIME+ COMMAND
 280197 will      20   0   30.2g  26.0g  37632 R 100.3  41.5   5:31.42 python3

While running the test case in the readme, it used up all the CPU again, and 15 GB of total RAM. The test case also had 100 tips.

It's likely that the issue lies in long fasta files and less so the number of tips on the tree?

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

1 participant