[issue45330] dulwich_log performance regression in 3.10

Ken Jin added the comment: Considering both Inada-san and I can't repro this on Linux and Windows respectively, I'm closing this and blaming code placement or some magic. Thanks everyone. -- resolution: -> rejected stage: -> resolved status: open -> closed

[issue45330] dulwich_log performance regression in 3.10

Inada Naoki added the comment: I can not confirm performance regression between 33ec88ac and 23ae2c3b. ``` Performance version: 1.0.2 Python version: 3.10.0a7+ (64-bit) revision 33ec88ac81 Report on Linux-5.4.0-81-generic-x86_64-with-glibc2.31 Number of logical CPUs: 8 Start date: 2021-10-06

[issue45330] dulwich_log performance regression in 3.10

Pablo Galindo Salgado added the comment: We use a pinned version of pyperformance so the code has not changed. I need to manually bump the version and when they happens I wipe all previous benchmarks -- nosy: +pablogsal -vstinner title: speed.python.org: dulwich_log performance

[issue45330] dulwich_log performance regression in 3.10

Ken Jin added the comment: Ooh thanks Irit, I hadn't considered that. I thought that versions were fixed, but it seems that we *do* change the 3rd party package versions once in a while. In that time period, we bumped dulwich from 0.20.20 to 0.20.21

[issue45330] dulwich_log performance regression in 3.10

Irit Katriel added the comment: Looks like this is using a 3rd party module (dulwitch.repo). Could it be a new version of that? -- ___ Python tracker ___

[issue45330] dulwich_log performance regression in 3.10

Change by Brandt Bucher : -- nosy: +brandtbucher ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe:

[issue45330] dulwich_log performance regression in 3.10

New submission from Ken Jin : Somewhere between May02-May11, dulwich_log benchmark on pyperformance had a major performance regression on the 3.10 branch. https://speed.python.org/timeline/?exe=12==dulwich_log=1=200=off=on=on For a start, we could git bisect with pyperformance. FWIW, I