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

Two other instances where a set subtraction operation would be faster as a filter #452

Merged
merged 1 commit into from
May 8, 2015

Conversation

lfkellogg
Copy link
Contributor

Of all the other uses of the set subtraction operator, these are two where the set being subtracted is generally larger. Both of these improve benchmark run times, especially the FactoredAlgorithm case.

@bruttenberg
Copy link
Collaborator

This looks good, and as long as you ran the factored tests and they pass I'm fine. But where are you getting these performance benchmarks?

mreposa added a commit that referenced this pull request May 8, 2015
Two other instances where a set subtraction operation would be faster as a filter
@mreposa mreposa merged commit da8beb5 into charles-river-analytics:DEV3.2.0 May 8, 2015
@lfkellogg
Copy link
Contributor Author

Good question! I'm using ScalaMeter benchmark tests, which I haven't been including in these commits. Mike mentioned that you and Glenn had been thinking about how to do performance/speed tests outside of your unit testing framework. ScalaMeter is an option but I didn't want to just start checking them in because they'd be automatically run as part of the existing sbt Test suite, which is probably not what we want. We should discuss at some point.

@lfkellogg lfkellogg deleted the set_operations branch May 8, 2015 17:50
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