[Python-Dev] Arena-freeing obmalloc ready for testing
Nick Craig-Wood
nick at craig-wood.com
Thu Mar 2 15:54:38 CET 2006
More information about the Python-Dev mailing list
Thu Mar 2 15:54:38 CET 2006
- Previous message: [Python-Dev] Arena-freeing obmalloc ready for testing
- Next message: [Python-Dev] Arena-freeing obmalloc ready for testing
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
On Thu, Mar 02, 2006 at 01:43:00AM -0600, Tim Peters wrote: > I'm optimistic, because the new test compares a quantity already being > tested by the macro, a second time against 0, and it's hard to get > cheaper than that. However, the new branch isn't predictable, so who > knows? When compiling with gcc at least you could give the compiler a hint, eg http://kerneltrap.org/node/4705 > For example, in a release build on WinXP, VM size is about 48MB at the > "full" prompt, and drops to 3MB at the "empty" prompt. In the trunk > (without this patch), VM size falls relatively little from what it is > at the "full" prompt Excellent work! -- Nick Craig-Wood <nick at craig-wood.com> -- http://www.craig-wood.com/nick
- Previous message: [Python-Dev] Arena-freeing obmalloc ready for testing
- Next message: [Python-Dev] Arena-freeing obmalloc ready for testing
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
More information about the Python-Dev mailing list