I host a small 1.7.2 server for a few (<10) friends.
The javaw process running the server.exe utilizes significantly higher CPU when I launch my local client. Around 20-30% increase in server CPU usage vs a remote client logon from my laptop where the CPU load increase is typically 1-2%.
If I set the javaw server process Affinity to 4 of the cores, and redirect my client javaw to the other cores, basically forcing the client and server processes onto different CPU cores the server impact of my local client drops back into the 1-2% range of a normal client connection.
Comments 4
Is this still a concern in the current Minecraft version 1.7.4 / Launcher version 1.3.8 or later? If so, please update the affected versions in order to best aid Mojang ensuring bugs are still valid in the latest releases/pre-releases.
Sorry for the delayed response, I had moved my server off to a dedicated Ubuntu system to avoid the CPU conflict issues. After the move to Ubuntu the server runs so stable it was harder to justify finding time to pull it back into windows to revalidate 🙂
I'm no longer able to duplicate the CPU degradation by running the client and server on the same Windows 7 system so as far as I can tell it was resolved at least by Launcher 1.4.2 and Server/Client at 1.7.9.
Thanks
So do you think this is related to the "nogui" issue you posted after this one? It looks like MC-39078 was deleted? but I saw the cached version where you said setting the nogui reduced the CPU down to 1-2%. I'm having similar issues... CPU usage on an idle server (no clients, hour+ after last person disco'd) hovers from 25 - 45% on a 4-core 3.4ghz i5 processor. CPU load appears evenly distributed across all 4 cores. Running VisualVM shows the largest time consumer is some javax.swing.timer call (or DoPostEvents or something like that, don't have it in front of me)