nick at craig-wood.com
Mon Jan 22 10:30:09 CET 2007
George Sakkis <george.sakkis at gmail.com> wrote:
> The file is written once and then opened as read-only, there's no
> flushing. So if caching is completely up to the OS, I take it that my
> options are either (1) modify my algorithms so that they work in
> fixed-size batches instead of arbitrarily long sequences or (2)
> implement my own memory-mapping scheme to fit my algorithms. I guess
> (1) would be the less trouble overall, or is there a way to give a hint
> to the OS on how large cache can it use ?
The above behaviour isn't as expected. So either there is something
going on in your program that we don't know about or there is a bug
somewhere, either in the OS or in python.
Can you make a short program to replicate the problem? That will help
narrow down the problem.
Nick Craig-Wood <nick at craig-wood.com> -- http://www.craig-wood.com/nick
More information about the Python-list