[Geoserver-users] GeoServer startup time (>2h)

Hi,

I have been experiencing some very long GeoServer startup times - more than 2 hours.

I looked into the logs and found out that geoserver is loading each layer, but at a pace of ~3/sec, which seems very slow, since I have ~14000 of these and will have more…

The rasters are stored on external server accessed via NFS. They are in JPEG2000 format, Geoserver is using Kakadu 6.4 library, has access to 1024MB of RAM (-XX:MaxPermSize=1024m), and the CPU load during startup is ~20%.

So, is there any way to speed this up? Maybe to skip some checking of these layers?

Thank you

Jaroslav Urik

Dear Jaroslav,
please, find my comments inline below…

Regards,

···

On Mon, Oct 26, 2015 at 8:34 AM, Jaroslav Urik <jarda.urik@anonymised.com> wrote:

Hi,

I have been experiencing some very long GeoServer startup times - more than 2 hours.

I looked into the logs and found out that geoserver is loading each layer, but at a pace of ~3/sec, which seems very slow, since I have ~14000 of these and will have more…

This is quite strange.
Can you give us more info about the GeoServer version as well as the output of gdalinfo on a single file?

The rasters are stored on external server accessed via NFS. They are in JPEG2000 format, Geoserver is using Kakadu 6.4 library, has access to 1024MB of RAM (-XX:MaxPermSize=1024m), and the CPU load during startup is ~20%.

One importanto observation, the flag -XX:MaxPermSize has nothing to do with the Heap for GeoServer.
128M is more than enough for this flag, you might want to make sure to use the -Xmx properly.

So, is there any way to speed this up? Maybe to skip some checking of these layers?

Do you really need 14k layers or they are a mosaic, which means 1 layer?

Thank you

Jaroslav Urik



Geoserver-users mailing list
Geoserver-users@anonymised.comsts.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-users

Simone Giannecchini

GeoServer Professional Services from the experts!
Visit http://goo.gl/it488V for more information.

Ing. Simone Giannecchini
@simogeo
Founder/Director

GeoSolutions S.A.S.
Via Poggio alle Viti 1187
55054 Massarosa (LU)
Italy
phone: +39 0584 962313
fax: +39 0584 1660272
mob: +39 333 8128928

http://www.geo-solutions.it
http://twitter.com/geosolutions_it


AVVERTENZE AI SENSI DEL D.Lgs. 196/2003
Le informazioni contenute in questo messaggio di posta elettronica e/o nel/i file/s allegato/i sono da considerarsi strettamente riservate. Il loro utilizzo è consentito esclusivamente al destinatario del messaggio, per le finalità indicate nel messaggio stesso. Qualora riceviate questo messaggio senza esserne il destinatario, Vi preghiamo cortesemente di darcene notizia via e-mail e di procedere alla distruzione del messaggio stesso, cancellandolo dal Vostro sistema. Conservare il messaggio stesso, divulgarlo anche in parte, distribuirlo ad altri soggetti, copiarlo, od utilizzarlo per finalità diverse, costituisce comportamento contrario ai principi dettati dal D.Lgs. 196/2003.

The information in this message and/or attachments, is intended solely for the attention and use of the named addressee(s) and may be confidential or proprietary in nature or covered by the provisions of privacy act (Legislative Decree June, 30 2003, no.196 - Italy’s New Data Protection Code).Any use not in accord with its purpose, any disclosure, reproduction, copying, distribution, or either dissemination, either whole or partial, is strictly forbidden except previous formal approval of the named addressee(s). If you are not the intended recipient, please contact immediately the sender by telephone, fax or e-mail and delete the information in this message that has been received in error. The sender does not give any warranty or accept liability as the content, accuracy or completeness of sent messages and accepts no responsibility for changes made after they were sent or for other risks which arise as a result of e-mail transmission, viruses, etc.

Hi Simone,

I am running Geoserver 2.7.2. The images are mainly old maps in jp2, here is gdalinfo of one of them:

gdalinfo /storage/…/d01/00012_00010_300dpi.jp2
Driver: JP2KAK/JPEG-2000 (based on Kakadu v6.4)
Files: /storage/…/d01/00012_00010_300dpi.jp2
/storage/…/d01/00012_00010_300dpi.wld
Size is 2820, 16419
Coordinate System is `’
Origin = (13.273995359042500,51.310171640957499)
Pixel Size = (0.000343281915000,-0.000343281915000)
Metadata: Corder=RPCL
TIFFTAG_RESOLUTIONUNIT=3 (pixels/cm)
TIFFTAG_XRESOLUTION=118.103
TIFFTAG_YRESOLUTION=118.103
Corner Coordinates:
Upper Left ( 13.2739954, 51.3101716)
Lower Left ( 13.2739954, 45.6738259)
Upper Right ( 14.2420504, 51.3101716)
Lower Right ( 14.2420504, 45.6738259)
Center ( 13.7580229, 48.4919988)
Band 1 Block=2048x128 Type=Byte, ColorInterp=Red
Overviews: 1410x8210, 705x4105, 353x2053, 177x1027, 89x514
Image Structure Metadata:
COMPRESSION=JP2000
Band 2 Block=2048x128 Type=Byte, ColorInterp=Green
Overviews: 1410x8210, 705x4105, 353x2053, 177x1027, 89x514
Image Structure Metadata:
COMPRESSION=JP2000
Band 3 Block=2048x128 Type=Byte, ColorInterp=Blue
Overviews: 1410x8210, 705x4105, 353x2053, 177x1027, 89x514
Image Structure Metadata:
COMPRESSION=JP2000

<<<

Ad. -XX:MaxPermSize: Thank you, I will reconfigure this. The -Xmx is set to 2048M.

Ad. layers: It is 50k (was 14k) of old maps, so I might have mistaken term “layer” for something else, the term “image” might suit it better?
Anyway the Geoserver tells me, that I have 34 Workspaces, 49,721 Stores and 49,660 Layers. If I understand the system correctly, than yes, I need 50k of layers. I am using geoserver to view those maps in openLayers and via wms.

Thank you

Jaroslav

···

Simone Giannecchini

GeoServer Professional Services from the experts!
Visit http://goo.gl/it488V for more information.

Ing. Simone Giannecchini
@simogeo
Founder/Director

GeoSolutions S.A.S.
Via Poggio alle Viti 1187
55054 Massarosa (LU)
Italy
phone: +39 0584 962313
fax: +39 0584 1660272
mob: +39 333 8128928

http://www.geo-solutions.it
http://twitter.com/geosolutions_it


AVVERTENZE AI SENSI DEL D.Lgs. 196/2003
Le informazioni contenute in questo messaggio di posta elettronica e/o nel/i file/s allegato/i sono da considerarsi strettamente riservate. Il loro utilizzo è consentito esclusivamente al destinatario del messaggio, per le finalità indicate nel messaggio stesso. Qualora riceviate questo messaggio senza esserne il destinatario, Vi preghiamo cortesemente di darcene notizia via e-mail e di procedere alla distruzione del messaggio stesso, cancellandolo dal Vostro sistema. Conservare il messaggio stesso, divulgarlo anche in parte, distribuirlo ad altri soggetti, copiarlo, od utilizzarlo per finalità diverse, costituisce comportamento contrario ai principi dettati dal D.Lgs. 196/2003.

The information in this message and/or attachments, is intended solely for the attention and use of the named addressee(s) and may be confidential or proprietary in nature or covered by the provisions of privacy act (Legislative Decree June, 30 2003, no.196 - Italy’s New Data Protection Code).Any use not in accord with its purpose, any disclosure, reproduction, copying, distribution, or either dissemination, either whole or partial, is strictly forbidden except previous formal approval of the named addressee(s). If you are not the intended recipient, please contact immediately the sender by telephone, fax or e-mail and delete the information in this message that has been received in error. The sender does not give any warranty or accept liability as the content, accuracy or completeness of sent messages and accepts no responsibility for changes made after they were sent or for other risks which arise as a result of e-mail transmission, viruses, etc.

On Mon, Oct 26, 2015 at 8:34 AM, Jaroslav Urik <jarda.urik@anonymised.com> wrote:

Hi,

I have been experiencing some very long GeoServer startup times - more than 2 hours.

I looked into the logs and found out that geoserver is loading each layer, but at a pace of ~3/sec, which seems very slow, since I have ~14000 of these and will have more…

This is quite strange.
Can you give us more info about the GeoServer version as well as the output of gdalinfo on a single file?

The rasters are stored on external server accessed via NFS. They are in JPEG2000 format, Geoserver is using Kakadu 6.4 library, has access to 1024MB of RAM (-XX:MaxPermSize=1024m), and the CPU load during startup is ~20%.

One importanto observation, the flag -XX:MaxPermSize has nothing to do with the Heap for GeoServer.
128M is more than enough for this flag, you might want to make sure to use the -Xmx properly.

So, is there any way to speed this up? Maybe to skip some checking of these layers?

Do you really need 14k layers or they are a mosaic, which means 1 layer?

Thank you

Jaroslav Urik



Geoserver-users mailing list
Geoserver-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-users

Hi,
I have a similar question. My layers are loading much faster, about 46 per
second. But with ~30000 of them (and growing), it still takes like 10
minutes to start up Geoserver.

My questions are:
1. Is there a way to speed this up, such as not loading a layer until it's
needed?
2. We have been storing our Raster (GeoTIFF) images on the file system.
Would it have been faster if we store them in a database somehow? Would this
be the more recommended approach?
3. During the Layer loading process, we are not able to do anything with
Geoserver (such as sending a GET request for a layer already loaded). Is
this the expected behavior?
4. I noticed that after Geoserver successfully loaded all the layers, it
then goes through a 'Depersisting' process for some of the layers:

2015-10-26 18:30:30,927 DEBUG [org.geoserver.gwc.layer] - Depersisting
GeoServerTileLayerInfo from
C:\dev\apps\geoserver-2.2.5\data_dir\gwc-layers\LayerGroupInfoImpl--10d71042_1509744aecd_-7ff7.xml
2015-10-26 18:30:30,939 DEBUG [org.geoserver.gwc.layer] - Loaded tile layer
'WV_27893'

which took another few minutes to complete. I'm wondering what does
'Depersisting' do and is there a way to turn it off?

Thank you very much in advance,
Eting

--
View this message in context: http://osgeo-org.1560.x6.nabble.com/GeoServer-startup-time-2h-tp5232511p5232727.html
Sent from the GeoServer - User mailing list archive at Nabble.com.

On Tue, Oct 27, 2015 at 3:14 AM, eting123 <eting@anonymised.com> wrote:

Hi,
I have a similar question. My layers are loading much faster, about 46 per
second. But with ~30000 of them (and growing), it still takes like 10
minutes to start up Geoserver.

My questions are:
1. Is there a way to speed this up, such as not loading a layer until it's
needed?

The time is spent locating and parsing the XML files (not much, but if you
have tens of thousands, it's visible) and checking the layers are ok
(visible).

The JDBCConfig community module dodges both issues by backing stuff
in a database, loading it on demand, and not checking if a layer is actually
usable.

For the core version we could just do the second thing, not test the layers,
that would have to go with caps document generation set to be tolerant
to misconfigured layers (the option is there).
We just need someone to resource this work:
https://github.com/geoserver/geoserver/wiki/Successfully-requesting-and-integrating-new-features-and-improvements-in-GeoServer

2. We have been storing our Raster (GeoTIFF) images on the file system.

Would it have been faster if we store them in a database somehow? Would
this
be the more recommended approach?

Unsure, I have no experience on loading rasters in the database (something
that even Paul Ramsey discourages in his PostGIS presentations though, that
is,
loading them to do display, as opposed to load them to do analysis, which is
the sweet spot of the postgis raster support).

3. During the Layer loading process, we are not able to do anything with
Geoserver (such as sending a GET request for a layer already loaded). Is
this the expected behavior?

Yes, it is expected behavior, loading the catalog is part of the Spring
context
startup, and no request can be served until the catalog is fully loaded
(with
the deafult in memory version).

4. I noticed that after Geoserver successfully loaded all the layers, it
then goes through a 'Depersisting' process for some of the layers:

2015-10-26 18:30:30,927 DEBUG [org.geoserver.gwc.layer] - Depersisting
GeoServerTileLayerInfo from

C:\dev\apps\geoserver-2.2.5\data_dir\gwc-layers\LayerGroupInfoImpl--10d71042_1509744aecd_-7ff7.xml
2015-10-26 18:30:30,939 DEBUG [org.geoserver.gwc.layer] - Loaded tile layer
'WV_27893'

which took another few minutes to complete. I'm wondering what does
'Depersisting' do and is there a way to turn it off?

It's GWC, don't know why it's happening without checking the code and doing
some tests,
a GWC developer might have to chime in to comment on that

Cheers
Andrea

--

GeoServer Professional Services from the experts! Visit
http://goo.gl/it488V for more information.

Ing. Andrea Aime
@geowolf
Technical Lead

GeoSolutions S.A.S.
Via Poggio alle Viti 1187
55054 Massarosa (LU)
Italy
phone: +39 0584 962313
fax: +39 0584 1660272
mob: +39 339 8844549

http://www.geo-solutions.it
http://twitter.com/geosolutions_it

*AVVERTENZE AI SENSI DEL D.Lgs. 196/2003*

Le informazioni contenute in questo messaggio di posta elettronica e/o
nel/i file/s allegato/i sono da considerarsi strettamente riservate. Il
loro utilizzo è consentito esclusivamente al destinatario del messaggio,
per le finalità indicate nel messaggio stesso. Qualora riceviate questo
messaggio senza esserne il destinatario, Vi preghiamo cortesemente di
darcene notizia via e-mail e di procedere alla distruzione del messaggio
stesso, cancellandolo dal Vostro sistema. Conservare il messaggio stesso,
divulgarlo anche in parte, distribuirlo ad altri soggetti, copiarlo, od
utilizzarlo per finalità diverse, costituisce comportamento contrario ai
principi dettati dal D.Lgs. 196/2003.

The information in this message and/or attachments, is intended solely for
the attention and use of the named addressee(s) and may be confidential or
proprietary in nature or covered by the provisions of privacy act
(Legislative Decree June, 30 2003, no.196 - Italy's New Data Protection
Code).Any use not in accord with its purpose, any disclosure, reproduction,
copying, distribution, or either dissemination, either whole or partial, is
strictly forbidden except previous formal approval of the named
addressee(s). If you are not the intended recipient, please contact
immediately the sender by telephone, fax or e-mail and delete the
information in this message that has been received in error. The sender
does not give any warranty or accept liability as the content, accuracy or
completeness of sent messages and accepts no responsibility for changes
made after they were sent or for other risks which arise as a result of
e-mail transmission, viruses, etc.

-------------------------------------------------------

Hi Andrea
Thank you very much for your quick response!

Regarding
"For the core version we could just do the second thing, not test the
layers,
that would have to go with caps document generation set to be tolerant
to misconfigured layers (the option is there).
We just need someone to resource this work:
https://github.com/geoserver/geoserver/wiki/Successfully-requesting-and-integrating-new-features-and-improvements-in-GeoServer&quot;

Since there are 2 main things going on during loading, a) locating and
parsing the layers b) testing the layers, I'm wondering approximately how
much time can be saved by skipping just b)? For example, do you think we can
save half the time or even more?

Thank you very much!
eting

--
View this message in context: http://osgeo-org.1560.x6.nabble.com/GeoServer-startup-time-2h-tp5232511p5232839.html
Sent from the GeoServer - User mailing list archive at Nabble.com.

On Tue, Oct 27, 2015 at 4:26 PM, eting123 <eting@anonymised.com> wrote:

Since there are 2 main things going on during loading, a) locating and
parsing the layers b) testing the layers, I'm wondering approximately how
much time can be saved by skipping just b)? For example, do you think we
can
save half the time or even more?

Yes, testing the layers should be significantly slower than just locating
and parsing the XML
files. How much slower, depends on the nature of the layer, where the data
is,
how expensive the test is (e.g., testing a remote WFS layer is likely going
to be slower
than verifying a local shapefile).

The main question is normally... why do you need 30k layers (and growing)?
Often people publish a ton of files for cases that would be solved by using
a single
image mosaic, or a single layer with time/elevation dimensions.

There are of course also legit cases for such large number of layers,
like someone acting as a service provider, and selling slices of GeoServer
(workspaces) to customers on a cloud platform.

Cheers
Andrea

--

GeoServer Professional Services from the experts! Visit
http://goo.gl/it488V for more information.

Ing. Andrea Aime
@geowolf
Technical Lead

GeoSolutions S.A.S.
Via Poggio alle Viti 1187
55054 Massarosa (LU)
Italy
phone: +39 0584 962313
fax: +39 0584 1660272
mob: +39 339 8844549

http://www.geo-solutions.it
http://twitter.com/geosolutions_it

*AVVERTENZE AI SENSI DEL D.Lgs. 196/2003*

Le informazioni contenute in questo messaggio di posta elettronica e/o
nel/i file/s allegato/i sono da considerarsi strettamente riservate. Il
loro utilizzo è consentito esclusivamente al destinatario del messaggio,
per le finalità indicate nel messaggio stesso. Qualora riceviate questo
messaggio senza esserne il destinatario, Vi preghiamo cortesemente di
darcene notizia via e-mail e di procedere alla distruzione del messaggio
stesso, cancellandolo dal Vostro sistema. Conservare il messaggio stesso,
divulgarlo anche in parte, distribuirlo ad altri soggetti, copiarlo, od
utilizzarlo per finalità diverse, costituisce comportamento contrario ai
principi dettati dal D.Lgs. 196/2003.

The information in this message and/or attachments, is intended solely for
the attention and use of the named addressee(s) and may be confidential or
proprietary in nature or covered by the provisions of privacy act
(Legislative Decree June, 30 2003, no.196 - Italy's New Data Protection
Code).Any use not in accord with its purpose, any disclosure, reproduction,
copying, distribution, or either dissemination, either whole or partial, is
strictly forbidden except previous formal approval of the named
addressee(s). If you are not the intended recipient, please contact
immediately the sender by telephone, fax or e-mail and delete the
information in this message that has been received in error. The sender
does not give any warranty or accept liability as the content, accuracy or
completeness of sent messages and accepts no responsibility for changes
made after they were sent or for other risks which arise as a result of
e-mail transmission, viruses, etc.

-------------------------------------------------------

Good question and I have been thinking about the same thing, whether we
should have done this differently by combining the layers.

I'm wondering how scalable is an image mosaic? If we currently have 30,000
layers, should we put all of them into a single Image Mosaic? At which point
should we consider separating things into a separate mosaic?

Thank you very much for your help
eting

--
View this message in context: http://osgeo-org.1560.x6.nabble.com/GeoServer-startup-time-2h-tp5232511p5232855.html
Sent from the GeoServer - User mailing list archive at Nabble.com.

On Tue, Oct 27, 2015 at 4:57 PM, eting123 <eting@anonymised.com> wrote:

Good question and I have been thinking about the same thing, whether we
should have done this differently by combining the layers.

I'm wondering how scalable is an image mosaic? If we currently have 30,000
layers, should we put all of them into a single Image Mosaic? At which
point
should we consider separating things into a separate mosaic?

The mosaic can have hundreds of thousands of files inside its index (if the
index is a dbms), the main question is,
how many do you have to open in order to produce the output image?

That number should be small, significantly less than 100 if possible

Cheers
Andrea

--

GeoServer Professional Services from the experts! Visit
http://goo.gl/it488V for more information.

Ing. Andrea Aime
@geowolf
Technical Lead

GeoSolutions S.A.S.
Via Poggio alle Viti 1187
55054 Massarosa (LU)
Italy
phone: +39 0584 962313
fax: +39 0584 1660272
mob: +39 339 8844549

http://www.geo-solutions.it
http://twitter.com/geosolutions_it

*AVVERTENZE AI SENSI DEL D.Lgs. 196/2003*

Le informazioni contenute in questo messaggio di posta elettronica e/o
nel/i file/s allegato/i sono da considerarsi strettamente riservate. Il
loro utilizzo è consentito esclusivamente al destinatario del messaggio,
per le finalità indicate nel messaggio stesso. Qualora riceviate questo
messaggio senza esserne il destinatario, Vi preghiamo cortesemente di
darcene notizia via e-mail e di procedere alla distruzione del messaggio
stesso, cancellandolo dal Vostro sistema. Conservare il messaggio stesso,
divulgarlo anche in parte, distribuirlo ad altri soggetti, copiarlo, od
utilizzarlo per finalità diverse, costituisce comportamento contrario ai
principi dettati dal D.Lgs. 196/2003.

The information in this message and/or attachments, is intended solely for
the attention and use of the named addressee(s) and may be confidential or
proprietary in nature or covered by the provisions of privacy act
(Legislative Decree June, 30 2003, no.196 - Italy's New Data Protection
Code).Any use not in accord with its purpose, any disclosure, reproduction,
copying, distribution, or either dissemination, either whole or partial, is
strictly forbidden except previous formal approval of the named
addressee(s). If you are not the intended recipient, please contact
immediately the sender by telephone, fax or e-mail and delete the
information in this message that has been received in error. The sender
does not give any warranty or accept liability as the content, accuracy or
completeness of sent messages and accepts no responsibility for changes
made after they were sent or for other risks which arise as a result of
e-mail transmission, viruses, etc.

-------------------------------------------------------

For our purposes, we actually always show just one GeoTIFF at one time,
that's why we decided to have them as individual layers.

So if we change this to an image mosaic, we will still just open one GeoTIFF
at a time. So the purpose of the image mosaic is solely for performance
reasons, not that we need to 'group' anything together. Would this be the
correct use of an image mosaic?

Thank you,
eting

--
View this message in context: http://osgeo-org.1560.x6.nabble.com/GeoServer-startup-time-2h-tp5232511p5232874.html
Sent from the GeoServer - User mailing list archive at Nabble.com.

Hi eting,

I have a short experience with ImageMosaic datastores. I think you might be interested.

We have an installation with approximately 14000 GeoTiffs (and growing) organized into several Image Mosaic layers. The starting time is just a minute or two and geoserver is able to serve them smoothly (no noticeable difference to individual GeoTiff layers). We serve multidimensional meteorological datasets (forecasts with time, forecast hour and sometimes ensemble dimensions) so it makes a lot of sense to use Image Mosaic datastores. For example we are able to iterate over all forecasts for a given runtime of a meteorological model.

Cheers,

Peter

--

Peter Kovac
IMS Programmer
MicroStep-MIS
http://www.microstep-mis.com
peter.kovac@anonymised.com

On 27. 10. 2015 16:57, eting123 wrote:

Good question and I have been thinking about the same thing, whether we
should have done this differently by combining the layers.

I'm wondering how scalable is an image mosaic? If we currently have 30,000
layers, should we put all of them into a single Image Mosaic? At which point
should we consider separating things into a separate mosaic?

Thank you very much for your help
eting

--
View this message in context: http://osgeo-org.1560.x6.nabble.com/GeoServer-startup-time-2h-tp5232511p5232855.html
Sent from the GeoServer - User mailing list archive at Nabble.com.

------------------------------------------------------------------------------
_______________________________________________
Geoserver-users mailing list
Geoserver-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-users

--
Peter Kovac
IMS Programmer
MicroStep-MIS
peter.kovac@anonymised.com

On Tue, Oct 27, 2015 at 5:46 PM, eting123 <eting@anonymised.com> wrote:

For our purposes, we actually always show just one GeoTIFF at one time,
that's why we decided to have them as individual layers.

So if we change this to an image mosaic, we will still just open one
GeoTIFF
at a time. So the purpose of the image mosaic is solely for performance
reasons, not that we need to 'group' anything together. Would this be the
correct use of an image mosaic?

Yes, just created a index in a database, add a field that you will use to
identify
the specific tiff file you want, and pass a cql filter matching the layer
you desire.

The only drawback I see is that clients won't have a notion of the bbox of
that particular image, but only of the entire mosaic... although, you can
also
publish the index, or a view of it, as a WFS layer, and have the clients
go though that to discover the location of the data (for "zoom on selection"
purposes).

Cheers
Andrea

--

GeoServer Professional Services from the experts! Visit
http://goo.gl/it488V for more information.

Ing. Andrea Aime
@geowolf
Technical Lead

GeoSolutions S.A.S.
Via Poggio alle Viti 1187
55054 Massarosa (LU)
Italy
phone: +39 0584 962313
fax: +39 0584 1660272
mob: +39 339 8844549

http://www.geo-solutions.it
http://twitter.com/geosolutions_it

*AVVERTENZE AI SENSI DEL D.Lgs. 196/2003*

Le informazioni contenute in questo messaggio di posta elettronica e/o
nel/i file/s allegato/i sono da considerarsi strettamente riservate. Il
loro utilizzo è consentito esclusivamente al destinatario del messaggio,
per le finalità indicate nel messaggio stesso. Qualora riceviate questo
messaggio senza esserne il destinatario, Vi preghiamo cortesemente di
darcene notizia via e-mail e di procedere alla distruzione del messaggio
stesso, cancellandolo dal Vostro sistema. Conservare il messaggio stesso,
divulgarlo anche in parte, distribuirlo ad altri soggetti, copiarlo, od
utilizzarlo per finalità diverse, costituisce comportamento contrario ai
principi dettati dal D.Lgs. 196/2003.

The information in this message and/or attachments, is intended solely for
the attention and use of the named addressee(s) and may be confidential or
proprietary in nature or covered by the provisions of privacy act
(Legislative Decree June, 30 2003, no.196 - Italy's New Data Protection
Code).Any use not in accord with its purpose, any disclosure, reproduction,
copying, distribution, or either dissemination, either whole or partial, is
strictly forbidden except previous formal approval of the named
addressee(s). If you are not the intended recipient, please contact
immediately the sender by telephone, fax or e-mail and delete the
information in this message that has been received in error. The sender
does not give any warranty or accept liability as the content, accuracy or
completeness of sent messages and accepts no responsibility for changes
made after they were sent or for other risks which arise as a result of
e-mail transmission, viruses, etc.

-------------------------------------------------------

Thank you very much Andrea and Peter for your help! We will look into using
an image mosaic.

Thanks,
eting

--
View this message in context: http://osgeo-org.1560.x6.nabble.com/GeoServer-startup-time-2h-tp5232511p5232937.html
Sent from the GeoServer - User mailing list archive at Nabble.com.