On 19 June 2018 at 11:50, Alex HighViz <[email protected]> wrote: > On 19/06/2018 10:28, Mateusz Loskot wrote: >> On 19 June 2018 at 11:22, Alex HighViz <[email protected]> wrote: >>> Regrettably I overstated the performance in my previous post, due to a bug >>> that is now solved. With the solved bug, Pronto is about 50% slower than >>> GDAL directly. I believe this is still good considering the benefits, but >>> not as glamorous as I first thought. I have also applied it on a set of >>> 100000 x 1000 rasters and the results are consistent. >>> >>> The related post has been updated (and I still consider it "promising"): >>> https://github.com/ahhz/raster/blob/master/docs/_posts/2018-06-14-Preliminary-benchmark-results-are-promising.md >> I might have missed that, but there seem to be no information about used >> - compiler(s) and their versions >> - compilation flags >> >> Best regards, > > No you're right, that information is missing. I was using Visual Studio 15.2 > > /GS /GL /analyze- /W3 /Gy /Zc:wchar_t /Zi /Gm- /O2 /sdl > /Fd"Release\vc141.pdb" /Zc:inline /fp:precise /D "_MBCS" > /errorReport:prompt /WX- /Zc:forScope /Gd /Oy- /Oi /MD /std:c++latest > /Fa"Release\" /EHsc /nologo /Fo"Release\" /Fp"Release\raster.pch" > /diagnostics:classic
Looks OK, close to or same as the defaults for VS optimised builds. I was wondering if the slow performance may be due to the standard iterators debugging enabled. Best regards, -- Mateusz Loskot, http://mateusz.loskot.net _______________________________________________ gdal-dev mailing list [email protected] https://lists.osgeo.org/mailman/listinfo/gdal-dev
