"No one is harder on a talented person than the person themselves" - Linda Wilkinson ; "Trust your guts and don't follow the herd" ; "Validate direction not destination" ;

May 21, 2014

Learnings in performance testing (JBOSS Tuning, Windows TCP / IP Changes)

Tuning JBOSS performance by increasing the RAM, number of max threads to be used, increasing TCP / IP Connections limit. Below are good references for the same
JBOSS parameters tweaked


The -Xms value is the space in memory that is committed to the VM at init. The JVM can grow to the size of –Xmx


The -Xmx value determines the size of the heap to reserve at JVM initialization

..\deploy\jboss-web.deployer\server.xml -> "<Connector>" tag
The maximum number of request processing threads to be created by this Connector, which therefore determines the maximum number of simultaneous requests that can be handled. If not specified, this attribute is set to 200.
The maximum queue length for incoming connection requests when all possible request processing threads are in use
The number of milliseconds this Connector will wait, after accepting a connection, for the request URI line to be presented
..\conf\jboss-service.xml -> "org.jboss.util.threadpool.BasicThreadPool"
How long a thread will live without any tasks in milliseconds
The max number of threads in the pool
The max number of tasks before the queue is full
..\conf\jboss-service.xml -> "org.jboss.remoting.transport.Connector"
The number of threads that exist for accepting client connections
The number of server threads for processing client
Client side maximum number of active socket connections. This basically equates to the maximum number of concurrent client calls that can be made from the socket client invoker

More Reads

Big List Of 20 Common Bottlenecks

Happy Learning!!!

No comments: