-
Notifications
You must be signed in to change notification settings - Fork 32
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
Can we find which script or function is taking longer than 50 ms? #28
Comments
Yes, long tasks V2 will have scriptUrl. |
When will you release Long Task V2? |
We are just starting to work on this, so hopefully in a couple of milestones. |
If you release the feature within two or three weeks, it will be very helpful to me. |
Actually , i have the same question as @Vasikaran : |
We currently do not plan to expose the script URL, AFAIK. We don't have any concrete future work on how to make attribution better in general. This was deprioritized because of an effort on the sampling profiler, see https://github.com/WICG/js-self-profiling. Ideally after that is shipped then we can use it to surface some longtask attribution. |
We did some experiments at Elastic, here are the relevant details - WICG/js-self-profiling#21 |
FWIW, I'm cautiously hopeful to make progress on that using Task Tracking as infrastructure on top of which attribution can be built. |
Marking as duplicate of #89 |
In long task API has a name attribute, which value is self. It's not more specific detail to find long task. If we find which script or function is taking longer than 50 ms, the optimize is too easy.
The text was updated successfully, but these errors were encountered: