-
-
Notifications
You must be signed in to change notification settings - Fork 5.5k
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
Regression in methodshow/print_to_string #11700
Comments
Isn't this function only used interactively? And isn't the difference less than a human can perceive? |
Yes, but I do not think the root cause is inside the methodshow but in the string conversion. I have not been able to track the exact difference down. |
Maybe you can test the commit before and see if it is fast again then? Or alternative just do a full fledged bisection. |
I have tried to track this further. The following goes from 14.7s to 20.6s post #10380
|
My best guess is that this is caused by the call to jl_f_tuple used to allocate varargs tuples ( Line 4613 in 99391b3
Another possibility is that the optimization to elide varargs tuples has regressed in some cases. |
Now an additional ~5x slower, with all the time in |
I'm on a phone so I can't measure it, but Jeff already fixed at least some of it: c2d35bb (thanks Jeff!) |
0.3.12 runs #11700 (comment) at 10 seconds, master at 11.5 seconds. Seems close enough to close. |
I have observed a regression of a factor of 2-3 between master and 0.3.8 in the following test case:
0.3.8 runs in
2.467998002 s
while master takes7.016 s
.The text was updated successfully, but these errors were encountered: