This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author erlendaasland
Recipients erlendaasland
Date 2022-02-04.10:38:53
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1643971133.68.0.0138168910429.issue46634@roundup.psfhosted.org>
In-reply-to
Content
`pysqlite_connection_execute_impl()` and friends (executemany, executescript) goes all the way through the Call API just to call `pysqlite_connection_cursor_impl`. We can same a lot of calls by calling the cursor _impl function directly; after all, it does live in the same file scope as the callers.

A quick bench (sqlitesynth) shows a small speedup:

    Mean +- std dev: [main] 9.55 us +- 0.25 us -> [patched] 9.32 us +- 0.23 us: 1.02x faster



(Side effect: will get rid of _Py_IDENTIFIER(cursor) in sqlite3)
History
Date User Action Args
2022-02-04 10:38:53erlendaaslandsetrecipients: + erlendaasland
2022-02-04 10:38:53erlendaaslandsetmessageid: <1643971133.68.0.0138168910429.issue46634@roundup.psfhosted.org>
2022-02-04 10:38:53erlendaaslandlinkissue46634 messages
2022-02-04 10:38:53erlendaaslandcreate