Hi,
You can check the structure of your source image with gdalinfo utility
http://www.gdal.org/gdalinfo.html. Most important thing in this case is this:
Band 1 Block=16645x1 Type=Byte, ColorInterp=Palette
Large tiff files which are organised in rows are unsuitable for servers which
need a fast access to arbitrary regions inside the image. Also this image is
without overviews which are ready made subsampled versions of the image.
Read Setup Geotiff data for fast rendering from
http://docs.geoserver.org/stable/en/user/production/data.html?,<http://docs.geoserver.org/stable/en/user/production/data.html>
follow the insructions for making an internally tiled tiff with overviews and
you will get much faster service.
-Jukka Rahkonen-
________________________________
Lähettäjä: Scott Murphy <sc...@alwaysvip.com>
Lähetetty: 29. elokuuta 2017 21:04
Vastaanottaja: geoserver-users@lists.sourceforge.net
Aihe: [Geoserver-users] Slow 2-4 second WMS tile rendering from GeoTIFF Store
Hello Everyone,
I am new to GeoServer and I just had a performance question. I am interested
in displaying the Federal Aviation Administrations pilot charts. I attempted to
store a chart on geoserver, but it seems very slow when I preview it in
OpenLayers. Each tile takes anywhere from 2 to 4 seconds to load.
The source Los_Angeles_SEC_101.tif file is 69 MB and is available for download
here:
http://aeronav.faa.gov/content/aeronav/sectional_files/Los_Angeles_101.zip
Which was listed on this page:
https://www.faa.gov/air_traffic/flight_info/aeronav/digital_products/vfr/
Here are the steps I used to set up my GeoServer.
1. I deployed tomcat on Amazon Web Services then copied geoserver.war with
the chart added inside the data folder.
2. http://geoserver2.us-east-1.elasticbeanstalk.com/web/
3. Changed Administrator password
4. Deleted all existing workspaces
5. Created a new workspace faa
6. Add a new Store
* GeoTIFF
* Workspace: faa
* Data Source Name: Los Angeles
* Description: 101 - Jun 22 2017
* Enabled: checked
* URL: file:data/Los_Angeles_101/Los_Angeles_SEC_101.tif
7. New Layer - Los_Angeles_SEC_101
* Publish
* Data
* Declared SRS - I am guess on this one. I chose
WRF_Lambert_Conformal_Conic 2
* SRS handling - I am guess on this one. I chose keep native
* Save
8. Layer Preview
9.
http://geoserver2.us-east-1.elasticbeanstalk.com/faa/wms?service=WMS&version=1.1.0&request=GetMap&layers=faa:Los_Angeles_SEC_101&styles=&bbox=-351020.4576958068,-245067.92468142207,353646.13725918817,277738.9876785168&width=768&height=569&srs=EPSG:45555&format=application/openlayers
10. If I hit the zoom out button 3 times, I see my chart.
Now if I try and move around, zoom in and out, etc. Each tile takes anywhere
from 2-4 seconds. I really need a solution that can render in less than 500ms.
Is this possible? What do I need to do to get the server responding faster?
Best,
Scott
------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
_______________________________________________
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
Geoserver-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-users
