Change the configuration file parameter of HTTP Server KeePalive. Cause: This value indicates whether the client is connected to the HTTP Server. If set to ON, the request will be queued when the request reaches the MaxkeepAliveRequests setting value, causing a slow response. Method: Open the IBM HTTP Server installation directory, open the folder conf, open the file httpd.conf, find the Keepalive value, change ON for OFF, whose default is ON
2. Change the HTTP Server's configuration file parameter threadsperchild value to a larger number, default is 50 reasons: server response thread Number of methods: Open the IBM HTTP Server installation directory, open the folder conf, open the file httpd.conf, find the ThreadsperChild value, The default is 50, change to a larger number, depending on how much the number of users, generally changed to 1.1 times the number of clients, such as 200 sets, set to 220
3. Turn off the HTTP Server Log Record: HTTP Server log IO affects performance method: Open the IBM HTTP Server installation directory, open the folder conf, open the file httpd.conf, find the Customlog value, find the line without comments (the beginning of the line No symbol "#"), comment with the row symbol "#" to close the log record, improve processing performance.
4. Change WebSphere's server processing thread reasons: Number of requests for thread affects the number of requests: Open the management console, open the directory tree, server -> server1-> Web container -> thread pool, modify "maximum size" Value, default is 50, change to larger numbers, specifically considering the number of users and the configuration of the machine, generally sets the value equal to or less than the MaxkeepAliveRequests set by HTTP Server.
Alternatively, make sure the database connection is turned off
