Antoine Pitrou added the comment:
The original changeset in Richard's repository is
https://hg.python.org/sandbox/sbt/rev/6c8554a7d068. Unless Richard answers
otherwise, I think it's likely the performance degradation was an oversight.
Given the code we're talking about is POSIX-specific, truncate() (or its
sibling os.ftruncate()) is specified to always zero-fill. So it should be safe
to use.
Another related point is that the arena file is created inside get_temp_dir(),
which allocates something in /tmp. On modern Linux systems at least, /tmp is
usually backed by persistent storage. Instead, we could use
/run/user/{os.getuid()}, which uses a tmpfs and would therefore save on I/O
when later accessing the shared array.
----------
nosy: +pitrou
stage: -> needs patch
versions: +Python 3.7 -Python 2.7, Python 3.5, Python 3.6
_______________________________________
Python tracker <rep...@bugs.python.org>
<http://bugs.python.org/issue30919>
_______________________________________
_______________________________________________
Python-bugs-list mailing list
Unsubscribe:
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
