> It is likely that PyMalloc would be better with a way to disable the > free()ing of empty arenas, or move to an arrangement where (like the > various type free-lists in 2.6+) explicit action can force pruning of > empty arenas - there are other usage patterns than yours which would > benefit (performance wise) from not freeing arenas automatically. Before such a mechanism is added, I'd like to establish for a fact that this is an actual problem. Regards, Martin
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