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
I'm speaking to you as a third-party developer creating scripts that run on a wide variety of websites. I'm currently at a stage where I need to gather detailed performance data. The more information I can collect, the more specific and valuable recommendations I can provide to my customers.
In particular, I'd like to better understand what happens between the moment a scheduler.yield() call is made and when execution resumes. While I can already measure the duration of this pause, I want to go further by identifying what happens during that time. This could offer insights into optimizing specific parts of a website and its integrations.
Since third-party scripts run on various websites where we don't have prior knowledge of their implementation, I believe we share common goals:
Minimize the impact of third-party scripts on each website.
Maximize the performance of third-party scripts, especially given that some parts are tied to the complex ecosystem of online advertising.
By understanding the actions that take place during the pause created by scheduler.yield(), I believe I can significantly improve how the product interacts with different websites and enhance overall performance and integration efficiency.
The text was updated successfully, but these errors were encountered:
Tracing of some sort seems like it would be helpful. Could you maybe use the JS Self-Profiling API to collect traces during this period? (The availability is currently limited to Chromium-based browsers).
I'm speaking to you as a third-party developer creating scripts that run on a wide variety of websites. I'm currently at a stage where I need to gather detailed performance data. The more information I can collect, the more specific and valuable recommendations I can provide to my customers.
In particular, I'd like to better understand what happens between the moment a
scheduler.yield()
call is made and when execution resumes. While I can already measure the duration of this pause, I want to go further by identifying what happens during that time. This could offer insights into optimizing specific parts of a website and its integrations.Since third-party scripts run on various websites where we don't have prior knowledge of their implementation, I believe we share common goals:
By understanding the actions that take place during the pause created by
scheduler.yield()
, I believe I can significantly improve how the product interacts with different websites and enhance overall performance and integration efficiency.The text was updated successfully, but these errors were encountered: