Message134380
| Author |
neologix |
| Recipients |
flox, kaifeng, neologix, pitrou |
| Date |
2011年04月25日.12:36:04 |
| SpamBayes Score |
6.2050547e-09 |
| Marked as misclassified |
No |
| Message-id |
<BANLkTimFzWwMwtDtmY3TnMj=w=_B6i83SQ@mail.gmail.com> |
| In-reply-to |
<1303718493.1.0.475643832984.issue11849@psf.upfronthosting.co.za> |
| Content |
> The MALLOC_MMAP_THRESHOLD improvement is less visible here:
>
Are you running on 64-bit ?
If yes, it could be that you're exhausting M_MMAP_MAX (malloc falls
back to brk when there are too many mmap mappings).
You could try with
MALLOC_MMAP_THRESHOLD_=1024 MALLOC_MMAP_MAX_=16777216 ../opt/python
issue11849_test.py
By the way, never do that in real life, it's a CPU and memory hog ;-)
I think the root cause is that glibc's malloc coalescing of free
chunks is called far less often than in the original ptmalloc version,
but I still have to dig some more.
>> By the way, I noticed that dictionnaries are never allocated through
>> pymalloc, since a new dictionnary takes more than 256B...
>
> On 64-bit builds indeed. pymalloc could be improved to handle allocations up
> to 512B. Want to try and write a patch?
Sure.
I'll open another issue. |
|