3 Replies Latest reply on Dec 15, 2010 10:55 AM by peterj

    Recommendation Setting for JBoss web

    a-koptan

      Hello all,
      I have a small question regarding the proper environment and settings to run an application on the Web Jibus.
      Note that the average number of users from 500 to 1000 , and the database is Oracle.
      thanks,

      Hello all,


      I have a small question regarding the proper environment and settings to run an application on the JBoss web.


      Note that the average number of users from 500 to 1000 , and the database is Oracle.


      thanks,

        • 1. Re: Recommendation Setting for JBoss web
          peterj

          And what is your question? Are you asking about JVM settings? About how to deploy a WAR? About how to define a datasource in a *-ds.xml file? About looking up the datasource JNDI name?

          • 2. Re: Recommendation Setting for JBoss web
            a-koptan

            hi Peter ,

             

            My question is :

            what is the best Environment to run my Application,
            what is the best Environment to run my application  in production use,

             

            i mean the best from Hardware,OS, JVM settings ,and JBoss web server settings.

             

             

             

             

            i mean the best from Hardware,OS,and JBoss web server setting .

            • 3. Re: Recommendation Setting for JBoss web
              peterj

              I assume that when you say 500 to 1000 users that you mean that is the total number of users on the app, which equates to about 5 to 10 requests per second.

               

              Hardware: 2 CPUs should be fine, 2GB RAM should be sufficient.

              OS: Either Linux or Windows, 32-bit (note that you must run one of the Server version of Windows and those are expensive, save some money and run Linux)

              JVM settings: leave at the defaults (though set -Xms to 512m to match -Xmx)

              Web server settings: leave at the defaults

               

              The above recommendations are based on the assumption that your web application is a typical web application that responds to most requests within 100ms-200ms and to all requests in less than a second. If your web app does not fit that description (for example, it spends several seconds processing large amounts of data before replying to a request) then the recommendations do not apply.