> Is it worth collecting all these different platform specific tweaks > into a single file? I don't think so. Tuning malloc is only possible if you know the access pattern, and if you can experiment. E.g. in an MT application, those parameter may need completely different values from the ones in a single-threaded application. Or, an application allocating many strings might have different requirements than an application allocating many numbers (which are fixed-size). These parameters are offered to applications, to quiet the application developers that have been asking for them all these years, without knowing what they'd get when they can tune the parameters. If you don't know the application (such as when implementing a Python interpreter), they are useless. As will all computational-complexity problems: You can change the constants. You cannot change the complexity class of an algorithm with tuning. 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