How many requests a second can you throw at your Google Apps Script webapp

There was a question on the Google Apps Script Community the other day. It went something like this.

This is an important question, because if you have a webapp, potentially used by many people – is it going to run out of some kind of quota and start to fail.

Here’s a simple webapp. I’m going to throw as much as I can at it by making asynchronous requests from a few instances.


The results

I can get about 35 responses per second before consistently getting
Script invoked too many times per second for this Google user account.

The conclusion

You’ll need to always use exponential backoff when running popular webapps. You can find a snippet for that here.

Here’s the code for the test. I’m making asynchronous jsonp requests, and reporting the results with a Google Viz table.

For more like this, visit the desktop liberation site, or follow me on Twitter, and join the Google Apps Script Community.


About brucemcp 225 Articles
I am a Google Developer Expert and decided to investigate Google Apps Script in my spare time. The more I investigated the more content I created so this site is extremely rich. Now, in 2019, a lot of things have disappeared or don’t work anymore due to Google having retired some stuff. I am however leaving things as is and where I came across some deprecated stuff, I have indicated it. I decided to write a book about it and to also create videos to teach developers who want to learn Google Apps Script. If you find the material contained in this site useful, you can support me by buying my books and or videos.

Be the first to comment

Leave a Reply

Your email address will not be published.


two − one =