If that helps then you can try Process Lasso to automate this. Source: 6 months ago

CoreDirector is pretty straight forward and easy to use, but on my machine it caused micro-stutters even if I had higher frames. I used Process Lasso to do this, which should be the same thing CoreDirector does, but it worked better for me. Source: 7 months ago

If BES doesn't work for you, you can try Project Lasso for free: https://bitsum.com/. On this one, I've set the CPU Limiter to when the process reach 85% for 2 seconds, limit by 1 core for 1 second. You can also reduce the CPU affinity to one less core using the Windows Task Manager but this will impact the frame rate. Source: 8 months ago

I use process lasso to assign priority, cores, powerplans and 0.5ms timer resolution to processes to improve performance. (something to manage a process once run like powerplans). Source: 8 months ago

All right, here are two possible solutions I know of: Firstly you can limit the number of cores the game is using, which can increase your FPS significantly (and potentially fix the stutter as well). Why? Because Far Cry 3 and 4's optimalization on PC sucks ass, and the newer the PC setup, the more likely it will have problems with both games. How to set CPU affinity: 1. Open the game. 2. Once in-game, press... Source: 12 months ago

If you're curious, attach VisualVM and watch the RAM usage graph. You'll notice that Java performs garbage collections long before reaching allocating the maximum amount of RAM allocated, and you can't even feel any performance issue in-game. Source: about 1 year ago

Hangs and deadlocks are significantly harder to debug. A first step is taking a thread dump so you can see what each thread in the JVM is currently trying to do. I like VisualVM for this, you can also use the command-line tools jps -l (to list all Java PIDs) and jstack for taking a thread dump. Source: about 1 year ago

The Java VisualVM project is an advanced dashboard for Memory and CPU monitoring. It features advanced resource visualization, as well as process and thread utilization. - Source: dev.to / about 1 year ago

This sounds like a server thread freeze/deadlock/crash or something. I think I would start debugging this using a tool like VisualVM; attach it to the game, wait for the hang, take a thread dump, and check what the server thread is up to. Source: about 1 year ago

Just wanted to chip in to say that /u/UtilFunction is correct. The proper way to measure memory consumption of any Java application independent of which garbage collector is used is to perform a heap dump (which automatically forces a complete garbage collection). I like to use VisualVM for that. Source: about 1 year ago