[gdal-dev] Can GDAL be configured to do direct I/O? (bypass cache, control blocksize, etc)

[Ethan Alpert]

I'm running in to a situation where I believe the filesystem cache
settings are screwing things up. Based on iozone tests I'm not getting
near the throughput I should for large 4gb+ files with multiple writing
processes. It is a complex interaction of the number of dirty pages in
filesystem cache in combination with small blocksize of the filesystem.
I'm still trying to figure this out but I can now get these machines to
tip over with just iozone. 

 

 

I'm actively working on how to refactor this code base to use GDAL
WriteBlock but in absence of a solution there I'm wondering if there's
anyway to get GDAL writing using O_DIRECT?

 

Thanks,

 

-ethan


This electronic communication and any attachments may contain confidential and proprietary 
information of DigitalGlobe, Inc. If you are not the intended recipient, or an agent or employee 
responsible for delivering this communication to the intended recipient, or if you have received 
this communication in error, please do not print, copy, retransmit, disseminate or 
otherwise use the information. Please indicate to the sender that you have received this 
communication in error, and delete the copy you received. DigitalGlobe reserves the 
right to monitor any electronic communication sent or received by its employees, agents 
or representatives.

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.osgeo.org/pipermail/gdal-dev/attachments/20121214/40130a00/attachment-0001.html>