>>>>> "MvL" == Martin v Loewis <martin@loewis.home.cs.tu-berlin.de> writes: MvL> to the existing approach. The main point of this patch is to MvL> improve efficiency, and (according to Jeremy's analysis), most MvL> of the time for calling a function is spend in MvL> PyArg_ParseTuple. I'd like to qualify this a bit. What I reported earlier is that the BuiltinFuntionCall microbenchmark in pybench spends 30% of its time in PyArg_ParseTuple(). This strikes me as excessive, because it's a static property of the code. (One could imagine writing a Python script that parsed the "O!|is#" format strings and generated efficient, specialized C code for that format.) If we benchmark other programs, particularly those that do more work in the builtins, the relative cost of the argument processing will be lower. Jeremy
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