<div dir="ltr"><div class="gmail_extra"><div class="gmail_quote">Jeff,<br><br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr">Thanks Blake for the detailed response. I did not realize that I did not do a reply all in my previous email I sent.</div>
</blockquote><div><br></div><div>Not an issue, glad you guys are interested in my changes.</div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr"><div class="gmail_extra">
<div class="gmail_quote"><div class=""><div><br></div></div><div>--> I thought that this was not possible using current trunk GDAL because of the global cache. At least the writing side using multiple threads can cause issues.</div>
<div>See this response on a older topic I found in GDAL dev list: <a href="http://lists.osgeo.org/pipermail/gdal-dev/2013-January/035215.html" target="_blank">http://lists.osgeo.org/pipermail/gdal-dev/2013-January/035215.html</a> </div>
<div>
The response there was for a similar question as the one i posted about supporting of batch translating of dataset with this <span style="font-family:arial,sans-serif;font-size:13px">RFC</span> .</div></div></div></div></blockquote>
<div><br></div><div>I do believe it is possible in the current trunk of GDAL (and I have written some code to do it with out seeing any issues). There is a "lock" on raster blocks currently that prevents them from being removed from the cache if they are currently be utilized. </div>
<div> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr"><div class="gmail_extra"><div class="gmail_quote"><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex">
<div dir="ltr"><div class="gmail_extra"><div class="gmail_quote">
</div></div></div></blockquote><div><br></div><div>--> Ok, I was under the wrong impression that in addition of a cache per dataset there is still a cap of global cache that oversee the total cache used by GDAL.</div>
</div></div></div></blockquote><div><br></div><div>This really isn't possible, because if something needs to be removed from the cache and there is nothing to remove from the current dataset, it would have to go to another dataset to lower the cache size. At this point the per dataset cache really has limited meaning, because a lot of the same issues will occur.</div>
<div><br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr"><div class="gmail_extra"><div class="gmail_quote"><div>--> Is this mean that in addition of the per dataset cache once can still use the global cache (only not per dataset one) and have the scenario of translating multiple datasets in a parallel way</div>
<div>works ok (without threading issues due to current implementation global cache).</div></div></div></div></blockquote><div><br></div><div>Yes, it will work to translate multiple datasets in a parallel way with a global cache.</div>
<div><br></div><div>Thanks,</div><div><br></div><div>Blake</div></div></div></div>