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

Crash on tracing test_poisson_regression_non_normal_loss #8

Open
niyonx opened this issue May 17, 2021 · 1 comment
Open

Crash on tracing test_poisson_regression_non_normal_loss #8

niyonx opened this issue May 17, 2021 · 1 comment
Labels
bug Something isn't working performance performance

Comments

@niyonx
Copy link
Contributor

niyonx commented May 17, 2021

On parse, it would at some point stop printing and the trace file inside the traces folder gets so big, my computer would run out of memory, taking around 50GB.

Do I just not have enough memory or did the test get stuck into a loop? Thanks

@yohanchatelain
Copy link
Owner

It's a memory limitation indeed. I added an online parsing for not loading all traces in memory but it seems to fail.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working performance performance
Projects
None yet
Development

No branches or pull requests

2 participants