Hi Stephen,
Inevitably you can't have a single image file that's TB-size (or even 5+GB)
so you'll have thousands, and overviews with mosaicing won't particularly
help - when you render a "zoomed out" view of the layer, the server has to
do a tonne of IO to access thousands of 10px x 10px overviews from each of
the relevant tiles. OTOH, with a pyramid, the imagery is retiled at each
"level" so the server has to read less imagery (normally a maximum of 4x
tiles) to render a single response.
You might find it helpful to add overviews (eg. 2x) to pyramid images and
render fewer pyramid levels (eg. 1x 4x 16x rather than 1x 2x 4x 8x 16x) -
but there are a number of different aspects (disk performance, storage/size
constraints, image format, compression, tile size, memory, CPU) which *all*
interact in weird & wonderful ways to affect performance - so you'll need
to do some testing in your environment to see what works for you.
HTH, good luck!
Rob :)
--
*Koordinates*PO Box 1604, Shortland St, Auckland 1140, New Zealand
Phone +64-9-966 0433 koordinates.com <https://koordinates.com/about>
------------------------------------------------------------------------------
Infragistics Professional
Build stunning WinForms apps today!
Reboot your WinForms applications with our WinForms controls.
Build a bridge from your legacy apps to the future.
http://pubads.g.doubleclick.net/gampad/clk?id=153845071&iu=/4140/ostg.clktrk
_______________________________________________
Geoserver-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/geoserver-users
