| FazBrowse GitHub Viewer | Trending | | Home |
| Tools: [Download Repo ZIP] [Original HTTPS Page] |
Sorry, something went wrong.
This makes Windows about 3% faster on pyperformance benchmarks.
There was a problem hiding this comment.
Nice, looks very straightforward.
Though based on our offline conversation, did you find out whether Windows PGO uses -E?
Sorry, something went wrong.
| uint8_t opcode; /* Current opcode */ | ||
| int oparg; /* Current opcode argument, if any */ |
There was a problem hiding this comment.
Heh, I would have kept the comments at the same column, so you don't appear to be editing the oparg line. :-)
Sorry, something went wrong.
There was a problem hiding this comment.
Sure -- I think my editor did something magical.
Sorry, something went wrong.
I don't know, but I think that's orthogonal to this. Currently on the benchmarking infrastructure, we only pass the PYTHON_UOPS env variable to pyperformance, so it definitely has no effect during build. Independently of this, I measured what happens when you force Tier 2 on during the build, and it is about 1% faster. |
Sorry, something went wrong.
Ah, sorry. Should I merge this then?
1% faster than without Tier 2, or 1% faster than main? |
Sorry, something went wrong.
Yeah, I think that's fine.
When you turn Tier 2 on during build (PGO collection), it's 1% faster than if you don't. (Using Tier 2 at runtime in both cases). |
Sorry, something went wrong.
That's great news! |
Sorry, something went wrong.
…on#112289) This makes Windows about 3% faster on pyperformance benchmarks.
…on#112289) This makes Windows about 3% faster on pyperformance benchmarks.
| Back | FazBrowse Home | New Git URL |
Suggested by @neonene: #111786 (comment)
This makes Windows about 3% faster on pyperformance benchmarks. See analysis here