[Python-Dev] Per opcode cache for LOAD_GLOBAL (original) (raw)
Brett Cannon brett at python.org
Wed May 29 12:45:33 EDT 2019
- Previous message (by thread): [Python-Dev] Per opcode cache for LOAD_GLOBAL
- Next message (by thread): [Python-Dev] Should I postpone PEP 558 (locals() semantics) to Python 3.9?
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
On Wed, May 29, 2019 at 6:21 AM Inada Naoki <songofacandy at gmail.com> wrote:
Hi, all.
Yury implemented per opcode cache for LOADGLOBAL, LOADATTR, and LOADMETHOD. [1] I update the patch for current master branch, but only for LOADGLOBAL for now. [2] It sped up LOADGLOBAL about 40%. [3] It is attractive optimization. Now 3.8b1 will be coming soon, but the pull request is not reviewed well yet. For example, should we add some switch to disable the cache?
Why would we want disable it?
May I merge it before beta1 and polish (or revert) it by rc1?
I think that's an RM call.
Or should I postpone it for 3.9?
That's obviously the simplest. :)
-Brett
Regards, [1]: https://bugs.python.org/issue26219 [2]: https://github.com/python/cpython/pull/12884 [3]: https://github.com/methane/sandbox/tree/master/2019/opcacheloadglobal#opcache-for-loadglobal -- Inada Naoki <songofacandy at gmail.com>
Python-Dev mailing list Python-Dev at python.org https://mail.python.org/mailman/listinfo/python-dev Unsubscribe: https://mail.python.org/mailman/options/python-dev/brett%40python.org -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://mail.python.org/pipermail/python-dev/attachments/20190529/0c4a7aac/attachment.html>
- Previous message (by thread): [Python-Dev] Per opcode cache for LOAD_GLOBAL
- Next message (by thread): [Python-Dev] Should I postpone PEP 558 (locals() semantics) to Python 3.9?
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]