Repository navigation
Performance regression on travis #245
Description
Activity
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.
For me, this issue isn't reproducible, neither on OSX (native), nor on an ubuntu64 VM. This is the VM's result:
- added a commit that references this issue
on 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.
This seems to be gone !
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 ?