You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
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.
Activity
Byron commentedon 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 commentedon 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:
Improved performance of rev-parse test.
Byron commentedon 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 commentedon Jun 10, 2015
This seems to be gone !