[Oskari-user] Oskari's performance and java processes

[Mäkinen Sami (MML)]

Hi,

It's not unusual for CPU to go over 100% as modern hardware have multiple cores and 100% means that one of those cores is fully utilized. The transport webapp in particular can consume whatever resources the server has to offer if there are multiple users looking at layers from WFS-services. On our servers the oskari-server application usually bounces between 15-120% CPU averaging at about 35% but this is of course dependent of the hardware and number of concurrent users etc. Looks like you have quite a lot of memory assigned to Oskari. We've been running even our largest instances with about 4gb. Adding memory is not always the right solution since Java garbage collection just takes longer if there's more "garbage" to clear which might lead to the server not being responsive while making room in the memory.

Then there are other things that affect CPU usage like what else is running on that Jetty-process? You might want to separate the included GeoServer and transport webapps to other Jetty instances so the main oskari-server is not hindered when these webapps consume resources if you have a lot of data going through those webapps. Are there any server code customizations that might lead to unexpected behavior like infinite loops on errors?

Best regards,
        Sami

Lähettäjä: Oskari-user <oskari-user-bounces at lists.osgeo.org> Puolesta Ryyppö, Minna
Lähetetty: torstai 23. toukokuuta 2019 15.06
Vastaanottaja: oskari-user at lists.osgeo.org
Aihe: [Oskari-user] Oskari's performance and java processes

Hello dear Oskari-users,

At Finnish Heritage Agency we have had occasionally some problems with our Oskari application's performance. At the server, that can be seen as bigger CPU load than normally. Top processes command gives a list like that:

  PID USER      PR  NI    VIRT    RES    SHR S  %CPU %MEM     TIME+ COMMAND
1546 jetty     20   0 15.534g 5.375g  16544 S 123.9 69.0  26019:00 java
  992 ----     20   0 1158860 674672   2648 S   0.3  8.3 644:39.14 ----
12753 ----   20   0  396852  86396  78048 S   0.3  1.1   4:20.40 ---
    1 ---      20   0   38160   4548   2588 S   0.0  0.1   0:09.68 ---
    2 ----      20   0       0      0      0 S   0.0  0.0   0:00.19 ----
    3 ----      20   0       0      0      0 S   0.0  0.0   0:13.08 ----

So it looks like there is a java process by jetty which takes more of cpu than there is available. When this process starts, the application is unable to work properly.
My question is, has anyone else ever encountered similar situation? Or has any idea whether this kind of java-process is normal with Oskari? Or, what that process might do when it is taking so much processor power?

I know that this is difficult to answer, but I'm just hoping that someone has had the same situation somewhere and could maybe give some good tips to solve this annoying problem... :)

regards,

Minna Ryyppö
Geoinformation Specialist
Archives and Information Services
Finnish Heritage Agency
PL 913, 00101 Helsinki
p. 0295 33 6253
minna.ryyppo at museovirasto.fi<mailto:minna.ryyppo at museovirasto.fi>

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.osgeo.org/pipermail/oskari-user/attachments/20190523/1a93f36b/attachment.html>