Skip to content

Optimize some computation-intensive code #9721

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

Merged
merged 5 commits into from
Sep 5, 2020

Conversation

odersky
Copy link
Contributor

@odersky odersky commented Sep 4, 2020

No description provided.

 - Avoid recursions deeper than 10
 - Avoid copying tail after last dropped element
replace filter by filterConserve if

 - the call is warm (called for more than 10% of source lines)
 - the filter predicate has a high chance of succeeding

Avoid filter altogether if there's a faster alternative
Copy link
Member

@dottybot dottybot left a comment

Choose a reason for hiding this comment

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

Hello, and thank you for opening this PR! 🎉

All contributors have signed the CLA, thank you! ❤️

Commit Messages

We want to keep history, but for that to actually be useful we have
some rules on how to format our commit messages (relevant xkcd).

Please stick to these guidelines for commit messages:

  1. Separate subject from body with a blank line
  2. When fixing an issue, start your commit message with Fix #<ISSUE-NBR>:
  3. Limit the subject line to 72 characters
  4. Capitalize the subject line
  5. Do not end the subject line with a period
  6. Use the imperative mood in the subject line ("Add" instead of "Added")
  7. Wrap the body at 80 characters
  8. Use the body to explain what and why vs. how

adapted from https://chris.beams.io/posts/git-commit

Have an awesome day! ☀️

@odersky
Copy link
Contributor Author

odersky commented Sep 4, 2020

test performance please

@dottybot
Copy link
Member

dottybot commented Sep 4, 2020

performance test scheduled: 9 job(s) in queue, 1 running.

@dottybot
Copy link
Member

dottybot commented Sep 4, 2020

Performance test finished successfully:

Visit http://dotty-bench.epfl.ch/9721/ to see the changes.

Benchmarks is based on merging with master (1ab71c1)

@odersky
Copy link
Contributor Author

odersky commented Sep 4, 2020

test performance please

@dottybot
Copy link
Member

dottybot commented Sep 4, 2020

performance test scheduled: 8 job(s) in queue, 1 running.

@dottybot
Copy link
Member

dottybot commented Sep 4, 2020

Performance test finished successfully:

Visit http://dotty-bench.epfl.ch/9721/ to see the changes.

Benchmarks is based on merging with master (1ab71c1)

@odersky
Copy link
Contributor Author

odersky commented Sep 5, 2020

This looks like a consistent win (~6%) for stdlib, and in the noise for the others. So it looks worthwhile to merge this.

Copy link
Contributor

@liufengyun liufengyun left a comment

Choose a reason for hiding this comment

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

LGTM

@liufengyun liufengyun merged commit 8c94870 into scala:master Sep 5, 2020
@liufengyun liufengyun deleted the optimize-computations branch September 5, 2020 09:25
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants