has anyone seen the logging process for ArcGIS Server spike CPU usage?
When Esri replaced geronimo at 10.6 I'm assuming that the remaining javaw process is still the logging manager - the command line for 10.6.1 and 10.5.1 are almost the same.
We are currently performing some load testing and have the GIS server logs set to FINE - so we can analyse the logs with tools like System Log Parser afterwards.
We have Load Runner scripts to test with up to 200 users and during the test period we are seeing the javaw process spike to almost 70% CPU alone which affects the rest of the machine. I'm assuming that with the additional load and amount of incoming requests this process is struggling to keep up? This in turn starts to affect the performance of the server which affects the test which affects the results etc.
Has anyone seen this process do this? I have seen it use a load of memory but not spike the CPU.