perf(python): read union case fields directly instead of rebuilding Array#4725
Open
MangelMaxime wants to merge 1 commit into
Open
perf(python): read union case fields directly instead of rebuilding Array#4725MangelMaxime wants to merge 1 commit into
MangelMaxime wants to merge 1 commit into
Conversation
Contributor
Python Type Checking Results (Pyright)
Excluded files with errors (4 files)These files have known type errors and are excluded from CI. Remove from
|
5a140d9 to
ec38a85
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
When working on Scriptorium, I discovered that Python generated code is slower than JS for union-heavy workloads.
One of the main reasons is that union case field reads (
x.fields[i], emitted for every pattern match) went throughUnion.fields, a@propertythat rebuilds a fullArrayfromgetattr()calls on every access. Even if JavaScript does a similar thing, in that case it storesfieldsonce at construction, while Python rebuilds it every time.In my codebase, it resulted in
union.fieldsbeing called (~8M calls) when profiling.Amounting to ~5sec of the run time.
Before:
After:
The drawback I found from this change is that we now need to cast the union to the case class type before reading its fields. Otherwise, Pyright will complain that the "field property" (ex
left_,item1, etc. ) is not defined on the union type.Benchmark
I made a small benchmark to test the performance difference between the two approaches using something like the following code:
Results: