What things contribute to Client Init time as show...
# ask-stanley-ai
a
What things contribute to Client Init time as shown in the Page Time Details Timeline? I have some records showing 88 seconds on just the Client Init part of the timeline, much longer than any other part. How do I find out what's causing it to take so long?
c
AI generated answer (using internal Slack threads):
****** Disclaimer: This response was generated by an artificial intelligence assistant based on previous conversations from multiple Slack channels, and may contain inaccuracies or mistakes. ****** The Client Init time in the Page Time Details Timeline can be influenced by several factors. Here are some of the main contributors: 1. Scripts Running on the Record: If there are multiple scripts running on the record, they can significantly increase the Client Init time. You can review these scripts and optimize them if possible. 2. Data Volume: If the record is handling a large amount of data, it can also increase the Client Init time. You can check your monthly transaction line count in Setup > Company > View billing information. If you're over 200k per month, you may be moving too much data for the standard shared database infrastructure. 3. Complex Operations: If the record is performing complex operations, it can also increase the Client Init time. 4. Server Performance: The performance of the server can also affect the Client Init time. However, you have little control over the server performance, except for the scripts and workflows running on it. To investigate what's causing the long Client Init time, you can use the Application Performance Management (APM) tool provided by NetSuite. This tool can help you identify the scripts that are taking a long time to execute. You can also double-click the NetSuite logo in the upper left after loading a record to see the breakdown of the load time. In addition, you can use the developer mode of modern browsers to see how long it's been loading on the client side. This can help you identify if there's something local that is causing the issue. Lastly, you can use a timing function to log the time elapsed for different sections of code. This can help you identify which parts of the code are taking the longest to execute.
Slack thread 1: here (available only if the original thread was posted in the last 90 days)
Similarity score: 0.816768408
Slack thread 2: here (available only if the original thread was posted in the last 90 days)
Similarity score: 0.815851629
Slack thread 3: here (available only if the original thread was posted in the last 90 days)
Similarity score: 0.810452223
Please provide your feedback on this answer.
Thank you for your feedback
Thank you for your feedback