Perfect, thx Joe On Mon, Feb 3, 2025 at 11:01 AM Joe Witt <[email protected]> wrote:
> Erik, > > The JVM offers plenty of good monitoring/tooling these days where you can > watch its behavior over time to see for your flows/workload what the steady > state level you need is. What you want to watch for is what is the level > of memory used after a cleanup (old/iterative/etc..). Add some buffer and > call it good. That said, it is totally workload dependent so if your aim > is to minimize heap size do this and call it good. > > Alternatively you can do the trial/error dance of dropping the size by say > 100MB at a time until it breaks after some period of time then lower it by > smaller increments. > > Joe > > On Mon, Feb 3, 2025 at 11:55 AM Erik Ostermueller <[email protected]> > wrote: > >> Hi, >> >> We've seen Minifi JVM heap sizes above 512m....but these are on machines >> that are relatively idle. >> >> If there's a beefy portion of that 512m that is not used, we'd like to >> see if we can shrink that consumption -- using the JVM startup parm >> -XX:MaxRAM. >> >> Have others tried to shrink the heap footprint? >> Any recommendations on where to start? 64mb? 1g? >> As a completely rough starting point, the contents of the lib folder if >> the 2.2 minifi distribution are about 200mb. >> >> Besides confirming that GC pauses/time are sufficiently low (like less >> than 2-5% of all processing time), any suggestions for how to assess >> whether we're doing too much shrinking? >> >> Thanks in advance for any insight here, >> >> --Erik >> >>
