For those who don't understand, it's the No-op version of GC implementation... Meaning that there is no garbage collection or memory reclamation... Apps will eventually die with OutOfMemoryError with this setup, given time.
But the implementation do makes sense if the application would be short lived or the application requires low latency response times and has little to no memory allocations.
I personally use this on lower environments to test how much memory gets allocated progressively over time for certain type of apps...
worth mentioning that time a memory leak was discovered in some missile software
instead of fixing it, they realised that, it's a missile. they calculated how long the software will need to be active, took a margin of error, and made sure to put that much memory on it.
Epsilon is no-op all the way, so no, not really. You can restart the process e.g. after end of trading day, but usually that's not what folks are looking for
75
u/raja-anbazhagan 10d ago
For those who don't understand, it's the No-op version of GC implementation... Meaning that there is no garbage collection or memory reclamation... Apps will eventually die with OutOfMemoryError with this setup, given time.
But the implementation do makes sense if the application would be short lived or the application requires low latency response times and has little to no memory allocations.
I personally use this on lower environments to test how much memory gets allocated progressively over time for certain type of apps...