FYI, I had to visit those parameters for my PS3 port and cut down on the bombastic memory footprint of 2.7 dicts. Some the supposedly tunable parameters aren´t tunable at all. See http://blog.ccpgames.com/kristjan/2012/04/25/optimizing-the-dict/ Speed and memory are most often conflicting requirements. I would like to two or more compile time settings to choose from: Memory optimal, speed optimal, (and mix). Cheers, K > -----Original Message----- > From: python-dev-bounces+kristjan=ccpgames.com at python.org > [mailto:python-dev-bounces+kristjan=ccpgames.com at python.org] On > Behalf Of Mark Shannon > Sent: 13. júní 2012 21:37 > To: python-dev at python.org > Subject: [Python-Dev] Tunable parameters in dictobject.c (was dictnotes.txt > out of date?) > > Raymond Hettinger wrote: > > > > On Jun 13, 2012, at 10:35 AM, Eli Bendersky wrote: > > > >> Did you mean to send this to the list, Raymond? > > > > > > Yes. I wanted to find-out whether someone approved changing > > all the dict tunable parameters. I thought those weren't supposed > > to have changed. PEP 412 notes that the existing parameters were > > finely tuned and it did not make recommendations for changing them. > > The PEP says that the current (3.2) implementation is finely tuned. > No mention is made of tunable parameters. > > > > > At one point, I spent a full month testing all of the tunable > > parameters using dozens of popular Python applications. The values > > used in Py3.2 represent the best settings for most apps. > > Best in terms of speed, but what about memory use? >
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