RyanHeidorn
StaffJoined 11 years ago
User Profile
Staff
User Widgets
Contributions
Re: Report analysis-How to analysis the graph result,what is the count of user that can handle a website
Hi AlexKaras When LoadComplete — or more specifically, the Remote Agent Service that is used to generate load — is running a test, it will consume all available CPU resources. (As a side-note, we are looking to change this behavior in the future to be more responsible with CPU resources.) Monitoring the CPU on the machine that is generating the load will not provide a useful metric. To determine load capacity on a local machine, I would be looking to see how the web server responds to all the requests that are generated. In my example above, I determined load capacity by looking at server responses. When the server was overloaded, I started to see HTTP status codes of 500 Internal Server Error. Does this help?Re: Rule for automatically setting constant value across all my request paths
Hi SagarShroff I have been thinking about how to accomplish this. There is not currently a quick way to do it, but I believe if you spend some time on the script, it will be very easy to change in the future. This is how I would approach it: Create a constant variable that contains the value you want in the request path. For each request in your scenario that will have a changing URL, create a Data Replacer for the request path. I attached an screenshot you can use as an example. When the request path value changes in a future release, simply edit the constant variable you created and all the requests using the data replacer will be updated automatically. I also suggest going to our feature request forum and requesting some "find / replace all" functionality that could simplify this process going forward. Hope this helps.Re: Report analysis-How to analysis the graph result,what is the count of user that can handle a website
Hi Alex, The process I outlined in my post was intended to be a guide for how you might approach stress testing. My own test conditions are unrealistic, as I used LoadComplete to test a locally hosted application, so network was not a consideration. As such, I was generating the load and hosting the app on the same machine (a laptop — Intel i7-3540M 3.0GHz, 8GB RAM, SSD — with an ASP.NET app hosted on IIS 7.5). I was actually surprised this environment could handle as much load as it did. Hope this helps.Re: Report analysis-How to analysis the graph result,what is the count of user that can handle a website
Hello Manav, The following documentation article may be useful to you: Load Testing: Checking Whether Server Supports a Certain Number of Users There is no single configuration to achieve the test objectives you have described. In general, you will want to use a Stepwise load profile so that you can see at what point performance issues may occur. A good starting point is to identify what kind of peak load your application currently receives. If such data is not available, you may make an educated guess based on the amount of concurrent load you may need to support. For example, to find the crash point for my application, I started by running a test for 100 VU, then 500 VU, then 1000 VU and so on. My 100VU test passed with no problems. My 500VU test also passed, but I noted that Page Load Time was much worse. My 1000VU test failed, and the graph is shown below: I can see that errors occurred, but not until my load had ramped up to 1000VUs. Therefore, I ran another test for 1500VUs: In this test, I can clearly see that the server began to give me errors around 1100 users. I then consulted the Details report to see exactly what errors occurred. This article on Analyzing Results may also be useful to you. Hope this helps.Re: Rule for automatically setting constant value across all my request paths
Hi SagarShroff, Is the URL string for your requests a dynamic value that changes from run to run, or is it a constant value that changes with each software release? Is it every request in your scenario, or only a few? Variables that you create in LoadComplete can be easily inserted in the /Request/Path/ field. The process is the same as with any parameterized value, so you can use the Parameterization Wizard or you can manually create and use the variable where appropriate. If the value is a constant and does not contain any special characters, my suggestion is to create a constant variable and manually insert the variable directly into the request header, as seen below: Please let me know if this helps.Re: Validation error
Hi SagarShroff, I have seen a similar issue where LoadComplete had difficulty processing chunked JSON responses. I do not know if this situation applies to you as well, but I suggest contacting our support group for more help. If it is indeed the same issue, I know we have a prepared a patch that addresses the issue. If it is a separate issue, our support team will still be happy to assist. :) Best,
