<p>about your learning experience to help us improve.</p>

You've completed

cleanFiles/bookmap_Optimizing_Performance_in_SAP_Analytics_Cl_en-US_learning-sap-com_lsc-prod.zip (MMCP-DROPZONE) - 2025-03-06T14:23:04.000Z

Exploring Scripting Performance

<div id="content"><div class="parentsection"><div class="section"><p tabindex="0">In this lesson, we will explore script processing in order to gain an understanding of how the Main and SandboxWorker interact when a script is processed in SAP Analytics Cloud.</p><div class="kalturaVideoLessonWrapper"><div aria-label="" class="kalturaVideoLessonContainer" data-testid="video" id="1_vme6dilv"></div></div></div></div><div class="parentsection"><div class="section"><div tabindex="0"><h3>Summary</h3></div><p tabindex="0">Script optimization is typically required when there are frontend performance issues, such as when a story with scripting doesn't perform as well on older or slower laptops but still performs well on more powerful machines.</p><p tabindex="0">In general, you should try to minimize the number of interactions between the Main and the SandboxWorker thread. So, whenever you use the same get or set function multiple times, it is an indication that there is something to improve. For example, using a local script variable, which is covered later on in this unit.</p><p tabindex="0">In addition, everything that happens in loops is relevant to script performance because it is executed multiple times. It's best practice to keep the array to loop over as small as possible, for example, using a limiting parameter when using the <code>getResultSet</code> API.</p></div></div></div>

Script Processing

Managing Performance in SAP Analytics Cloud

<div><div><div>Explore how scripts are processed in SAP Analytics Cloud Story, understanding main & SandboxWorker threads, script interactions, processing time impact, and optimization importance.<br><br># This description was auto-generated #</div></div></div>

Exploring Script Processing

In this video, we will explore how a script is processed in an SAP Analytics Cloud Story. To be able to apply some of the scripting recommendations, you need to understand how scripts are technically processed. When a story runs in a browser, there are two core threads that are used, the Main thread and the SandboxWorker thread. Let's use a very simple scenario as an example. You have a story with two text boxes. A user clicks the button in the story that runs a script. The script reads the text in the first text box and adds a word to this text, and then sends it to the second textbox. This is a simple and short script, but let's take a look at how the Main and SandboxWorker threads handle the task. The Main thread handles the whole story processing and can communicate with all of the data sources. However, it cannot process any scripts. For any kind of script processing, the Main thread sends the code to the SandboxWorker thread and asks for processing. Hey SandboxWorker, the user has clicked the button. Please process the script. The SandboxWorker thread is separated from the main story processing and has no access to any information that is handled outside of the script. This ensures that nothing harmful is programmed within the script. Okay, I will start processing it immediately. If the script needs to know something from the outside, The SandboxWorker must ask the main thread. Hey Main, I need the content of the text box. Can you send it to me? Sure, I'll look it up and get back to you. Here it is. Hello is the text in the textbox that you require. Got it. I will continue working. Done! Please write Hello World in the second textbox. Good job! I will update the textbox accordingly. The more interaction there is between the two threads, the longer the processing time will be, eventually leading to a slower performance of your story, which is why it's important to keep your scripts as optimized as possible. While we demonstrated this process using a series of chat messages, the events that are displayed are not part of performance analysis and optimization, they are simply the technical names for the events that are triggered for the Main and the SandboxWorker threads while the script is processed.