Repository navigation
Faster positional arguments parsing in PyArg_ParseTupleAndKeywords #73215
Description
Activity
Proposed patch speeds up parsing positional arguments in PyArg_ParseTupleAndKeywords().
$ ./python -m perf timeit "1 .to_bytes(1, 'little', signed=False)" Unpatched: Median +- std dev: 2.01 us +- 0.09 us Patched: Median +- std dev: 1.23 us +- 0.03 usCurrently names of all passed positional argument are looked up in the kwargs dictionary for checking if the argument is passed as positional and keyword argument. With the patch this is checked only if there are unhandled keyword arguments after parsing keyword arguments that don't passed as positional arguments.
The same optimization also is applied to _PyArg_ParseTupleAndKeywordsFast() and like, but the effect is much smaller.
The patch also includes tiny refactoring.
- added3.7 (EOL)end of lifeend of lifeinterpreter-core(Objects, Python, Grammar, and Parser dirs)(Objects, Python, Grammar, and Parser dirs)performancePerformance or resource usagePerformance or resource usage
on Dec 20, 2016 LGTM
New changeset a36e60c5fee0 by Victor Stinner in branch 'default':
Rename keywords to kwargs in getargs.c
https://hg.python.org/cpython/rev/a36e60c5fee0Oh, I missed this issue. Since I made minor cleanup recently, I took the liberty of rebasing your patch.
I also pushed your "keywords => kwargs" change, just to make the patch simpler to review.
Unpatched: Median +- std dev: 2.01 us +- 0.09 us
Patched: Median +- std dev: 1.23 us +- 0.03 usOh wow, impressive speedup! As usual, good job Serhiy ;-)
PyArg_ParseTupleAndKeywords-faster-positional-args-parse-2.patch: LGTM! Can you please push it?
LGTM again.
New changeset a8563ef0eb8a by Serhiy Storchaka in branch 'default':
Issue bpo-29029: Speed up processing positional arguments in
https://hg.python.org/cpython/rev/a8563ef0eb8aThank you for your reviews Inada and Victor. Thank you for rebasing the patch Victor.
I were going first to try an alternative patch, maybe less efficient, but allowing to share more code. But since the code is changed so fast, it is better to commit the ready patch.
Note: these values reflect the state of the issue at the time it was migrated and might not reflect the current state.
Show more details
GitHub fields:
bugs.python.org fields: