Please don't do this. If you need to pin a thread to a CPU use https://github.com/OpenHFT/Java-Thread-Affinity.

If your service is so latency sensitive that you can't allow for GC, run with "Epsilon GC" and avoid GC altogether.

If your service is not that latency sensitive but you most definitely can't afford a 500ms pause, run with GC1 and feed it something like `-XX:MaxGCPauseMillis=100`

If some developers (or external libraries) implemented `System.gc()` or `Runtime.getRuntime().gc()` which are stop-the-world garbage collectors, you can avoid that by running with `-XX:+DisableExplicitGC`

If you're running on a new JMV run with ZGC (https://wiki.openjdk.org/display/zgc) which should have very consistent pauses.

But for the sake of all future developers, delete that line.