用户级别的Gmail-API请求配额 [英] Gmail-API request quota at a user level

问题描述

注意:这个问题是关于我在此处的文档中不了解的内容: https://developers.google.com/gmail/api/v1/reference/quota#concurrent_requests

Gmail API强制执行每个用户的并发请求限制(在以及每个用户的速率限制).此限制由所有人共享Gmail API客户端访问给定用户，并确保没有API客户端超载Gmail用户邮箱或其后端服务器.

The Gmail API enforces a per-user concurrent request limit (in addition to the per-user rate limit). This limit is shared by all Gmail API clients accessing a given user and ensures that no API client is overloading a Gmail user mailbox or their backend server.

 enforces a per-user concurrent request limit (in addition to the per-user rate limit).

我在他们的文档的任何地方都找不到每用户并发请求".而每个用户的速率限制位于同一页面的顶部. https://developers.google.com/gmail/api/v1/reference/quota#top_of_page

I do not find what is the 'per-user concurrent request' anywhere in their documentation. Whereas the per-user rate limit is found at the top in the same page. https://developers.google.com/gmail/api/v1/reference/quota#top_of_page

推荐答案

Gmail API强制执行每用户并发请求限制(除了每用户速率限制之外).此限制由访问给定用户的所有Gmail API客户端共享，并确保没有API客户端超载Gmail用户邮箱或其后端服务器.

The Gmail API enforces a per-user concurrent request limit (in addition to the per-user rate limit). This limit is shared by all Gmail API clients accessing a given user and ensures that no API client is overloading a Gmail user mailbox or their backend server.

这里的困惑是每用户并发请求限制和每用户速率限制

让我们说我制作了一个应用程序，允许用户从其Gmail帐户中读取信息.我将受到每个用户通过 MY 应用程序可以发出的请求数量的限制，该限制是每用户速率限制

Lets say I make an app that lets users read from their Gmail account. I am going to be limited by the number of request each user can make though MY app the limit is per-user rate limit

现在，可以说用户安装了您的应用程序，这也使他们可以访问其Gmail帐户.您还受限于用户通过每用户速率限制访问api的速度.

Now lets say the user installs your app which also allows them to access their Gmail account. You are also limited to how fast the user can access the api via the per-user rate limit.

但是，我们的所有应用程序以及gmail和收件箱应用程序都在用户正在使用的所有应用程序中均以相同的每用户并发请求限制并发运行.

However both of our APPs and the gmail and inbox apps are are all running with the same per-user concurrent request limit concurrent meaning across all of the apps the user is using.

每个用户的并发请求限制可能在此处，以确保开发人员不会创建多个不同的项目并使用所有项目提取数据.

the per-user concurrent request limit is probably there to ensure that a developer doesn't create a number of different projects and rip data using all of them.

据我所知，每用户并发请求限制并未记录其隐身限制，而且我从未见过能够确定Google并发限制的确切数字的人蜜蜂.除了Google Analytics API(它是10000，不包括Google Analytics(分析)网站和官方移动应用)

To my knowledge per-user concurrent request limit is not documented its a stealth limit and i have never seen anyone who has been able to nail down exactly what the numbers are for the concurrent limits in Google APIs. With the exception of the Google Analytics API which is 10000 not including the google analytics website and the official mobile apps

示例:

每用户速率限制

1. 第一位用户登录并列出了他有10位用户的所有电子邮件，都没有错误.
2. 第二位用户登录，他有1000封电子邮件，您的应用程序尝试在1秒内将它们全部选中.您将获得此用户的速率限制错误.您正在泛滥Google.但是其他开发人员的应用将能够通过API访问用户收件箱

1. User number one logs in and lists all of his emails he has 10 user gets no error.
2. User number two logs in, he has 1000 emails and your application tries to select them all out in 1 second. You are going to get a rate limit error for this user. You are flooding google. However apps by other developers will be able to access the user inbox via the API

每用户并发

1. 第一号用户仅在运行您的应用程序.登录并列出他有10位用户的所有电子邮件，都没有错误.
2. 第二个用户正在运行您的应用程序，其他开发人员正在运行其他20个应用程序.特里斯(Tries)列出了他所有的电子邮件，并假设他同时在所有应用程序上执行了此操作，可能最终会出错.

这些错误是基于用户的，因为限制名称中的名称为每用户".

These errors are user based due to the name Per-user in the name of the limit.

示例2:

让我们看看Google Analytics(分析)API，因为我知道此API的具体数字.

Lets look at the Google analytics API because i know the hard numbers for this api.

• 使用您的应用的用户最多可以在90秒内发出100个请求.(基于用户应用)
• 一个应用程序每天最多可以发出50000个请求.(基于应用)
• 所有应用程序每天最多可针对一个视图(基于并发应用程序)最多发出10000个请求

这篇关于用户级别的Gmail-API请求配额的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！