A RetroSearch Logo

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

Search Query:

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

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

[Python-Dev] extremely slow exit for program having huge (45G) dict (python 2.5.2) [Python-Dev] extremely slow exit for program having huge (45G) dict (python 2.5.2)Mike Coleman tutufan at gmail.com
Mon Dec 22 21:43:33 CET 2008
On Mon, Dec 22, 2008 at 2:38 PM, "Martin v. Löwis" <martin at v.loewis.de> wrote:
>> Or perhaps there's a smarter way to manage the list of
>> arena/free pool info.
>
> 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.
This presumably wouldn't be any worse than things were in Python 2.4,
when memory was never returned to the OS.

(I'm working on a test case.)
More information about the Python-Dev mailing list

RetroSearch is an open source project built by @garambo | Open a GitHub Issue

Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo

HTML: 3.2 | Encoding: UTF-8 | Version: 0.7.4