SHIMODA Piro Hiroshi
null+****@clear*****
Sat Oct 4 02:45:29 JST 2014
SHIMODA "Piro" Hiroshi 2014-10-04 02:45:29 +0900 (Sat, 04 Oct 2014) New Revision: 877c4d9cdb004a7a686edee5eff412e1eada991d https://github.com/droonga/droonga.org/commit/877c4d9cdb004a7a686edee5eff412e1eada991d Message: Add more factors Modified files: tutorial/1.0.7/benchmark/index.md Modified: tutorial/1.0.7/benchmark/index.md (+1 -1) =================================================================== --- tutorial/1.0.7/benchmark/index.md 2014-10-04 02:43:39 +0900 (a4ee863) +++ tutorial/1.0.7/benchmark/index.md 2014-10-04 02:45:29 +0900 (07881a5) @@ -90,7 +90,7 @@ Look at the result above, and this graph. You'll see that the QPS stagnated around 250, for 12 or more clients. This means that the target service can process 250 requests in one second, at a maximum. -In other words, we can describe the result as: 250 QPS is the maximum throughput performance of this system - generic performance of hardware, software, and network. +In other words, we can describe the result as: 250 QPS is the maximum throughput performance of this system - generic performance of hardware, software, network, size of the database, queries, and more. If the number of requests for your service is growing up and it is going to reach the limit, you have to do something about it - optimize queries, replace the computer with more powerful one, and so on. And, sending same request patterns to Groonga and Droonga, you can compare maximum QPS for each system. -------------- next part -------------- HTML����������������������������...Télécharger
