Sina Abolhoseini ( 
https://osgeo-org.atlassian.net/secure/ViewProfile.jspa?accountId=712020%3A4932e1ef-d7c0-49d4-b1ca-060a321e85ff
 ) *created* an issue

GeoServer ( 
https://osgeo-org.atlassian.net/browse/GEOS?atlOrigin=eyJpIjoiYTE1YTExNmJiM2Y2NDc0MzkwZDAzMzRhNDg3Mzg4ZDQiLCJwIjoiaiJ9
 ) / Bug ( 
https://osgeo-org.atlassian.net/browse/GEOS-11034?atlOrigin=eyJpIjoiYTE1YTExNmJiM2Y2NDc0MzkwZDAzMzRhNDg3Mzg4ZDQiLCJwIjoiaiJ9
 ) GEOS-11034 ( 
https://osgeo-org.atlassian.net/browse/GEOS-11034?atlOrigin=eyJpIjoiYTE1YTExNmJiM2Y2NDc0MzkwZDAzMzRhNDg3Mzg4ZDQiLCJwIjoiaiJ9
 ) Slow initial loading of layers in Geoserver from huge COGs stored in a AWS 
S3 ( 
https://osgeo-org.atlassian.net/browse/GEOS-11034?atlOrigin=eyJpIjoiYTE1YTExNmJiM2Y2NDc0MzkwZDAzMzRhNDg3Mzg4ZDQiLCJwIjoiaiJ9
 )

Issue Type: Bug Affects Versions: 2.22.3 Assignee: Unassigned Components: 
Community modules Created: 17/Jun/23 3:59 PM Environment:

Geoserver version is: 2.22.3
Web server is: Tomcat 9
OS is: Ubuntu

Priority: Medium Reporter: Sina Abolhoseini ( 
https://osgeo-org.atlassian.net/secure/ViewProfile.jspa?accountId=712020%3A4932e1ef-d7c0-49d4-b1ca-060a321e85ff
 )

Hello,

I am working with huge COGs (around 500GB) stored on my private S3 bucket. I am 
trying to publish these COGs as GeoTiff layers using COG community module in 
Geoserver. The Geoserver is deployed on an EC2 instance with 8 vCPUs and 16Gb 
of RAM. The projection system of COGs is WGS84 (EPSG:4326) and I want to access 
the WMS in WGS84.

The layers are published successfully, but when I want to access the WMS of 
these layers, the initial loading of the layers take about a couple of minutes. 
But when they are loaded, everything works smoothly and tiles are loaded pretty 
quick. Also, when the COG is smaller in size (less than 2GB), the initial 
loading is pretty good.

I realized that first thing Geoserver does, is to load the header of the COG 
and then access the inner tiles. By default, Geoserver reads first 16KB of COGs 
to access the header. I have tried to increase 
it.geosolutions.cog.default.header.length so that a larger portion of the COG 
is read initially. But, it ended up slower loading of COGs.

( 
https://osgeo-org.atlassian.net/browse/GEOS-11034#add-comment?atlOrigin=eyJpIjoiYTE1YTExNmJiM2Y2NDc0MzkwZDAzMzRhNDg3Mzg4ZDQiLCJwIjoiaiJ9
 ) Add Comment ( 
https://osgeo-org.atlassian.net/browse/GEOS-11034#add-comment?atlOrigin=eyJpIjoiYTE1YTExNmJiM2Y2NDc0MzkwZDAzMzRhNDg3Mzg4ZDQiLCJwIjoiaiJ9
 )

Get Jira notifications on your phone! Download the Jira Cloud app for Android ( 
https://play.google.com/store/apps/details?id=com.atlassian.android.jira.core&referrer=utm_source%3DNotificationLink%26utm_medium%3DEmail
 ) or iOS ( 
https://itunes.apple.com/app/apple-store/id1006972087?pt=696495&ct=EmailNotificationLink&mt=8
 ) This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100227- 
sha1:5147d46 )
_______________________________________________
Geoserver-devel mailing list
Geoserver-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-devel

Reply via email to