Resin3.1 优化

Resin3.1 优化 [转贴]2008-12-12 10:39使用resin已经有四、五年了，但以前都是做一些小系统，resin的压力并不大，近段时间做一个大系统，日平均ip上10万，resin的压力非常的大，除了对程序做优化以外，resin 的优化也小不了。

一、优化配置修改conf/resin.conf 文章中的ＪＶＭ参数<jvm-arg>-Xms512m</jvm-arg><jvm-arg>-Xss128k</jvm-arg><jvm-arg>-Xmn184m</jvm-arg><jvm-arg>-XX:ParallelGCThreads=20</jvm-arg><jvm-arg>-XX:+UseConcMarkSweepGC</jvm-arg><jvm-arg>-XX:+UseParNewGC</jvm-arg><jvm-arg>-Xdebug</jvm-arg><jvm-arg>-Xloggc:gc.log</jvm-arg>修改最大thread-max为2500<!-- Maximum number of threads. --><thread-max>2500</thread-max><!-- Configures the socket timeout --><socket-timeout>65s</socket-timeout><!-- Configures the keepalive --><keepalive-max>10240</keepalive-max><keepalive-timeout>30s</keepalive-timeout>二、利用resin-admin监控resin运行情况。

第一行是Thread pool情况，如果发现Peak大于thread max，就应该修改conf/resin.conf 中的thread-max，相应的增大thread-max。

第二行是Threads，如果长期出现在这里而又不是ＳＵＮ的方法，或者resin的方法的话，就要对这些方法进行测试、优化。

以下内容都是自己不断实验总结的，而非resin官方的建议，可能不适合你的情况，我的经验仅做为参考。

）最近发现有人用黑客类工具恶意点击网站，或发送大量垃圾包，具体是什么不清楚，但是很明显是故意的，造成80端口无法正常访问，或访问速度极慢。

用netstat -an >>c:\temp\aaa.txt 命令查看了当时情况，发现某几个ip的连接数量巨大，是不正常的。

不管是访问量大，还是有黑客骚扰，我想还是试试看把resin优化一下。

首先要在访问量巨大的时候进行观察。

先将resin.conf文件中的thread-min，thread-max，thread-keepalive三个参数设置的比较大，分别写上，1000，3000，1000，当然这是根据你的机器情况和可能同时访问的数量决定的，如果你的网站访问量很大的，应该再适当放大。

然后观察任务管理器中的java线程变化情况，看看到底是线程达到多大的时候，java进程当掉的。

我的是在379左右当掉。

然后将thread-min，thread-max，thread-keepalive分别写为150，400，300；，也就是将当掉的时候的最大值稍微放大点，作为thread-max的值，因为该系统一般不会超过这个值。

然后其他两个参数根据情况设置一下。

这只是我的估计值，根据机器性能和访问量不同，应该有所不同。

然后将accept-buffer-size值设置的较大，我设置到10000以上，这样可以让java能使用到更多的内存资源。

这样的设置基本上能够满足resin的正常运行，当掉resin服务的情况大大减少，本设置适合于中小型网站。

Resin ThreadsResin will automatically allocate and free threads as the load requires. Since the threads are pooled, Resin can reuse old threads without the performance penalty of creating and destroying the threads. When the load drops, Resin will slowly decrease the number of threads in the pool until is matches the load.Most users can set thread-max to something large (200 or greater) and then forget about the threading. Some ISPs dedicate a JVM per user and have many JVMs on the same machine. In that case, it may make sense to reduce the thread-max to throttle the requests.Since each servlet request gets its own thread, thread-max determines the maximum number of concurrent users. So if you have a peak of 100 users with slow modems downloading a large file, you'll need a thread-max of at least 100. The number of concurrent users is unrelated to the number of active sessions. Unless the user is actively downloading, he doesn't need a thread (except for "keepalives").KeepalivesKeepalives make HTTP and srun requests more efficient. Connecting to a TCP server is relatively expensive. The client and server need to send several packets back and forth to establish the connection before thefirst data can go through. HTTP/1.1 introduced a protocol to keep the connection open for more requests. The srun protocol between Resin and the web server plugin also uses keepalives. By keeping the connection open for following requests, Resin can improve performance.TimeoutsRequests and keepalive connections can only be idle for a limited time before Resin closes them. Each connection has a read timeout,request-timeout. If the client doesn't send a request within the timeout, Resin will close the TCP socket. The timeout prevents idle clients from hogging Resin resources.In general, the read-timeout and keepalives are less important for Resin standalone configurations than Apache/IIS/srun configurations. Veryheavy traffic sites may want to reduce the timeout for Resin standalone.Since read-timeout will close srun connections, its setting needs to take into consideration the client-live-time setting for mod_caucho or isapi_srun. client-live-time is the time the plugin will keep a connection open. read-timeout must always be larger than client-live-time, otherwise the plugin will try to reuse a closed socket.Plugin keepalives (mod_caucho/isapi_srun)The web server plugin, mod_caucho, needs configuration for its keepalive handling because requests are handled differently in the web server. Until the web server sends a request to Resin, it can't tell if Resin has closed the other end of the socket. If the JVM has restarted or if closed the socket because of read-timeout, mod_caucho will not know about the closed socket. So mod_caucho needs to know how long to consider a connection reusable before closing it. client-live-time tells the plugin how long it should consider a socket usable.Because the plugin isn't signalled when Resin closes the socket, the socket will remain half-closed until the next web server request. A netstat will show that as a bunch of sockets in the FIN_WAIT_2 state. With Apache, there doesn't appear to be a good way around this. If these become a problem, you can increase read-timeout and client-live-time so the JVM won't close the keepalive connections as fast.unix> netstat...localhost.32823 localhost.6802 327680 32768 0 CLOSE_WAITlocalhost.6802 localhost.32823 327680 32768 0 FIN_WAIT_2localhost.32824 localhost.6802 327680 32768 0 CLOSE_WAITlocalhost.6802 localhost.32824 327680 32768 0 FIN_WAIT_2...TCP limits (TIME_WAIT)A client and a server that open a large number of TCP connections can run into operating system/TCP limits. If mod_caucho isn't configured properly, it can use too many connections to Resin. When the limit isreached, mod_caucho will report "can't connect" errors until a timeout is reached. Load testing or benchmarking can run into the same limits, causing apparent connection failures even though the Resin process is running fine.The TCP limit is the TIME_WAIT timeout. When the TCP socket closes, the side starting the close puts the socket into the TIME_WAIT state. A netstat will short the sockets in the TIME_WAIT state. The following shows an example of the TIME_WAIT sockets generated while benchmarking. Each client connection has a unique ephemeral port and the server always uses its public port:The socket will remain in the TIME_WAIT state for a system-dependent time, generally 120 seconds, but usually configurable. Since there are less than 32k ephemeral socket available to the client, the client will eventually run out and start seeing connection failures. On some operating systems, including RedHat Linux, the default limit is only 4k sockets. The full 32k sockets with a 120 second timeout limits the number of connections to about 250 connections per second.If mod_caucho or isapi_srun are misconfigured, they can use too many connections and run into the TIME_WAIT limits. Using keepalives effectively avoids this problem. Since keepalive connections are reused, they won't go into the TIME_WAIT state until they're finally closed. A site can maximize the keepalives by setting thread-keepalive large and setting live-time and request-timeout to large values. thread-keepalivelimits the maximum number of keepalive connections. live-time and request-timeout will configure how long the connection will be reused.read-timeout must always be larger than client-live-time. In addition, keepalive-max should be larger than the maximum number of Apache processes.Apache 1.3 issuesUsing Apache as a web server on Unix introduces a number of issues because Apache uses a process model instead of a threading model. The Apache processes don't share the keepalive srun connections. Each process has its own connection to Resin. In contrast, IIS uses a threaded model so it can share Resin connections between the threads. The Apache process model means Apache needs more connections to Resin than a threaded model would.In other words, the keepalive and TIME_WAIT issues mentioned above are particularly important for Apache web servers. It's a good idea to use netstat to check that a loaded Apache web server isn't running out of keepalive connections and running into TIME_WAIT problems.先将resin.conf文件中的thread-min，thread-max，thread-keepalive三个参数设置的比较大，分别写上，1000，3000，1000，当然这是根据你的机器情况和可能同时访问的数量决定的，如果你的网站访问量很大的，应该再适当放大。