Speed up i18n string lookup
---------------------------
Key: GEOS-3039
URL: http://jira.codehaus.org/browse/GEOS-3039
Project: GeoServer
Issue Type: Improvement
Components: Wicket UI
Affects Versions: 2.0-alpha2
Reporter: Andrea Aime
Assignee: Andrea Aime
Fix For: 2.0-beta1
The current i18n lookup times make it feel like we're still playing with jsps:
the first access to a page is very slow, and what's worse, it happens again on
each startup (jsp take time to load only when they need recompiling).
This is a list of the times it take to open a few pages on a cold startup (and
first time you access them, in order):
home: 2.9s
layers: 2.7s
ws: 1.8s
stores: 2.0s
The attached patch simplifies the i18n lookup so that the times become:
home: 2.0s
layers: 1s
ws: 0.6s
stores: 0.7s
As far as I can see no i18n string is lost, but I could be wrong.
Anyways, if any is lost, in my opinion it would be better to force some strict
convention that eases up the work of the lookup so that we don't have to wait
over and over for the i18n strings to load during development.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
------------------------------------------------------------------------------
The NEW KODAK i700 Series Scanners deliver under ANY circumstances! Your
production scanning environment may not be a perfect world - but thanks to
Kodak, there's a perfect scanner to get the job done! With the NEW KODAK i700
Series Scanner you'll get full speed at 300 dpi even with all image
processing features enabled. http://p.sf.net/sfu/kodak-com
_______________________________________________
Geoserver-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/geoserver-devel
