Hi list members!
I started with Geoserver on a Windows 2016 server some time ago. Since I had problems with high CPU & memory usage I tried a Linux installation which seemed much better. For various reasons I now went back to Windows on a more capable server (4 CPU / 8 GB RAM) which I thought would be able to run Geoserver better than the first installation.
But unfortunately the same issue on Windows again. On startup the service goes up to approx 70%, idles around 1-2 % CPU but still hogs about 600MB of RAM. Logging into the web admin brings the CPU up to 50%. The main issue is that a layer request makes it spike at around 90% and 2.5GB RAM and then it just stays there without me making any more requests. Now it's game over until after the service is restarted which by the way is not possible. I have to kill the process and start the service.
The layer in question is loading an ImageMosaic layer with images on disk and the time/elevation data in PostgreSQL. A windbarb SLD is applied to the layer.
Any ideas on where to start troubleshooting this?
Thanks in advance!
Niklas
Hi,
Find a mail thread with title "Geoserver 2.20.RC generating high CPU load" from the geoserver-devel mailing list from mid-September 2021, and see the ticket https://osgeo-org.atlassian.net/browse/GEOS-10243
I believe that you have met by the same issue.
-Jukka Rahkonen-
-----Alkuperäinen viesti-----
Lähettäjä: Niklas Elelid <niklas@anonymised.com>
Lähetetty: sunnuntai 19. joulukuuta 2021 20.37
Vastaanottaja: geoserver-users <geoserver-users@lists.sourceforge.net>
Aihe: [Geoserver-users] High CPU & memory on Windows
Hi list members!
I started with Geoserver on a Windows 2016 server some time ago. Since I had problems with high CPU & memory usage I tried a Linux installation which seemed much better. For various reasons I now went back to Windows on a more capable server (4 CPU / 8 GB RAM) which I thought would be able to run Geoserver better than the first installation.
But unfortunately the same issue on Windows again. On startup the service goes up to approx 70%, idles around 1-2 % CPU but still hogs about 600MB of RAM. Logging into the web admin brings the CPU up to 50%.
The main issue is that a layer request makes it spike at around 90% and 2.5GB RAM and then it just stays there without me making any more requests. Now it's game over until after the service is restarted which by the way is not possible. I have to kill the process and start the service.
The layer in question is loading an ImageMosaic layer with images on disk and the time/elevation data in PostgreSQL. A windbarb SLD is applied to the layer.
Any ideas on where to start troubleshooting this?
Thanks in advance!
Niklas
_______________________________________________
Geoserver-users mailing list
Please make sure you read the following two resources before posting to this list:
- Earning your support instead of buying it, but Ian Turton: http://www.ianturton.com/talks/foss4g.html#/
- The GeoServer user list posting guidelines: http://geoserver.org/comm/userlist-guidelines.html
If you want to request a feature or an improvement, also see this: https://github.com/geoserver/geoserver/wiki/Successfully-requesting-and-integrating-new-features-and-improvements-in-GeoServer
Geoserver-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-users
Hi Niklas,
Jody talks about this here
https://sourceforge.net/p/geoserver/mailman/message/37328870/
Now that I think about it I did have a windows situation when GeoServer consumed resources, become unresponsive and never came back, possibly following a silly SQL query. Installing the Control Flow Module fixed this, at least so that the service would reliably stay running after dropping long queries.
Running fine here on Windows Server 2019, AdoptOpenJDK: 11.0.6 (OpenJDK 64-Bit Server VM) and Tomcat 8.5. With 2 CPUs and 12 GB RAM.
When I do things in the Web UI the CPU spikes briefly but goes back down. I also have your noted steady 2.5 GB RAM usage by Tomcat. I assumed this was fine.
Server Status screenshot in case it helps (note early morning here and not much usage presently):
Good luck!
···
If you are not the intended recipient of this email, please notify us immediately and be aware that any disclosure, copying, distribution or use of the contents of this information is prohibited.
From: Niklas Elelid niklas@anonymised.com
Sent: Monday, 20 December 2021 5:37 AM
To: geoserver-users geoserver-users@lists.sourceforge.net
Subject: [Geoserver-users] High CPU & memory on Windows
Hi list members!
I started with Geoserver on a Windows 2016 server some time ago. Since I
had problems with high CPU & memory usage I tried a Linux installation
which seemed much better. For various reasons I now went back to Windows
on a more capable server (4 CPU / 8 GB RAM) which I thought would be
able to run Geoserver better than the first installation.
But unfortunately the same issue on Windows again. On startup the
service goes up to approx 70%, idles around 1-2 % CPU but still hogs
about 600MB of RAM. Logging into the web admin brings the CPU up to 50%.
The main issue is that a layer request makes it spike at around 90% and
2.5GB RAM and then it just stays there without me making any more
requests. Now it’s game over until after the service is restarted which
by the way is not possible. I have to kill the process and start the
service.
The layer in question is loading an ImageMosaic layer with images on
disk and the time/elevation data in PostgreSQL. A windbarb SLD is
applied to the layer.
Any ideas on where to start troubleshooting this?
Thanks in advance!
Niklas
Geoserver-users mailing list
Please make sure you read the following two resources before posting to this list:
If you want to request a feature or an improvement, also see this: https://github.com/geoserver/geoserver/wiki/Successfully-requesting-and-integrating-new-features-and-improvements-in-GeoServer
Geoserver-users@anonymised.comsts.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-users
Dear all,
just wanted to add that we will be adding the option to disable the OSHI statics gathering by the end of the week (they will be disabled by default), this will allow us to:
- Unblock the situation, once the issue is clearly identified we may think about a fix for the environments where the high CU usage is identified.
- Disable and enable OSHI at runtime.
Kind regards,
Nuno Oliveira
···
Regards,
Nuno Oliveira
==
GeoServer Professional Services from the experts!
Nuno Miguel Carvalho Oliveira
@nmcoliveira
Technical Lead / Project Manager
GeoSolutions Group
phone: +39 0584 962313
fax: +39 0584 1660272
Con riferimento alla normativa sul trattamento dei dati personali (Reg. UE 2016/679 - Regolamento generale sulla protezione dei dati “GDPR”), si precisa che ogni circostanza inerente alla presente email (il suo contenuto, gli eventuali allegati, etc.) è un dato la cui conoscenza è riservata al/i solo/i destinatario/i indicati dallo scrivente. Se il messaggio Le è giunto per errore, è tenuta/o a cancellarlo, ogni altra operazione è illecita. Le sarei comunque grato se potesse darmene notizia.
This email is intended only for the person or entity to which it is addressed and may contain information that is privileged, confidential or otherwise protected from disclosure. We remind that - as provided by European Regulation 2016/679 “GDPR” - copying, dissemination or use of this e-mail or the information herein by anyone other than the intended recipient is prohibited. If you have received this email by mistake, please notify us immediately by telephone or e-mail.