Hi,
it seems that's it's fairly easy to reproduce... well, I'd suggest you open
a bug report and add all
these details into it. Hopefully it's something easy to fix that we can put
in the monthly bug fix
code sprint queue (which still does not guarantee any fix for date, but
gives it a more attention).
Cheers
Andrea
On Fri, Aug 25, 2017 at 4:17 PM, tõnis kärdi <[email protected]> wrote:
> Andrea, Jukka,
>
> since I can't publish gibberish on our production server, I did some
> with a local fresh 2.11.2 stable bin installation, using shapefiles
> and three different native SRSs - EPSG:3035, EPSG:4326 and EPSG:3301.
> All the required DATA_DIR files to rerun this are available at
> https://drive.google.com/drive/folders/0BwPIVpJhp8rHbzhUWk9VSV9FSGM.
> Some chrome screenshots aswell at
> https://drive.google.com/drive/folders/0BwPIVpJhp8rHUEUyNTBvVDFya1E.
>
> But in conclusion:
>
> data native in EPSG:3301 (data/test/puurkaev_3301.shp)
> [1] WMS 1.1.1 takes ~ 0.2 s. see img/EPSG3301_1.1.1.png in the screenshots
> dir
> [2] WMS 1.3.0 takes ~ 4.7 s. see img/EPSG3301_1.3.0.png
>
> data native in EPSG:3035 (data/test/puurkaev_3035.shp)
> [3] WMS 1.1.1 takes ~ 0.2 s. see img/EPSG3035_1.1.1.png
> [4] WMS 1.3.0 takes ~ 3.9 s. see img/EPSG3035_1.3.0.png
>
> data native in EPSG:4326 (data/test/puurkaev_4326.shp)
> [5] WMS 1.1.1 takes < 0.2 s. see img/EPSG4326_1.1.1.png
> [6] WMS 1.3.0 takes < 0.2 s. see img/EPSG4326_1.3.0.png
>
> data native in EPSG:4326 (data/test/puurkaev_4326.shp) but requested
> in EPSG:3301
> [7] WMS 1.1.1 takes < 0.5 s. see img/EPSG4326_to_EPSG3301_1.1.1.png
> [8] WMS 1.3.0 takes < 0.5 s. see img/EPSG4326_to_EPSG3301_1.3.0.png
>
> Request URLs aswell for the sake of making it easier to repeat the
> requests :)
>
> [1] http://localhost:8080/geoserver/test/wms?SERVICE=
> WMS&VERSION=1.1.1&REQUEST=GetMap&FORMAT=image%2Fpng&
> TRANSPARENT=true&LAYERS=puurkaev_3301&STYLES=point&
> SRS=EPSG%3A3301&WIDTH=768&HEIGHT=486&BBOX=320676.1358612784%2C6349387.
> 490053313%2C789779.5117497771%2C6646241.970107753
>
> [2] http://localhost:8080/geoserver/test/wms?SERVICE=
> WMS&VERSION=1.3.0&REQUEST=GetMap&FORMAT=image%2Fpng&
> TRANSPARENT=true&LAYERS=puurkaev_3301&STYLES=point&
> CRS=EPSG%3A3301&WIDTH=768&HEIGHT=486&BBOX=6349387.
> 490053313,320676.1358612784,6646241.970107753,789779.5117497771
>
> [3] http://localhost:8080/geoserver/test/wms?SERVICE=
> WMS&VERSION=1.1.1&REQUEST=GetMap&FORMAT=image%2Fpng&
> TRANSPARENT=true&LAYERS=puurkaev_3035&STYLES=point&
> SRS=EPSG%3A3035&WIDTH=768&HEIGHT=525&BBOX=4953071.972760203%2C3888121.
> 7958570817%2C5422175.348648702%2C4208797.93171836
>
> [4] http://localhost:8080/geoserver/test/wms?SERVICE=
> WMS&VERSION=1.3.0&REQUEST=GetMap&FORMAT=image%2Fpng&
> TRANSPARENT=true&LAYERS=puurkaev_3035&STYLES=point&
> CRS=EPSG%3A3035&WIDTH=768&HEIGHT=525&BBOX=3888121.
> 7958570817,4953071.972760203,4208797.93171836,5422175.348648702
>
> [5] http://localhost:8080/geoserver/test/wms?SERVICE=
> WMS&VERSION=1.1.1&REQUEST=GetMap&FORMAT=image%2Fpng&
> TRANSPARENT=true&LAYERS=puurkaev_4326&STYLES=point&
> SRS=EPSG%3A4326&WIDTH=768&HEIGHT=330&BBOX=20.7861328125%
> 2C56.788330078125%2C29.2236328125%2C60.413818359375
>
> [6] http://localhost:8080/geoserver/test/wms?SERVICE=
> WMS&VERSION=1.3.0&REQUEST=GetMap&FORMAT=image%2Fpng&
> TRANSPARENT=true&LAYERS=puurkaev_4326&STYLES=point&
> CRS=EPSG%3A4326&WIDTH=768&HEIGHT=330&BBOX=56.
> 788330078125,20.7861328125,60.413818359375,29.2236328125
>
> [7] http://localhost:8080/geoserver/test/wms?SERVICE=
> WMS&VERSION=1.1.1&REQUEST=GetMap&FORMAT=image%2Fpng&
> TRANSPARENT=true&LAYERS=puurkaev_4326&STYLES=point&
> SRS=EPSG%3A3301&WIDTH=768&HEIGHT=486&BBOX=320676.1358612784%2C6349387.
> 490053313%2C789779.5117497771%2C6646241.970107753
>
> [8] http://localhost:8080/geoserver/test/wms?SERVICE=
> WMS&VERSION=1.3.0&REQUEST=GetMap&FORMAT=image%2Fpng&
> TRANSPARENT=true&LAYERS=puurkaev_4326&STYLES=point&
> CRS=EPSG%3A3301&WIDTH=768&HEIGHT=486&BBOX=6349387.
> 490053313,320676.1358612784,6646241.970107753,789779.5117497771
>
>
> All the best,
> Tõnis
>
>
> 2017-08-25 15:21 GMT+03:00 tõnis kärdi <[email protected]>:
> > Yes, it's EPSG:3301 natively aswell. I haven't tried data with any
> > other SRS, but I can give it a try. Will post back.
> >
> > All the best,
> > Tõins
> >
> > 2017-08-25 14:53 GMT+03:00 Andrea Aime <[email protected]>:
> >> I checked the capabilities document, it seems that layer is natively in
> >> 3301... can you confirm?
> >> Does it happen also if the native data is in some other coordinate
> reference
> >> system?
> >>
> >> Cheers
> >> Andrea
> >>
> >> On Fri, Aug 25, 2017 at 1:39 PM, Rahkonen Jukka (MML)
> >> <[email protected]> wrote:
> >>>
> >>> Hi,
> >>>
> >>> I tried the links and also made a simple test for making sure that
> >>> Geoserver knows that EPSG:3301 is a northing-easting system. It seems
> to
> >>> know because this request with non-flipped BBOX returns an empty map
> that is
> >>> correct.
> >>>
> >>>
> >>> https://gsavalik.envir.ee/geoserver/eelis/ows?SERVICE=
> WMS&VERSION=1.3.0&REQUEST=GetMap&FORMAT=image%2Fpng&
> TRANSPARENT=true&LAYERS=eelis%3Akr_puurkaev&STYLES=point&
> CRS=EPSG%3A3301&WIDTH=1432&HEIGHT=906&BBOX=372111.0,
> 6382027.0,738667.0,6614170.0
> >>>
> >>> So it feels like there is some real issue.
> >>>
> >>> -Jukka Rahkonen-
> >>>
> >>> -----Alkuperäinen viesti-----
> >>> Lähettäjä: tõnis kärdi [mailto:[email protected]]
> >>> Lähetetty: 25. elokuuta 2017 13:49
> >>> Vastaanottaja: [email protected]
> >>> Aihe: [Geoserver-users] response time of WMS 1.3.0 vs WMS 1.x.x
> >>>
> >>> Hello,
> >>>
> >>> I came upon this just by accident but it seems that GeoServer WMS
> GetMap
> >>> response times for WMS 1.3.0 are longer than those of WMS 1.x.
> >>> If the number of features to be rendered in the response is small then
> the
> >>> difference is not that noticable. But if for example with 20K+ point
> >>> features the difference becomes noticable, e.g.
> >>>
> >>> WMS 1.1.1
> >>> https://gsavalik.envir.ee/geoserver/eelis/ows?SERVICE=
> WMS&VERSION=1.1.1&REQUEST=GetMap&FORMAT=image%2Fpng&
> TRANSPARENT=true&LAYERS=eelis%3Akr_puurkaev&STYLES=point&
> SRS=EPSG%3A3301&WIDTH=1432&HEIGHT=906&BBOX=372111.0,
> 6382027.0,738667.0,6614170.0
> >>> takes around 3 seconds to return
> >>>
> >>> WMS 1.3.0
> >>> https://gsavalik.envir.ee/geoserver/eelis/ows?SERVICE=
> WMS&VERSION=1.3.0&REQUEST=GetMap&FORMAT=image%2Fpng&
> TRANSPARENT=true&LAYERS=eelis%3Akr_puurkaev&STYLES=point&
> CRS=EPSG%3A3301&WIDTH=1432&HEIGHT=906&BBOX=6382027.0,
> 372111.0,6614170.0,738667.0
> >>> gets a timeout, but I've checked it with a longer timeout setting and
> it
> >>> returns in 30+ seconds
> >>>
> >>> Catching the executed SQL from geoserver.log for either request and
> >>> executing it in the database yields no significant time difference (<
> >>> 50 ms)
> >>>
> >>> switching image/png with image/jpeg makes no difference. Also
> requesting
> >>> for FORMAT=application/json;type=geojson (using the vector tiles
> plugin)
> >>> results in ~ 4x response time diff for WMS 1.3.0 and 1.x.
> >>>
> >>> I've checked with different configurations but the issue remains the
> same:
> >>>
> >>> Geoserver 2.8.1 (war deploy), data in a PostgreSQL/PostGIS database
> >>> GeoServer 2.9.1 (bin deploy), data in a SpatiaLite database GeoServer
> 2.11.2
> >>> (bin deploy), data in a PostgreSQL/PostGIS database
> >>>
> >>> Just for checking that I'm not raving mad, here's sample queries for
> >>> another public gs instance (I'm not affiliated with this one so I
> don't know
> >>> about the setup :)):
> >>>
> >>>
> >>> https://kls.pria.ee/geoserver/avk/wms?SERVICE=WMS&VERSION=1.
> 1.1&REQUEST=GetMap&FORMAT=image%2Fpng&TRANSPARENT=true&
> LAYERS=avk:mesilased&STYLES=avk:mesilased&SRS=EPSG%3A3301&
> WIDTH=1432&HEIGHT=906&BBOX=372111.0,6382027.0,738667.0,6614170.0
> >>> takes around 0.2+ seconds to return
> >>>
> >>> vs
> >>>
> >>>
> >>> https://kls.pria.ee/geoserver/avk/wms?SERVICE=WMS&VERSION=1.
> 3.0&REQUEST=GetMap&FORMAT=image%2Fpng&TRANSPARENT=true&
> LAYERS=avk:mesilased&STYLES=avk:mesilased&CRS=EPSG%3A3301&
> WIDTH=1432&HEIGHT=906&BBOX=6382027.0,372111.0,6614170.0,738667.0
> >>> takes around 1.5+ seconds to return
> >>>
> >>> Is there any known issue with this that I've totally missed or have I
> >>> messed something up in the configuration?
> >>>
> >>> All the best,
> >>> Tõnis
> >>>
> > ...
>
--
Regards,
Andrea Aime
==
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 di Montramito 3/A
55054 Massarosa (LU)
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.
------------------------------------------------------------------------------
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
[email protected]
https://lists.sourceforge.net/lists/listinfo/geoserver-users
