Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

XML parsing slows down WFS and GML loading #12357

Closed
qgib opened this issue Dec 18, 2009 · 5 comments
Closed

XML parsing slows down WFS and GML loading #12357

qgib opened this issue Dec 18, 2009 · 5 comments
Labels
Bug Either a bug report, or a bug fix. Let's hope for the latter! Data Provider Related to specific vector, raster or mesh data providers
Milestone

Comments

@qgib
Copy link
Contributor

qgib commented Dec 18, 2009

Author Name: Paolo Cavallini (@pcav)
Original Redmine Issue: 2297

Redmine category:data_provider
Assignee: nobody -


WFS loading is very slow: I always thought that was due to bandwidth, but now it seems more likely that XML parsing is the culprit (thanks Furieri for noticing!). The same can be see in GML loading from local file. The effect seems particularly heavy on Windows.

@qgib
Copy link
Contributor Author

qgib commented Dec 23, 2009

Author Name: Marco Hugentobler (@mhugent)


Is there a test server instance / test file?
The WFS provider uses a different approach than the GML reader of OGR. So probably they are slow for different reasons.
And yes, reading XML is more demanding performance wise than reading the same information in a binary format.

@qgib
Copy link
Contributor Author

qgib commented Dec 24, 2009

Author Name: Paolo Cavallini (@pcav)


This should be a good and fast server, rather slow to download:

http://webgis.regione.sardegna.it/geoserver/wfs?

@qgib
Copy link
Contributor Author

qgib commented Dec 24, 2009

Author Name: Paolo Cavallini (@pcav)


While loading, the bottleneck seems CPU, that goes up (98-99%)

@qgib
Copy link
Contributor Author

qgib commented Dec 24, 2009

Author Name: Marco Hugentobler (@mhugent)


I tested it with the layer ras:IDT_MN11V_DATI_AGGR_PROV. (22MB) with wget and the WFS plugin. I didn't measure the time exactly, but it seemed comparable to me, appr. 60 - 70 seconds.

The reason the CPU works while loading is that the WFS provider does asynchronous request and starts parsing before the whole document has arrived.

@qgib
Copy link
Contributor Author

qgib commented Dec 27, 2009

Author Name: Paolo Cavallini (@pcav)


So better close it - still unsure about GML though, but this will require more testing, especially on Windows.


  • resolution was changed from to invalid
  • status_id was changed from Open to Closed

@qgib qgib added Bug Either a bug report, or a bug fix. Let's hope for the latter! Data Provider Related to specific vector, raster or mesh data providers labels May 24, 2019
@qgib qgib added this to the Version 1.4.0 milestone May 24, 2019
@qgib qgib closed this as completed May 24, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Bug Either a bug report, or a bug fix. Let's hope for the latter! Data Provider Related to specific vector, raster or mesh data providers
Projects
None yet
Development

No branches or pull requests

1 participant