RetroSearch Browse

Mon Dec 22 22:11:56 CET 2008 · https://mail.python.org/pipermail/python-dev/2008-December/084537.html

>> If that code is the real problem (in a reproducible test case),
>> then this approach is the only acceptable solution. Disabling
>> long-running code is not acceptable.
> 
> By "disabling", I meant disabling the optimization that's trying to
> rearrange the arenas so that more memory can be returned to the OS.

I meant the same thing - I'm opposed to giving up one feature or
optimization in favor of a different feature or optimization.

> This presumably wouldn't be any worse than things were in Python 2.4,
> when memory was never returned to the OS.

Going back to the state of Python 2.4 would not be acceptable.

Regards,
Martin

Home - News ( United States | United Kingdom | Italy | Germany ) - Football scores

Showing content from https://mail.python.org/pipermail/python-dev/2008-December/084537.html below:

[Python-Dev] extremely slow exit for program having huge (45G) dict (python 2.5.2)