Message277190
George's initial patch that naively checks for signals on every iteration could be used to get an upper bound on the likely benchmark impact.
I do think this is a case where we'll want a dedicated microbenchmark to complement the macrobenchmark suite, though - Raymond's right that these functions are frequently used to optimise sections of code that have already been identified as performance bottlenecks in a particular application, so we need to be really careful with changes that might make them slower (even if the current macrobenchmarks say things are still broadly OK). |
|
Date |
User |
Action |
Args |
2016-09-22 05:14:47 | ncoghlan | set | recipients:
+ ncoghlan, rhettinger, terry.reedy, vstinner, steven.daprano, wim.glenn, gslavin |
2016-09-22 05:14:46 | ncoghlan | set | messageid: <1474521286.94.0.165090532993.issue26351@psf.upfronthosting.co.za> |
2016-09-22 05:14:46 | ncoghlan | link | issue26351 messages |
2016-09-22 05:14:46 | ncoghlan | create | |
|