Mark Shannon <m...@hotpy.org> added the comment:
It's not an UNPACK_SEQUENCE slowdown, it's a silly benchmark ;) https://github.com/python/pyperformance/blob/main/pyperformance/data-files/benchmarks/bm_unpack_sequence/run_benchmark.py#L6 What I *think* is happening is that the inline cache takes the size of the function (in code units) from about 4800 to about 5200, crossing our threshold for quickening (currently set to 5000). When we quicken in-place, there will be no need for a threshold and this issue will disappear. We should probably up the threshold for now, just to keep the charts looking good. ---------- _______________________________________ Python tracker <rep...@bugs.python.org> <https://bugs.python.org/issue46841> _______________________________________ _______________________________________________ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
