Note that there are some explanatory texts on larger screens.

plurals
  1. POHow should I stress test / load test a client server application?
    primarykey
    data
    text
    <p>I develop a client-server style, database based system and I need to devise a way to stress / load test the system. Customers inevitably want to know such things as:</p> <p>• How many clients can a server support?<br> • How many concurrent searches can a server support?<br> • How much data can we store in the database?<br> • Etc.</p> <p>Key to all these questions is response time. We need to be able to measure how response time and performance degrades as new load is introduced so that we could for example, produce some kind of pretty graph we could throw at clients to give them an idea what kind of performance to expect with a given hardware configuration.</p> <p>Right now we just put out fingers in the air and make educated guesses based on what we already know about the system from experience. As the product is put under more demanding conditions, this is proving to be inadequate for our needs going forward though.</p> <p>I've been given the task of devising a method to get such answers in a meaningful way. I realise that this is not a question that anyone can answer definitively but I'm looking for suggestions about how people have gone about doing such work on their own systems.</p> <p>One thing to note is that we have full access to our client API via the Python language (courtesy of SWIG) which is a lot easier to work with than C++ for this kind of work.</p> <p>So there we go, I throw this to the floor: really interested to see what ideas you guys can come up with!</p>
    singulars
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
 

Querying!

 
Guidance

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload