[gdal-dev] Request for advice in unexpected slowdown working with LVBAG

[Jan Heckman]

My c++ utility-app collects Kadaster BAG data in postgresql tables for use
in "populatie service".
It has functioned for several years, with a typical runtime of 40 minutes.
In the process of rounding this off, I updated the gdal binaries from 3.03
to 3.53, as well as added some threaded workloads for analyzing the tables.
Confusingly, the runtime went up to 4 hours and more. This is after the
download, so internet speed has no role here. It's all local, no network
and my PC has not degraded. I have tried to reconstruct an older setup, but
failed to get it back up to speed.
Profiling and random breaks during waiting point conclusively to the
function getting features from a layer.
LVBAG processes lots of xml of a specific (but not highly particular)
structure.
My app is compiled, if so indicated, against expat. Xerces is also a
required dll.
So my first idea was that there might be a serious performance difference
between xml libs, but without direct evidence.
I am using gdal windows binaries from Gisinternals.
All suggestions are welcome!
Thanks in advance,
Jan
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.osgeo.org/pipermail/gdal-dev/attachments/20241110/c08466c7/attachment.htm>