You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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:
assignee='https://github.com/markshannon'closed_at=<Date2021-06-09.17:21:18.301>created_at=<Date2021-05-20.11:15:19.660>labels= ['3.11', 'performance']
title='Implement infrastructure for quickening and specializing'updated_at=<Date2021-06-09.17:21:18.300>user='https://github.com/markshannon'
As described in PEP-659 (Specializing Adaptive Interpreter) the first part of implementing specialization is to implement the machinery to do the quickening.
Conceptually, this is fairly simple: add a new field to the code object, which points to the first instruction in the bytecode.
When quickening, we create a new array, copy the old bytecode into it, and make the new field point to it.
Without any specialization or superinstructions, this will just waste memory.
However, it will pay off soon enough as we implement superinstructions, remove the old "opcache" and add new specializations.
We expect to see worthwhile speed ups with just superinstructions, and large speedups when all the above features have been implemented.
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:
The text was updated successfully, but these errors were encountered: