If suppose i am having more than one google plus pages and configuring them in difference brands (using the same application).In this case the rate limit (say 500 per min) will be decreased for both pages or each page having 500 requests? Thanks in advance.
There are Several Google quotas. These quotas are valid for all Google APIs the only difference really is the amount of quota you receive.
Queries per day 10,000
Queries per 100 seconds per user 500
Queries per 100 seconds 1,000
Queries per day is a project wide quota. Your application identified by the client_id and client secrete you are using can run max 10000 request per day.
Queries per 100 seconds per user this is a speed quota or flood protection really. Each user who has authenticated your application can make a max X queries per 100 seconds. in the case above the user can make max 500 request with in 100 seconds.
Queries per 100 seconds this last one is project wide. Your application identified by the client_id and client secret. Can make 1000 requests in 100 seconds.
All but the user based one can probably be increased by clicking on the penile icon in the Google developers console. Depending upon the API you may have to pay for the increase. I doubt this is the case with the Google+ pages API.
Related
my mouse can't check the checkbox in the picture to increase "Queries per 100 seconds per user" of Google drive api.
what could be the reason for this? I have followed the instructions to join a paid account.
"Queries per 100 seconds per user"
is a user based quota and can not be increased. Only the project based quotas can be increased.
I have a web page which contains many filters and some as drop-down options. For example, Filter called (Time Range-- with options Last 24 hours, All, Last 7 Days).
The web page supposes to open by 100 users at the same time and select one option from the Time Range drop-down).
Kindly let me know how to find the duration by 100 users at the same time and select one option from the Time Range drop-down).
Thanks in Advance.
JMeter automatically measures response time for each sampler, if you want to have the total time - open .jtl results file using LibreOffice Calc or Microsoft Excel or equivalent and sum up all the response times for all 100 samplers
In order to guarantee the desired concurrency add a Synchronizing Timer as a child of the request and set Number of Simultaneous Users to Group by to 100
Add View results table Listener to the suite to check the duration and Start time of each thread and connect time of each thread.
As I understood you want to check the load of 100 concurrent users clicking the filter , so the login process and its load should not interfere the load testing of users clicking the filter button. Hence, As mentioned in above comment, you can use Synchronizing Timer as child f the requests. What it does is, it is synchronized with the login requests and wait for the response of all the 100 users getting logged in. Once all the 100 users are logged in, Synchronizing Timer play its role by sending (clicking) requests at the same time same second. Cant ensure same milliseconds. There might be small difference in milliseconds, which you can see in View results table (start time).
i work on a spring 4 web app rest with angularjs
i have to limit the number of users connected at the same time because sometimes it's very slow and users have timeout. The goal is to show a modal with a message when the max users is reached
it would be a first step before a better monitoring
I am using Google Search Console URL Testing Tools API, I have a problem in the understanding limit quota of API. It says:
Project per-second limit per 100 seconds = 1
User per-second limit per 100 seconds per user = 1
What does that mean?
Most of highly used APIs (google, facebook..) have short-time limits and long-time limits for better control over traffic. It allows developers make many requests (eg. 20000 per day) but prevents throttling if someone would try to eg. send 1000 requests in one second, which could clog api endpoint.
What you have in your google console:
Project per-second limit per 100 seconds = 1
That means you can make 1 query for 100 seconds in each project.
And:
User per-second limit per 100 seconds per user = 1
That means you can make 1 query for 100 seconds for each user connected to project.
That two limit rules putted together dont make much sense beacuse second rule will never be triggered (both have 1 request per 100 seconds but first one is for 'higher' resource and will block more requests).
Example of many limits you can see eg. in Analytics API where we have:
Queries per day = 50000
Big limit for queries per day.
Queries per 100 seconds per user = 100
Small limit per 100 seconds and per user so they can prevent too high peaks of requests from single user.
Queries per 100 seconds = 2000
Medium limit per 100 seconds.
My test case is Users starts from 1000 and in next 1 hour there will be 10k users on website.
I am confuse that how can I increase users in jmeter so when test reach at 1 hour, I can see 10k active users.
Should I use ultimate thread group for this? I just want hint from expert to go to next step.
From what i have understood, you want to have 1000 users immediately, then slowly 9000 users in the next 1 hr, so that you will have 10000 users.
Then ultimate thread group seems to be a good choice for this exact requirement.
Hold Load for sec is the test duration with 10000 users. adjust accordingly.
Or, if your requirement is just to have 10000 users in 1 hr, (not 1000 in the beginning) , you can also use regular thread group.