I'm launching a Google Web App (within the Google Workspace of a company), and I would like to know if it has a maximum capacity of simultaneous users and if so, I would like to know the max capacity number.
I searched on Google Workspace page, Google for Business page, developers.google.com, and Google Search but I couldn't find anything except this article. The first response says the limit is 30 simultaneous users, but the other response says that with Google for Business you can increase it. Also, this article is two years old, so maybe things have changed.
If the maximum capacity is lower than 50 simultaneous users, I would like to know if someone has a way to increase it, or make a workaround. And if this isn't possible I would like to know if there is an alternative to overcome it.
From already thank you for your time and dedication!!
The maximum simultaneous connections per user is 30. The same limit applies to Google Workspace users.
https://developers.google.com/apps-script/guides/services/quotas#current_limitations
Because this is calculated on a per user basis, it depends how you've deployed it. If it's running as the user accessing the app, this limit shouldn't pose problems. If it's running as you (the person deploying the app), you'll start to see errors when more than 30 people are concurrently accessing it.
Related
We have a very complex core banking system using MongoDB and Google Sheets, and we are hitting the Google Apps Script quota limits and getting timeouts daily. We are looking at optimizing where we can, but I need to know if there is a way that I can increase the limits somehow in the meantime (don't mind paying more).
I have looked at the Early Access Program, but it says that they aren't taking any more new members.
Any ways that I can increase the limits?
Yes, you can
If you have a look at the Apps Script Quota information, you will see that the limits depend on the type of account you have.
If you have a free account, it means that most likely it is a Customer Account.
You can upgrade to either G Suite Basic, G Suite Business or G Suite Enterprise - depending on how much you need to increase your quota and how much you are willing to pay.
See here for more information about different accounts and pricing.
In their notifications about the new billing system for the Google Maps APIs, Google very clearly state that you "can set usage limits to protect against unexpected increases". However, I haven't found any documentation regarding how to set these usage limits against an API key. Does anyone know how to do this?
To clarify, I would like to set my own daily usage limits against my API key to prevent it ever going over the free threshold for the static maps API.
I understand Google means that you can set your custom daily quota for each individual API in order to stay within free 200$, not a global per API key/project/Billing account daily quota. As far as I know there is no such thing as limit per daily usage in $ per Billing account yet.
There are alerts that you can establish in your Billing account and receive notifications if your usage is close to the defined budget. Have a look at the following document that explain how to set alerts:
https://cloud.google.com/billing/docs/how-to/budgets?hl=en
If your project uses only Static Maps API, it is easy to set daily quota to stay within 200$ per month. The price sheet says that you can have up to 100 000 free requests per month. That means 100 000 / 31 = 3225 free requests per day. You can go to Quota section of Static Maps API in your project
https://console.developers.google.com/google/maps-apis/apis/static-maps-backend.googleapis.com/quotas?project=YOUR_PROJECT_ID&duration=PT1H
and change your daily quota as shown in my screenshots
edit number requests per day
and you are set.
I hope this helps!
OK a bit late for reply, but maybe somebody else can use this.
You do get tons of free map hits etc.
If you don't link a pay account, then you are limited to 1 hit per day (that's google maps) which is useless. All other quotas like 10000 per 100 sec etc are secondary to the 1 hit per day.
Now once you have linked your pay account or a Credit Card etc, to google development console then you get full quota for free user, plus more if you go over your quota covered by your Credit Card.
However don't panic, for first year it's all free and you get $300 (at this moment) worth of free stuff.
Even if you go over this limit Google will first ask you if you wish to change to payment system or continue with free.
If you decide to pay then you will be charged per indicated on google dev site.
If you decide to go with free option then the service to your site will stop until next rotation, i.e. day or month etc depending on service.
see this table.
Unless you have millions of hit on your map page or app, then the free quota is more than enough for normal sites.
Here is a price calculator by google.
As you see you get a lot of unlimited stuff and some paid if you go over your recurring credit of $200 or $300
Google makes it so complicated because it involves people coming from old system and those registering between roll over etc.
perhaps this will help too.
You can also set budgets and alerts just in case you go over budget (via Billing section of dev site)
So in short :) you get tons of free and if you have a lot of visitors the surely you make some money to pay for the services.
Note that google charges for all their API services in 1 place so if you use say Geocoding and firebase and cloud dev etc then you will soon start paying.
Sorry for any typos, I did this fast.
Capping API Usage
Depending on the API, you can explicitly cap requests in a variety of ways, including: requests per day, requests per 100 seconds, and requests per 100 seconds per user.
You might want to limit the billable usage by setting caps. For example, to prevent getting billed for usage beyond the free courtesy usage limits, you can set requests per day caps.
For more info, check this doc: https://cloud.google.com/apis/docs/capping-api-usage
I created an extension and published it 2 days ago.
On the Web Store it says that there are 10 users, but if I look at the Google Analytics that I installed on my extension it says "305 Users, 604 Pageviews" etc, and if I sort my audience by city, I get a large array of locations and the number of sessions is very even across 20-25 cities...
So my question is, how accurate is the web store with showing the amount of users? Perhaps a lot of my users removed the extension, but even so, I'd expect more than 10 stuck around.
Those are weekly stats representing the number of active installs; don't expect them to update often.
If you use Google Analytics in the extension itself, it provides a much better and up to date picture.
You can also look at those stats (while logged in to the developer account): https://chrome.google.com/webstore/developer/stats/<your_id_here>, available as a link from Developer Dashboard.
As your extension is still fairly new it may take a day or two before you are seeing numbers that reflect what you are seeing in Google Analytics.
Per the Google: https://support.google.com/chrome_webstore/answer/1154142?hl=en
The number of users includes everyone who has ever installed your item
in the store, so it is likely greater than the number of weekly
installs.
If the number of users is less than the the number of weekly
installs, this may indicate that users are uninstalling your item.
These user count is supposed to update everyday but it's not always reliable.
The developer dashboard does track the total number of installs and impressions but even then it's only for a limited time period (3 months) and it's sometimes unreliable as there are certain outages where you won't get any data back.
A more accurate way would be to add a listener (chrome.runtime.onInstalled) for the install event and trigger a tracking beacon accordingly. Source: https://developer.chrome.com/extensions/runtime#event-onInstalled
As #Xan stated earlier using google analytics or something similar is your best way in determining the "actual" number of active users (daily, weekly, monthly, etc.) Simply take the values listed on the Chrome web store with a grain of salt.
On a related note a useful tool I've found in quickly seeing total number of "users" as per Chrome Store is My extensions. It helps with getting notified of user reviews as well.
Also, is there a way to check what your current QPS limit is? We are currently experiencing a large number of errors with the following info:
<errors xmlns='http://schemas.google.com/g/2005'>
<error>
<domain>GData</domain>
<code>rateLimitExceeded</code>
<internalReason>Rate limit exceeded, lower query rate</internalReason>
<extendedHelp>Request rate limit exceeded.</extendedHelp>
</error>
</errors>
We have stats around all our drive calls. As far as I can tell, we should be well under our QPS.
When only counting "drive API" calls (calls made using the drive API) we're at about half of what our QPS limit should be. If you add in calls made to the export links (which are in the format of the old Document List API) we are still below what our limit should be.
I have tried reaching out to google to confirm what our limit is, and whether or not we are are actually going over our QPS (or if there's something else going on) but have not received any reply. Anyone have any thoughts?
Also, we are using exponential backoff and have implemented it as suggested in the Drive API docs.
In the api console you can see and increase the rate limit per second. Increasing it also means that a bad user could consume the entire quota. If youre making the api calls using a single user's auth is worse than distributing it across each user's own auth token since the limit is per user.
In Salesforce I have created a future method that makes a Google Maps geocode callout. I know there is a limit of 2,500 requests per day but our instance has made no more than 100 requests today. Maybe the same number of requests yesterday. Yet the response code is 620 G_GEO_TOO_MANY_QUERIES.
Could it be that Google is seeing the IP address of the instance of Salesforce and aggregating all of these requests as coming from one location. So other companies that are sharing the address are causing my instance to hit this limit?
If not can anyone suggest another cause?
This discussion suggests that it is the shared origin from salesforce that is messing it up.
This only makes sense though if you are doing the geocode lookup from the server and not from a client. If you would do it fromt the client it would use the ip from the client and you are dealing with the local clients lookup limits (see below).
If you are doing it on the server you might also have to check if you are actually doing something that is legal and not breaking the ToS from google. In this discussion you will get some background on that and also a solution if you need to fix this on the server (buy a licence)
To be complete the G_GEO_TOO_MANY_QUERIES can mean one of 2 things:
You exceeded the daily limit (too many in a day)
You exceeded the speed limit (too many request is too short period)
Google has not specified an exact limit as far as I know but they don't seem to enjoy automated lookups. If you look at various libraries and plugins you'll see that all of them force a delay between each request and often they add a little randomness to the delay. You could experiment with this if it makes any difference
Did this end up working for you? we're hitting a server-side 620 and all configuration looks a.o.k... we have a premier license and upgraded to 250k requests per day.