On Thu, Sep 21, 2023, at 18:05, Even Rouault wrote:
>
>> Of course, but I'm asking if it's worth calling ReadBlock on multiple
>> threads (if it always takes a lock, it's not, and I should use RasterIO
>> instead).
> Not on the same dataset object, otherwise you'll get crashes as no lock is
>
Of course, but I'm asking if it's worth calling ReadBlock on multiple
threads (if it always takes a lock, it's not, and I should use
RasterIO instead).
Not on the same dataset object, otherwise you'll get crashes as no lock
is taken
(*) I think these can also be implemented at VSI level by w
Hi,
On Thu, Sep 21, 2023, at 17:02, Even Rouault wrote:
> Laurentiu,
>
>>
>> GDAL 3.6 added support for multi-threaded reading using PRead, but I
>> couldn't spot ReadBlock using the same code path.
> If you read one single block at a time, the multi-threaded optimization
> cannot kick in, sin
Laurentiu,
GDAL 3.6 added support for multi-threaded reading using PRead, but I
couldn't spot ReadBlock using the same code path.
If you read one single block at a time, the multi-threaded optimization
cannot kick in, since the elementary decoding unit is a block. You must
call RasterIO()
Hello,
GDAL 3.6 added support for multi-threaded reading using PRead, but I couldn't
spot ReadBlock using the same code path. On the other hand, I didn't see it
taking a lock either, so I'm a little confused :-). My question is whether
ReadBlock supports concurrent reads or not (*).
(*) I thin
