This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author jcea
Recipients jcea, neologix
Date 2013-08-23.13:53:06
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1377265986.52.0.577159900734.issue18816@psf.upfronthosting.co.za>
In-reply-to
Content
Depending of a concrete OS implementation is not good. Linux is not the only OS out there, and I have very old machines in production yet:

"""
# uname -a
Linux colquide.XXXX.es 2.4.37 #4 Fri Dec 12 01:10:45 CET 2008 i686 unknown
"""

I have been hit by the VM/file cache split in the past. Portability is important.

Anyway, the Python "mmap" manual says that "mmap.flush()" is needed to be sure that you are not going to "lose" changes you made in the mmap. On "modern" OSs it is not actually needed, as you say, and the performance hit is important enough for me to investigate and write this enhancement proposal :).
History
Date User Action Args
2013-08-23 13:53:06jceasetrecipients: + jcea, neologix
2013-08-23 13:53:06jceasetmessageid: <1377265986.52.0.577159900734.issue18816@psf.upfronthosting.co.za>
2013-08-23 13:53:06jcealinkissue18816 messages
2013-08-23 13:53:06jceacreate