Timeline for Do large vertex counts in PostGIS cause performance issues in WMS?
Current License: CC BY-SA 3.0
5 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Aug 6, 2014 at 14:36 | comment | added | Paul Ramsey | @StephenLead, right the output image will be the same size regardless. I let my database-guy self get out in front: in order to get the feature from the database to the renderer, it usually also has to traverse a network link. There's an overhead to that too, particularly as objects get big. There's also an overhead to just ripping that much data up off the disk into memory. | |
| Aug 6, 2014 at 12:06 | comment | added | Stephen Lead | @Rino cool, that's what I figured. Hence my questioning about the network bandwidth. I don't believe that will vary for a more complex object, but the processing speed will vary. | |
| Aug 6, 2014 at 8:53 | comment | added | Rino | @Stephen Lead Yes the server is delivering images in WMS protocol, and yes, WMS image size stays the same regardless of the geometry complexity. But I was guessing that geometry with larger vertex count takes more computing power for rendering WMS images. Hence the performance issue lies in the effort of image rendering, not than in the effort for sending the image to the client. Now it is answered that large vertex count does cause performance. | |
| Aug 5, 2014 at 23:08 | comment | added | Stephen Lead | re: " A 1M vertex object will take up 32 Megabytes" - since the question is for WMS (and hence the server is delivering an image), wouldn't the size of the image be the same, regardless of the complexity of the underlying data? | |
| Aug 5, 2014 at 22:28 | history | answered | Paul Ramsey | CC BY-SA 3.0 |