Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

perf: Optimization to resolve uris #5657

Merged
merged 2 commits into from Sep 14, 2023
Merged

Conversation

avelad
Copy link
Collaborator

@avelad avelad commented Sep 14, 2023

Chained use of maps and reduce on legacy devices reduces performance. So if there is only one url to generate we can optimize performance.

@avelad avelad added type: performance A performance issue priority: P1 Big impact or workaround impractical; resolve before feature release labels Sep 14, 2023
@avelad avelad added this to the v4.5 milestone Sep 14, 2023
.map((base) => relativeAsGoog.map((i) => base.resolve(i)))
.reduce(Functional.collapseArrays, [])
.map((uri) => uri.toString());
return baseUris.map((uri) => {
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Would it help performance to rewrite this as a loop with no functional callbacks?

Copy link
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I don't see any difference using loops

@avelad avelad merged commit bd17c2b into shaka-project:main Sep 14, 2023
15 checks passed
joeyparrish pushed a commit that referenced this pull request Sep 14, 2023
Chained use of maps and reduce on legacy devices reduces performance. So
if there is only one url to generate we can optimize performance.
joeyparrish pushed a commit that referenced this pull request Sep 14, 2023
Chained use of maps and reduce on legacy devices reduces performance. So
if there is only one url to generate we can optimize performance.
@avelad avelad deleted the perf-optimization branch September 15, 2023 06:46
@shaka-bot shaka-bot added the status: archived Archived and locked; will not be updated label Nov 13, 2023
@shaka-project shaka-project locked as resolved and limited conversation to collaborators Nov 13, 2023
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
priority: P1 Big impact or workaround impractical; resolve before feature release status: archived Archived and locked; will not be updated type: performance A performance issue
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

3 participants