Charles-François Natali added the comment: > Apart from creating, unlinking and resizing the file I don't think there > should be any disk I/O. > > On Linux disk I/O only occurs when fsync() or close() are called.
What? Writeback occurs depending on the memory pressure, percentage of used pages, page modification time, etc. Try writing a large file without closing it, you'll see that there's disk activity (or use iostat/vmstat). > FreeBSD has a MAP_NOSYNC flag which gives Linux behaviour (otherwise > dirty pages are flushed every 30-60). It's the same on Linux, depending on your mount options, data will be committed to disk every 5 seconds or so, when the journal is committed. > Once the file has been unlink()ed then any sensible operating system > should realize it does not need to sync the file. Why? Even if you delete the file right after open, if you write data to it, when the amount of data written fills your caches, the data has to go somewhere, even if only to make it available to the current process upon read()... ---------- _______________________________________ Python tracker <rep...@bugs.python.org> <http://bugs.python.org/issue17560> _______________________________________ _______________________________________________ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
