Question

我在网上应用(与春季、Stuts2 REST共同设计,使用邮政总局)。

我正在对典型用户情景进行模拟,我的评估是:

4 GET, 3 INSERT, 20 UPDATE calls.

www.un.org/Depts/DGACM/index_spanish.htm 服务器光谱:

4 核心国际通信组织

8GB RAM

缩略语

页: 1

DB: Postgresql 8.4

Tomcat 6.0.18

Java 1.6.014

结果表明,服务器将处理约130项同时交易。这个数字是可能的吗? 是否有与地雷相比较的在线结果?

Answer 1

瓶颈问题将列入你的数据库,因此很难比较,而不知道你的数据库业绩。

我们拥有类似的机器(16GB RAM除外,操作Tomcat 5.5)。在高峰负荷,可以方便地为256个同时连接服务。我们正在辩论,将最大范围改为512。

一些tu,

If you run Apache as front-end, use mod_jk. Its performance is much better than mod_proxy.
If you serve HTTP directly or use mod_proxy, use the NIO connector in Tomcat 6.
Make sure your thread pool (maxThreads) is large enough, default is only 200.
Make Tomcat state-less. Especially, don t use HttpSession. The state may cause memory leak in the app and degrade the performance gradually. Push all your state to database or client (cookies).
Do use Database pooling (DBCP). We have MySQL, the JDBC driver is very chatty.
If you run one instance of JMeter, it may become the bottleneck. Run multiple slaves from different networks to simulate real production load.