Re: [gdal-dev] Multithread deadlock

Thank you so much Even. It is working like a charm! -Original Message- From: Even Rouault [mailto:even.roua...@spatialys.com] Sent: 30 September, 2016 01:05 To: gdal-dev@lists.osgeo.org Cc: Francisco Javier Calzado Subject: Re: [gdal-dev] Multithread deadlock > I don't think th

Re: [gdal-dev] Multithread deadlock

Cache() on dataset destructor. -Original Message- From: Even Rouault [mailto:even.roua...@spatialys.com] Sent: 27 September, 2016 19:16 To: Francisco Javier Calzado Cc: gdal-dev@lists.osgeo.org Subject: Re: [gdal-dev] Multithread deadlock Le mardi 27 septembre 2016 16:35:26, Francisco Javi

Re: [gdal-dev] Multithread deadlock

Thanks, BR. Javier. -Original Message- From: gdal-dev [mailto:gdal-dev-boun...@lists.osgeo.org] On Behalf Of Francisco Javier Calzado Sent: 27 September, 2016 09:50 To: Even Rouault ; gdal-dev@lists.osgeo.org Subject: Re: [gdal-dev]

Re: [gdal-dev] Multithread deadlock

Hi Even, Thanks for such a quick fix! I'm gonna apply the patch and recompile GDAL and will let you know :) Keep in touch. Best Regards, Javier Calzado -Original Message- From: Even Rouault [mailto:even.roua...@spatialys.com] Sent: 26 September, 2016 17:53 To: gda

Re: [gdal-dev] Multithread deadlock

ourcefilePath, > std::basic_string,std::allocator > > targetFilePath, int threadID) Line 66 C++ From: Andrew Bell [mailto:andrew.bell...@gmail.com] Sent: 26 September, 2016 16:06 To: Francisco Javier Calzado Cc: gdal-dev@lists.osgeo.org Subject: Re: [gdal-dev] Multithread dead

[gdal-dev] Multithread deadlock

Hi guys, I am experiencing a deadlock with just 2 threads in a single reader & multiple writer scenario. This is, threads read from the same input file (using different handlers) and then write different output files. Deadlock comes when the block cache gets filled. The situation is the followi

Re: [gdal-dev] Multithreading issue on pixel-based intensive access (GDAL 2.1.0)

Thank you so much Even, it is working now! I will check the link and send my driver code soon. Javier. -Original Message- From: Even Rouault [mailto:even.roua...@spatialys.com] Sent: 30 July, 2016 17:10 To: Francisco Javier Calzado Cc: gdal-dev@lists.osgeo.org Subject: Re: [gdal-dev

Re: [gdal-dev] Multithreading issue on pixel-based intensive access (GDAL 2.1.0)

nd the driver attached (Wizard_Driver.7z). By the way, what do we have to do to contribute with this new driver for GDAL? Thank you so much Even. Javier. -Original Message- From: Even Rouault [mailto:even.roua...@spatialys.com] Sent: 28 July, 2016 17:42 To: Francisco Javier Calzado

Re: [gdal-dev] Multithreading issue on pixel-based intensive access (GDAL 2.1.0)

Thanks Even, I don't want to waste your time, so just before sending any code to be tested I would like to be sure it is not a bug from my side. Although I usually work with GDAL compiled in 64bits, I had to swap to x86 for these tests. When trying to compile in 32bits with Visual Studio 2015 I

[gdal-dev] Multithreading issue on pixel-based intensive access (GDAL 2.1.0)

Hi guys, I'm experiencing an issue when running some simple tests involving multithreading. I would like to know if it is something I am not doing correctly with GDAL or it is a GDAL business dealing with threads and block cache. To make long story short, just imagine two threads accessing dif

Re: [gdal-dev] New driver implementation with larger block size

Thanks for your answer Even, I knew about GDAL_ONE_BIG_READ, but given that our tool will access several raster simultaneously and will perform intensive operations with them, I like the idea of allowing GDAL caching blocks, as long as cache hits rate is high, this will increase performance I g

[gdal-dev] New driver implementation with larger block size

Hi guys, First of all, congratulations for such a wonderful and useful library. My team and I are modernising a huge software legacy tool with an important GIS background. We decided to go with GDAL some time ago and we would like to get the most out of it. I have just finished implementing a