search

JeffersonLab / coatjava

1 stars 17 forks source link

JEVIO memory leak #4

Open baltzell opened 4 years ago

baltzell commented 4 years ago

For the decoder, our current "normal" 2 GB EVIO file corresponds to about 800s/2.5GB on the x/y-axis. This is, so far, not significantly limiting us, but for the future, e.g. multi-threading decoding, or larger EVIO files, this memory usage should be addressed.

Screen Shot 2019-10-09 at 17 54 07

baltzell commented 4 years ago

Will be addressed with CODA's move to EVIO6/HIPO.