You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
while running a bunch of sims in parallel, I noticed that the memory consumption went through the roof. When I looked into it I could reduce it to just running jx.integrate in a while loop, see snippet below. Do I need to clear some cache manually somehow or is memory leaking somewhere? If the latter is the case than I think a fix should be high priority.
the rate at which it leaks seems to be independent of number of t_steps / t_max
Lemme know if there is any other tests I should run or if you cannot reproduce this.
EDIT: @kyralianaka found out that jitting the function fixes the issue. My hypothesis is that each call to integrate instantiates some new objects that don't get destroyed for some reason. In the jitted version, this does not happen since they are only instantiated once.
The text was updated successfully, but these errors were encountered:
jnsbck
changed the title
Suspected memory leak in jx.integrate or jx.Cell
Memory leak in jx.integrate or jx.CellFeb 29, 2024
Hi,
while running a bunch of sims in parallel, I noticed that the memory consumption went through the roof. When I looked into it I could reduce it to just running
jx.integrate
in a while loop, see snippet below. Do I need to clear some cache manually somehow or is memory leaking somewhere? If the latter is the case than I think a fix should be high priority.things I already tried:
Lemme know if there is any other tests I should run or if you cannot reproduce this.
EDIT:
@kyralianaka found out that jitting the function fixes the issue. My hypothesis is that each call to
integrate
instantiates some new objects that don't get destroyed for some reason. In the jitted version, this does not happen since they are only instantiated once.The text was updated successfully, but these errors were encountered: