We tend to not worry too much about the web admin performance ... since the
point of geoserver is the web services accessed by desktop/mobile/web
clients.

As such I do not believe there is any caching in your way. With that in
mind any slowdown may be:
- all the components loading (if it is only slow when first time)
- a session being setup (if it is slow when logging in a second time on an
additional machine).

I did notice it be a bit slower when we introduced some url randomization
to address a security concern (where a URL can be predicted). My guess is
that is a tradeoff between security, and performance. And as and since we
only expect one or two admins in there at any one time security is the
right call. See this kind of thing
<https://docs.geoserver.org/latest/en/user/security/webadmin/settings.html#encryption>
in the user manual.
--
Jody Garnett


On Fri, 8 May 2020 at 01:45, Overkamp, Stefan <[email protected]> wrote:

> Hi list,
>
>
>
> testing Geoserver 2.17.0 the web administration app has become very slow.
>
> With the first access to an administration part (e.g. Layers) I have to
> wait 15 seconds.
>
> The following access is fast as in 2.16.2
>
>
>
> Accessing this administration part from a different PC is fast too.
>
> So maybe there is some sort of caching.
>
> Is there any way to pre cache the web gui?
>
>
>
>
>
> Mit freundlichen Grüßen
> Im Auftrag
>
> *Stefan Overkamp *
>
> Team Geodaten-Technik
> *Referat Geoinformation und Raumbeobachtung*
>
> Kronprinzenstraße 6
> 45128 Essen
>
> T:
> F:
>
> +49 201 2069-700
> +49 201 2069-369
>
>
>
> [email protected]
>
>
>
>
> Alle Informationen zum Jubiläum unter: 100jahre.rvr.ruhr
>
> *Regionalverband Ruhr *
> Die Regionaldirektorin
>
> Kronprinzenstraße 35
> 45128 Essen
> T: +49 201 2069-0
> F: +49 201 2069-500
> www.rvr.ruhr
>
> Postfach 10 32 64 | 45032 Essen
> Steuernummer: 112/5797/0116 | USt.-ldNr.: DE 173867500
>
> Diese E-Mail könnte vertrauliche und/oder rechtlich geschützte
> Informationen enthalten. Wenn Sie nicht der richtige Adressat sind oder
> diese E- Mail irrtümlich erhalten haben, informieren Sie bitte sofort den
> Absender und vernichten Sie diese Mail. Das unerlaubte Kopieren sowie die
> unbefugte Weitergabe dieser E-Mail sind nicht gestattet.
> This e-mail may contain confidential and/or privileged information. If you
> are not the intended recipient (or have received this e-mail in error)
> please notify the sender immediately and destroy this e-mail. Any
> unauthorised copying, disclosure or distribution of the material in this
> e-mail is strictly forbidden.
> _______________________________________________
> 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
>
>
> [email protected]
> https://lists.sourceforge.net/lists/listinfo/geoserver-users
>
_______________________________________________
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


[email protected]
https://lists.sourceforge.net/lists/listinfo/geoserver-users

Reply via email to