As mentioned in issue #35, ode4j appears to allocate significant amounts of memory in some situations/systems ("3-4 MB/s").
The problem may be in the stepper which allocates large arrays for the solver during each step.
A solution could involve array pooling.
As mentioned in issue #35, ode4j appears to allocate significant amounts of memory in some situations/systems ("3-4 MB/s").
The problem may be in the stepper which allocates large arrays for the solver during each step.
A solution could involve array pooling.