Skip to content

Performance regression on travis #245

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

Closed
Byron opened this issue Jan 22, 2015 · 4 comments
Closed

Performance regression on travis #245

Byron opened this issue Jan 22, 2015 · 4 comments

Comments

@Byron
Copy link
Member

Byron commented Jan 22, 2015

Py3 runs are 3 to 6 times slower on travis, even though this doesn't show on my machine at all.
What's up with that ?

@Byron Byron added this to the v0.3.6 - Features milestone Jan 22, 2015
@Byron
Copy link
Member Author

Byron commented Jan 22, 2015

It seems that all that time is spend in rev-parse. The latter might trigger plenty of file accesses, but it's still the question why this is so much slower in py3 all of the sudden.

@Byron
Copy link
Member Author

Byron commented Jan 22, 2015

For me, this issue isn't reproducible, neither on OSX (native), nor on an ubuntu64 VM. This is the VM's result:

screen shot 2015-01-22 at 17 53 18

Byron added a commit that referenced this issue Jan 22, 2015
Hoping to make this significantly faster on travis.

Related to #245
@Byron
Copy link
Member Author

Byron commented Jan 22, 2015

Performance regression is still visible on travis, even though said rev-parse test was nerfed to the point where we save 2 or 3 minutes at least. However, there must be more slow tests that need to be handled somehow.

@Byron Byron modified the milestones: v0.3.8 - Fixes, v0.3.7 - Fixes Apr 8, 2015
@Byron Byron modified the milestones: v1.0.1 - Fixes, v1.0.2 - Fixes Apr 22, 2015
@Byron
Copy link
Member Author

Byron commented Jun 10, 2015

This seems to be gone !

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Development

No branches or pull requests

1 participant