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

Process was automatically killed #136

Open
yanjw123 opened this issue Nov 2, 2023 · 3 comments
Open

Process was automatically killed #136

yanjw123 opened this issue Nov 2, 2023 · 3 comments
Labels
0.2.5 Double-hung Smudgeplot done with the 0.2.5 Double-hung with curtains version performance issues regarding scalability and performance of the method.

Comments

@yanjw123
Copy link

yanjw123 commented Nov 2, 2023

smudgeplot.py hetkmers -o kmcdb_L"$L"_U"$U" < kmcdb_L"$L"_U"$U".dump
Running smudgeplot v0.2.5
Task: hetkmers
Kmers and coverages loaded.
Killed

@yanjw123 yanjw123 added the potential problems for potential problems given different scenarios (How does XXX infulence sumdgeplot?) label Nov 2, 2023
@KamilSJaron KamilSJaron added performance issues regarding scalability and performance of the method. 0.2.5 Double-hung Smudgeplot done with the 0.2.5 Double-hung with curtains version and removed potential problems for potential problems given different scenarios (How does XXX infulence sumdgeplot?) labels Nov 18, 2023
@KamilSJaron
Copy link
Owner

Hi, that means you run out of memory (or the process does something else your computer does not like).

In general, I would just recommend to use more efficient smudge_pairs algorithm, or even better, give us a few weeks. The new updated release will have this process a lot more optimised.

@gongshuang33
Copy link

I also encountered a similar problem. When I ran the code "smudgeplot.py hetkmers -o kmcdb_L"$L"_U"$U" < kmcdb_L"$L"_U"$U".dump", my.dump file was about 10GB in size, and the memory usage kept increasing during the running process, eventually growing to over 300GB. If the server memory was insufficient, the program would be killed. Of course, if the server had enough memory, the program would run normally and produce output, but it would take several days.Thank you and all the best!

@KamilSJaron
Copy link
Owner

For the lack of capacity, I am just posting this here: #137 (comment)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
0.2.5 Double-hung Smudgeplot done with the 0.2.5 Double-hung with curtains version performance issues regarding scalability and performance of the method.
Projects
None yet
Development

No branches or pull requests

3 participants