Because of this issue, libraries shouldīe used sparingly in add-ons, and you may want toĪvoid them in non-add-on scripts that make lots of calls. HTML Service user interfaces that make repeated,Ĭalls, the delay will affect every call. Isn't noticeable for relatively long-running scripts (like a utility script toĬlean up your Google Drive files), but for client-side Libraries are a convenient way to reuse code,īut they slightly increase the time it takes to start the script. Just 1 second! Avoid libraries in UI-heavy scripts
FREEFILESYNCH BATCH SCRIPT EXAMPLE CODE
The inefficient code takes about 70 seconds to run. Sheet.getRange(1, 1, 100, 100).setBackgroundColors(colors) The array are written out to the spreadsheet: // OKAY TO USE THIS EXAMPLE or code based on it.Ĭolors = getColorFromCoordinates(xcoord, ycoord) Rewrite in which the cell range is read into an array called colors, the colorĪssignment operation is performed on the data in the array, and the values in Of the caching, there are only 100 calls to the Spreadsheet.īut the code can be made much more efficient by batching the calls. The Google Apps Script write-back cache helps,īecause it forces a write-back using flush at the end of every line. The script is inefficient: it loops through 100 rows and 100 columns, writingĬonsecutively to 10,000 cells.
Var c = getColorFromCoordinates(xcoord, ycoord) It is an example of SLOW, INEFFICIENT code. GetColorFromCoordinates() (not shown here) to determine what color to useįor each cell: // DO NOT USE THIS CODE. Uses the following code to set the background colors of every cell in aġ00 x 100 spreadsheet grid. Here's an example - an example you should not follow or use. Perform any operations on the data in the array, and write the data out with To speed up a script, read all data into an array with one command, Minimizing the number of reads and writes.
You can write scripts to take maximum advantage of the built-in caching, by To retrieve what a script is likely to get and write caching to save what is Script already has some built-in optimization, such as using look-ahead caching Scripts commonly need to read in data from a spreadsheet, perform calculations,Īnd then write out the results of the data to a spreadsheet. Makes development and maintenance of the project easier. If you are working on a script project with other developers, you canĬollaborate on Apps Script projects with shared drives.įiles in a shared drive are owned by the group, rather than individuals. Consider collaborating with shared drives Your scripts will run faster if you canįind ways to minimize the calls the scripts make to those services. Google's servers or an external server, such as requests to Spreadsheets, Docs, Itself will be much faster than making calls that need to fetch data from Anything you can accomplish within Google Apps Script Using JavaScript operations within your script is considerably faster thanĬalling other services. This document lists best practices that will help you improve the performance
0 kommentar(er)
