0 Replies Latest reply on Nov 29, 2010 10:19 AM by Ivan Tufegdzic

    Performance leak

    Ivan Tufegdzic Newbie

      Hello,

       

      I use Jboss AS 4.2.3.GA with liferay server 5.1.2 and MS SQL Server database.

      Icefaces 1.8.2.ee is in use with Seam 2.2.0.GA.

      Server is Blade with 24GB RAM. RAM allowed for MS SQL Server is 10GB.

       

      Application very offten has performance leak. Avarage number of users by day is 200-300. I repeat that I work in portlet technology, so each portlet is separate Session (15+ icefaces portlets x 300 users; 10 liferay portlets). I we'll mention some pieces that I think they are a problem, so if anyone sees a problem I will be grateful for his response:

       

      1.Too many small classes (Seam components)

       

      2. Database Poll:

           <min-pool-size>5</min-pool-size>

           <max-pool-size>100</max-pool-size>

       

      3. Huge Import functions, that take up huge resources and MS SQL resources, so that when RAM is wasted, does not relieve dor new imports

       

      4. Export 80000+ records to XLS (with huge logic, and too often usage of Interpolator.interpolate... method)

       

      5. Creating export files into bin folder. Export to xml files (1-5000 records) and archieve them into server/bin/export folder. CAN THIS BE A PROBLEM? Maybe bin must not be filled with other files, and increase size of server folder?

       

      6. jboss-service.xml:

           <attribute name="MaximumPoolSize">500</attribute>
           <attribute name="MaximumQueueSize">10000</attribute>

      ...

           <attribute name="TransactionTimeout">36000</attribute>

      ...

           <attribute name="MaxPoolSize">30000</attribute>
           <attribute name="ClientMaxPoolSize">3000</attribute>

      ...

           <attribute name="ClientRetryCount">2</attribute>

       

      7. jboss-log4j.xml

           <category name="org.hibernate">
           <priority value="WARN" />
          </category>

       

      8. If applaction is located into server/default/deploy. Can be a problem adding some files into that war and increase size of current working war file?

           Example: application has name app.war and XLS file created by application is saved on  server/default/deploy/app.war/export/xls/