On mardi 30 avril 2019 15:33:22 CEST Andrea Aime wrote: > On Tue, Apr 30, 2019 at 3:22 PM Even Rouault <[email protected]> > > wrote: > > What is slow exactly ? The first time you do a spatial filtering (which is > > expected, since it requires to do a full scan of the file, because the > > driver > > doesn't know how to use the on-disk spatial index), or later spatial > > filtering > > operations with the connection still opened (which should be fast > > normally) ? > > Oh wait! You mean those messages pop up only if OpenFileGDB is used? > Dang, thought I had forced usage of FileGBD but I did not, very sorry for > the noise. > > The log messages are gone, performance is still really bad. Can I blame > multithreading for that? > All the datasource objects are opened in read only mode
Ah, the FileGDB SDK used by the FileGDB driver was/is not thread-safe, so the FileGDB driver holds a global lock... Even -- Spatialys - Geospatial professional services http://www.spatialys.com _______________________________________________ gdal-dev mailing list [email protected] https://lists.osgeo.org/mailman/listinfo/gdal-dev
