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

Performance Regression in multithreading #15871

Closed
ranjanan opened this issue Apr 14, 2016 · 5 comments
Closed

Performance Regression in multithreading #15871

ranjanan opened this issue Apr 14, 2016 · 5 comments
Labels
domain:multithreading Base.Threads and related functionality kind:regression Regression in behavior compared to a previous version performance Must go faster

Comments

@ranjanan
Copy link
Contributor

I ran my Logistic Regression benchmark for threads. Not sure if this is related to earlier issues or not, but I thought I'd post an issue anyway.
Usually the output would be (on a version of master sometime in January)

Warm up run : 25 iterations!
Time taken by serial implementation = 1.508228316
Time taken by parallel implementation = 0.429550363
Speedup over 4 threads : 3.5111792374390336

Now, with the current threaded build of master, it's this:

Warm up run : 25 iterations!
Time taken by serial implementation = 1.831504341
Time taken by parallel implementation = 42.974081761
Speedup over 4 threads : 0.04261881268774738
@ViralBShah ViralBShah added domain:multithreading Base.Threads and related functionality performance Must go faster labels Apr 14, 2016
@ivarne ivarne added the kind:regression Regression in behavior compared to a previous version label Apr 14, 2016
@andreasnoack
Copy link
Member

I think this is mainly because of #15276 but it might be useful to keep a separate issue to track the consequences for threading.

@JeffBezanson
Copy link
Sponsor Member

This particular case is fixed on master. If it comes up again, the workaround is to declare types on variables used both inside and outside the @threads loop.

@ViralBShah
Copy link
Member

@ranjanan Can you verify?

@ranjanan
Copy link
Contributor Author

ranjanan commented Jul 8, 2016

Yes, this seems like it's fixed.

@elanmart
Copy link

Hi, running the logreg benchmark from above on 8 threads I'm getting a speedup of only 1.5 on the current master. Could this be a new issue or just a duplicate of #17395?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
domain:multithreading Base.Threads and related functionality kind:regression Regression in behavior compared to a previous version performance Must go faster
Projects
None yet
Development

No branches or pull requests

6 participants