Issue 28006: Remove tracing overhead from the fine-grained fast opcodes (original) (raw)

Issue28006

Created on 2016-09-07 18:54 by rhettinger, last changed 2022-04-11 14:58 by admin. This issue is now closed.

Files
File name Uploaded Description Edit
trace.diff rhettinger,2016-09-07 18:54 Reduce overhead in the review
Messages (3)
msg274867 - (view) Author: Raymond Hettinger (rhettinger) * (Python committer) Date: 2016-09-07 18:54
The fast opcodes are ones where we bypass signal/event checking, but they still have the overhead of checking for tracing enabled (this doesn't seem like much, it adds a memory access and can take almost half the time for some of these already quick opcodes). I haven't seen an effect on the upstream line level tracing but this needs a second look to be sure there isn't an unanticipated consequence.
msg274896 - (view) Author: Raymond Hettinger (rhettinger) * (Python committer) Date: 2016-09-07 21:15
Working on a revised patch. Stand by.
msg274898 - (view) Author: Raymond Hettinger (rhettinger) * (Python committer) Date: 2016-09-07 21:39
I'm going to withdraw this one. I'm not familiar enough with this part of the code to reliably make changes to it.
History
Date User Action Args
2022-04-11 14:58:36 admin set github: 72193
2016-09-07 21:39:31 rhettinger set status: open -> closedmessages: +
2016-09-07 21:15:23 rhettinger set assignee: steve.dower -> rhettingermessages: +
2016-09-07 20:58:48 rhettinger set nosy: + benjamin.peterson
2016-09-07 19:14:38 serhiy.storchaka set nosy: + serhiy.storchaka
2016-09-07 18:55:07 vstinner set nosy: + vstinner
2016-09-07 18:54:52 rhettinger create