How many requests can jboss handle

That sounds amazing If we need static content plus dynamic content, we'll use different machines right away But I think as we control the client and as we expect heavy heavy loads, it'll be better to just go directly with Jetty or Tomcat and let those only do what they do best: dynamic content.

For the static stuff probably only media, e. If you pull down Jetty The 1. JBoss builds with the 1. Substituting the jar in This is very cool! I've played around with the most current version of jetty was 4. My "LoadTester" opens Threads and each tries to open a connection and perform one stream.

Very cool! From my first impression, Jetty looks very very cool! Home Content Places Search Cancel. Error: You don't have JavaScript enabled. This tool uses JavaScript and much of it will not work correctly without it enabled. Please turn JavaScript back on and reload this page. Please enter a title. You can not post a blank message. Please type your message and try again. Ideally only 1 thread in the IO pool and it must never execute blocking network or file processing. The other group is generally called "Worker Task Threads" group.

Which is dedicated to executing blocking work. One of the settings of this second group will be "Task max threads" size. Sign up to join this community. The best answers are voted up and rise to the top.

Stack Overflow for Teams — Collaborate and share knowledge with a private group. Create a free Team What is Teams? Learn more. Asked 1 year, 9 months ago. Active 1 year, 5 months ago.

Viewed 3k times. I am asking here because I cannot find much information on this I have tried setting "Task max threads" to , and even , and it seems to slow down my site. Anyone can explain how these 2 settings work? Improve this question. Add a comment. Active Oldest Votes. Improve this answer. So if the site needs to support concurrent users, does that mean we should set the "task max threads" to ?

I have tried that, but all it does is slow down all the page requests during high load. So by IO, i assume it means file access? So if my apps does not read and write from files, i can just keep that as default?

To avoid this, set the max-active-sessions number accordingly in the jboss-web. Continuous monitoring is necessary to ensure that there are no bottlenecks in web request handling — either due to insufficient worker threads or due to a low max sessions limit. A poorly configured pool of EJBs could be even detrimental in terms of performance, and hence, setting the correct configuration for the EJB cache is important.

Monitoring of connection pool usage is important to ensure that there are sufficient connections available in the pool to handle the workload being handled by the Wildfly server. Other optimizations: There are several other optimizations that can be performed depending on whether Tomcat or Undertow is the servlet engine used. We have discussed several optimizations for Tomcat in an earlier blog.

For Undertow: Consider tuning the buffer cache. Having an optimized buffer cache for your servlet container can improve Undertow performance for serving static files. JSP Compilation optimizations : There are JSP configuration options for Undertow servlet containers that provide optimizations for how JSP pages are compiled into Java bytecode: generate-strings-as-char-arrays: If your JSPs contain a lot of Stringconstants, enabling this option optimizes scriplets by converting the String constants to char optimize-scriptlets: If your JSPs contain many Stringconcatenations, enabling this option optimizes scriplets by removing String concatenation for every JSP request.

Tuning Listeners : Depending on your applications and environment, you can configure multiple listeners specific to certain types of traffic. Some performance-related options for listeners include:. This is the maximum number of concurrent connections that the listener can handle. By default, this attribute is undefined, which results in unlimited connections. You can use this option to set a ceiling on the number of connections a listener can handle, which might be useful to cap resource usage.

While configuring this value, you should consider your workload and traffic type. This is the length of time in milliseconds that a connection is idle before it is closed. The default value is milliseconds 1 minute.

Tuning this option in your environment for optimal connection efficiency can help improve network performance.