Database Administrators Stack Exchange is a question and answer site for database professionals who wish to improve their database skills and learn from others in the community. Join them; it only takes a minute:

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

I've seen so many times that we use numbers like 5,6 or 10 at most. What is this concurrency? Doesn't it refer to number of simultaneous users in bench?

I'm not talking about any specific benchmarking tools, I mean in general. In benchmarks for databases OR for apache servers we use low concurrent numbers. why is that the case?

share|improve this question

closed as not constructive by Derek Downey, Aaron Bertrand, Paul White, Martin Smith, Mark Storey-Smith Nov 6 '12 at 15:32

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.If this question can be reworded to fit the rules in the help center, please edit the question.

Hi John, could you be more specific in your question? Like what software you are using to benchmark, some detail about what your analyzing, etc. – Craig Efrein Apr 27 '12 at 6:21

It really depends on what you are modeling. For mysql there are a few different definitions for simultaneous users.

  1. Number of database connections, including idles that only take up memory.
  2. Number of running queries.
  3. Number of queries active in the database engine. This is typically ignored.

With a typical web application, you may have a hundred connections open to the database, but only a handful actually running queries at any single time. You can view this number by running SHOW STATUS LIKE 'Threads_running';. Perhaps run it in a loop and see how it changes. Benchmarking the inactive connections is typically a waste as they just use some memory and not much cpu. So if your application only is running x number of concurrent queries at a time, might as well only benchmark x, even if it's a small number.

share|improve this answer

Not the answer you're looking for? Browse other questions tagged or ask your own question.