FYI, a good illustration of why tuning malloc per-platform is a bottomless
pit.
-----Original Message-----
From: python-list-admin@python.org
On Behalf Of Alexei Zverovitch <none@nowhere.invalid?
Sent: Tuesday, November 06, 2001 6:00 AM
To: python-list@python.org
Subject: Re: Program very slow to finish
Fred <fredNo@nospamco.com> wrote in news:3BE41CBE.94AED22@nospamco.com:
> Python 2.1.1 (#3, Oct 25 2001, 12:54:40) [C] on osf1V4
Since you're running Digital Unix, you might want to
try tweaking the __fast_free_max et al variables used
by the system malloc(). 'man malloc' is your friend
(I believe you'll need to re-link the python executable
if you want to change those variables).
We've had a similar problem recently when a (C++)
program was taking ages to free() .5 million small
structures. It turned out that most of the time was
spent by free() coalescing memory blocks as they
were being deallocated. Increasing __fast_free_max
solved the problem (IIRC the execution time was
reduced by several orders of magnitude).
You may be seeing the same (or similar) behaviour.
Cheers
Alexei
--
alexei (at) barclays (dot) net
--
http://mail.python.org/mailman/listinfo/python-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