stress-testing

问题 I need to stress-test a system and http://locust.io seems like the best way to go about this. However, it looks like it is set up to use the same user every time. I need each spawn to log in as a different user. How do I go about setting that up? Alternatively, is there another system that would be good to use? 回答1: Locust author here. By default, each HttpLocust user instance has an HTTP client that has it's own separate session . Locust doesn't have any feature for providing a list of user

问题 As it currently stands, this question is not a good fit for our Q&A format. We expect answers to be supported by facts, references, or expertise, but this question will likely solicit debate, arguments, polling, or extended discussion. If you feel that this question can be improved and possibly reopened, visit the help center for guidance. Closed 7 years ago . I'm building a stress testing framework for node.js services using node.js. Do you know relevant projects which I can use / look at?

问题 I am using While Controller with Condition: ${_javaScript("${DONE}" ! = "Resolved and Downloaded";)} where initially DONE="Not Assigned yet" . After few iterations DONE changes and has value Resolved and Downloaded (which I check in Debug Sampler) but loop continues and doesn't quit. What did I do wrong,What should I do to make it work? 回答1: Check syntax of your condition expression first: should be double __ before function name and , instead of ; after condition in function's params list: $

问题 This question already has answers here : Stresstest Memory on Android (2 answers) Closed 8 months ago . I've been reading up on the Android dalvik, and I was curious as to how one would go about stress testing the Dalvik to evaluate its stability. I understand the Dalvik is meant for memory an processor constrained devices. So would allocating a lot of memory/increasing frequency of some CPU cores and then launching multiple applications be a way to test the stability? I also understand that

问题 How can you simulate/stress test about 100 users accessing a given shared resource (e.g. Database) in a c# unit test? 回答1: Assuming you're accessing real DB you're in the scope of integration tests. The simplest way is to access the resource from multiple threads. For example: [Test] public void SimpleStressTest() { bool wasExceptionThrown = false; var threads = new Thread[100]; for(int i = 0; i < 100; i++) { threads[i] = new Thread(new ThreadStart((Action)(() => { try { AccessDB(); } catch

问题 I'm figuring what a timer implementation to use if you need to schedule tons of (non blocking) tasks as fast as possible inside jvm on one machine. I've studied ScheduledThreadPoolExecutor and HashedWheelTimer sources (+wheel timer general docs) and here are basic differences (N - number of all outstanding scheduled tasks so far, C - wheel size): ScheduledThreadPoolExecutor O(log N) for adding new task O(1) per each timer tick (but tick per each task, so N overall) O(log N) cancelling the

问题 I want to conduct a stress and performance test on the front-end of my ASP.NET app. My goal is to: Identify bottlenecks Learn the number and the load of HTTP requests Easily determine the components that are using an Expires header and/or being gzipped Figure out where to increase download parllelization Locate duplicate scripts and unncessary redirects Determine the load that will bring down the servers Pinpoint key areas of server optimization Besides YSlow and Fiddler, are there any other

问题 We’ve come across this question fairly often at Load Impact, so I thought I’d add it to the Stack Overflow community to make it easier to find. How do I calculate the number of concurrent users (VUs) that I need to simulate during a load test, in order to stress my system with the same kind of traffic that it will normally see in the course of a month, week or day? 回答1: Running a load test requires that you specify how many concurrent users should be simulated during testing. In other words,

问题 I need to test if our system can perform N requests per second. Technically, it's 2 requests to one API, 2 requests to another, and 6 requests to third one. But the important thing that they should happen simultaneously - so 10 requests per second. So, in JMeter I've created three Thread Groups, first defines number of threads 1, and ramp-up time 0. Second thread group is the same, and third thread group defines number of threads 6 and ramp-up time 0. But that doesn't really guarantee it's

问题 I have been trying to load test my API server using Locust.io on EC2 compute optimized instances. It provides an easy-to-configure option for setting the consecutive request wait time and number of concurrent users . In theory, rps = wait time X #_users . However while testing, this rule breaks down for very low thresholds of #_users (in my experiment, around 1200 users). The variables hatch_rate , #_of_slaves , including in a distributed test setting had little to no effect on the rps .