Hi there I am trying to conduct stress and scalability testing for a web application. One of the problem is that it is not clear how many users the website can handle. So first I am conducting a stress testing with different user number. Consider below picture:
In the picture first I am starting with 100 user by gradually increasing the load. So i have requirement for example:
Response time should not be 7 sec
throughput should not fall under 35 request per second
Percentage of error should not be more than 10 percent of the total request
So if this 100 user satisfies the requirement I will continue the test with 150 user and will go on until it breaks at least 2 requirement out of 3. And with that user I will perform the scalability test. Is this approach right? Please give me advise and how should I simulate user if not right?
The approach is more or less right. However you could save your time and efforts for finding the breaking point of the system with a single test only, just start with 1 user and gradually increase the load until the maximum.
JMeter's theoretical limit for a single Thread Group is 2,147,483,647, your actual limit will be less as most probably your hardware resources are limited, check out What’s the Max Number of Users You Can Test on JMeter? article for more details.
Whatever, if you put a reasonably high number of threads in the Thread Group and configure the load to increase gradually you can run your test and pay attention to the following charts:
Active Threads Over Time - shows the number of active users
Response Times Over Time - shows the system response time
Transactions Per Second - shows the throughput (the number of requests per second)
At first stage of the test response time will be the same and the throughput will be growing as you increase the load. At the certain point of test the response time will start increasing and throughput will be going down - that would be the limit of your system (so called "bottleneck")
Related
I recently subscribed on HERE Api for Freemium account, cause as far as I understood, I could make 250k requests per month and only would be charged after that, recently I'm working on Waypoints Sequence, and suddenly during a dev test, I got the error "Daily limit of 10 requests has been reached".
I thought that the limit was 250k requests per month, but then I read that the user can only make 10 requests per day by App ID, but makes no sense when the month limit is significantly higher.
Out of Freemium Account there's only the Pro/Premier Plans, which are actually very expensive for me right now.
Does anyone have a workaround for this? Or have another "Waypoints Sequence" tool to recomend?
Thank you all in advance
Currently, for Freemium plans only, the following limits apply:
Custom Locations: you may upload a maximum of 3 layers with a maximum of 100 polygons or polylines.
Waypoints Sequence: up to 10 requests per day.
Advanced Data Sets: up to 100 requests per hour and 1,000 per day.
Please contact our Sales team (Contact Sales) if you want to raise your limits. Thank you.
I'm in the process of devolving a new tool for a company app. The tool will be sending homogeneous number of searches to amadeus API. Is every search result is considered as a request? A sample search of a user will have to search the api 1000 times are these searches considered as requests? Because if the company has 10000 request limit per month it's going to be over by 10 users! I need to understand this please.
Every time you call an API (every time you use GET/POST verb) you do a "request".
The limitation (quota) is only in the test environment, you don't pay for it but you have a limited number of calls and you only have access to a subset of data.
In production, you don't have any limitation on the total number of queries you can do. You get access to our full set of data (live) but you pay per use (you pay for each request you do).
You have a limitation on the number you can do per second (TPS: 10 in production / 5 in test).
I have routines that synchronize Class/Roster information between an SIS and Google Classroom. Everything has been running smoothly until very recently (11/1/2016). Now we're seeing the following message in all of our log files for routines that handle Classroom syncs.
Insufficient tokens for quota group and limit 'DefaultGroupUSER-100s' of service 'classroom.googleapis.com', using the limit by ID...
We perform batch requests whenever possible and these errors are showing up in individual batch "part" responses. The fact that these errors suddenly started showing up for ALL of our Classroom routines makes me think that something changed on the Google end of things.
I've been playing around with the throttling on our end by changing both the number of requests that we send in each batch (docs say that you can send 1000 per batch) as well as the total number of requests/batches that we're sending per 100 seconds (docs say you can send 50/s/client and also 5/s/user). Interestingly, the quotas indicated in the development console display slightly different but I assume they are to be interpreted in conjunction with one another.
I've throttled things down to the point where we're not even getting close to 5 requests per second and I'm still getting these errors back from the server.
Can someone provide some suggestions or solutions. Has anyone experienced this lately?
Let me know if I any additional information is needed.
noob here using Arduino Wifi (Adafruit CC3000) to send data. Or try. I have read and understood about rate limits and a limit on number of data items uploaded per connection. But I searched and cannot find what the numbers are for those limits. One per minute? I have deduced by testing that the number of data items is two, and tried to send my 6 data points in three consecutive calls of two. That crashes and burns with assorted errors, so I suspect I'm hitting the rate limit.
P.S. Two datapoints per minute work, so API key, etc is not an issue.
Can anyone tell me what these limits are?
Thanks very much for your time.
If you have a developer account (free), you have a max of 25 requests per minute. This includes if you have an app on the front end pulling/sampling the data. It includes all the GET PUT and socket connections as well.
Src: http://forums.electricimp.com/discussion/2108/max-frequency-of-updates-to-xively-wo-getting-booted/p1
I just started playing with the Google Map API for Static Images, and in just an hour it has appeared this image:
http://www.coon.it/drop/limit.png
Is that normal?
My page need 6 static image, that means that I call it, like 170 times?
I don't think it's possible since the pictures are always the same and the documentation says that if i call the same image it doesn't count.
What can i do?
Thank you
Although there is an absolute limit on the number of images, that limit may be calculated over a shorter period than 24 hours. 2400/day could be interpreted as 100/hour, so you can't use all 2400 in one go [I can't remember what the limit is for Static Maps, but you get the idea].
With most Google services there is also a rate limit, and it's possible that fetching six images almost simultaneously breaks the rate limit. Rate limits vary depending on server load, but spacing requests out to 200ms should be ok.
Or it may look like an automated image-fetcher (especially if you have run it 30 times in the last hour). Google don't like automated crawlers either.
What should it display? With me it just displays a landscape with a row of trees(what i gues is what you want to see?).