[URGENT] Default Movement Component causing major dedicated server performance issues (Linux Only)
After a long process of profiling, I have found a major issue with the Default Movement Component & Linux Dedicated Servers. This issue does not appear on Windows Servers & this issue did not exist on 4.16.2.
This seems related to the "Char FindFloor" function, it seems to be looping in a very strange way, causing the server's CPU to spike & in some cases stalls the server from processing anything (Picture 1). There is also some hitches to do with the MoveComponent function (Picture 2).
This occurs when I jump on top of objects inside my map.
You can find my ue stats files here: https://www.dropbox.com/s/xfvaa4g5d0y8729/City-LinuxServer-18-10.09.06.ue4stats?dl=1 https://www.dropbox.com/s/kzq5oodehsus06v/City-LinuxServer-18-10.07.02.ue4stats?dl=1
You will unfortunately need to change source files and rebuild PhysX to fix this. This is not too hard but it can be time consuming.
First of all, you will need to download all the sources from github (you may already have that). Then, find all Linux CMakeLists.txt under Engine/ThirdParty/PhysX (there are three of importance:
) and remove -ffast-math from them.
Then, open VisualStudio solution for the engine, rebuild Programs\Automation directory (right click->Rebuild), rebuild AutomationTool and then run it like this
Then you can submit the resulting .a files (in Lib/Linux/x86_64-unknown-linux-gnu) to your source control and rebuild the Linux server.
We're looking into possibility of including this fix into 4.17 branch, but the above will get you unblocked today.
Follow this question
Once you sign in you will be able to subscribe for any updates here