An very large pool wastes memory and can slow down the system. Set this property to be representative of the anticipated high load of the system. The corresponding EJB deployment descriptor attribute is max-pool-size. The potential implication is that the JVM heap will be filled with objects in the pool. A value of zero means that the size of the pool is unbounded. Valid values are from zero to MAX_INTEGER., and the default is 32. Maximum Pool Size: the maximum number of connections that can be created to satisfy client requests. Having a value greater than zero ensures that there is always a pooled instance to process an incoming request. Set this property to a number greater than zero for a moderately loaded system. The corresponding EJB deployment descriptor attribute is steady-pool-size. Valid values are from 0 to MAX_INTEGER, and the default value is 8. Initial and Minimum Pool Size: the initial and minimum number of beans maintained in the pool. So, to avoid data inconsistencies, take into the account the expected behavior of the application when adjusting the reap interval.Īn individual EJB component can specify cache settings that override those of the EJB container in the element of the EJB component's sun-ejb-jar.xml deployment descriptor. The client clicks again expecting to see $11 but instead sees is $9, which is incorrect. As a result, the latest value recorded at the 60 second interval ($8) is be loaded into the session. The value the client sees is $10.ĭuring the client's 20 second rest, the GlassFish Server stops and starts in 10 seconds. But if a client accesses a servlet to update a value at 20 second increments, then inconsistencies will result.įor example, consider the following online auction scenario:īidding starts at $5, in 60 seconds the value recorded will be $8 (three 20 second intervals).ĭuring the next 40 seconds, the client starts incrementing the price. Modifying the reap interval can improve performance, but setting it without considering the nature of your sessions and business logic can cause data inconsistency, especially for time-based persistence-frequency.įor example, if you set the reap interval to 60 seconds, the value of session data will be recorded every 60 seconds. To find additional Performance Tuning development information, see the Performance Tuner in Oracle GlassFish Server 3.1 blog. To view a demonstration video showing how to use the GlassFish Server Performance Tuner, see the Oracle GlassFish Server 3.1 - Performance Tuner demo. You may also want to refer to the following resources for additional information: Note that no dynamic inspection of the system is performed.įor complete information about using the Performance Tuning features available through the GlassFish Server Administration Console, refer to the Administration Console online help. The Tuner performs a static analysis of GlassFish Server resources and throughput requirements. You can configure performance tuning for the entire domain, or for individual GlassFish Server instances or clusters. It helps you reach an optimal configuration, although finer tuning might be needed in case of specific requirements. The Performance Tuner recommends server settings to suit the needs of your GlassFish Server deployment. These changes can be made manually, as described in this chapter, or by using the built-in Performance Tuner in the GlassFish Server Administration Console. You can significantly improve the performance of GlassFish Server and the applications deployed on it by adjusting a few deployment and server configuration settings. Using the GlassFish Server Performance Tuner For complete information about using the GlassFish Server command-line interface, refer to the other titles in the GlassFish Server documentation set at. For complete information about using the Administration Console, refer to the Administration Console online help. Note that while this chapter describes numerous interactions with both the GlassFish Server Administration Console and the command-line interface, it is not intended to provide exhaustive descriptions of either. This chapter describes some ways to tune your GlassFish Server installation for optimum performance.
0 Comments
Leave a Reply. |