This subsection describes points to be considered when using the functionality for controlling object movement to the Explicit memory block and functionality for specifying classes to be excluded from the application of the Explicit Memory Management functionality, which are used for reducing the time required for automatic release processing.

• The functionality for controlling object movement in an Explicit memory block does not let move the objects of the Java heap, which are referenced from objects in an Explicit memory block created by using automatic placement functionality, to an Explicit heap when a full garbage collection occurs. If you enable this functionality, occurrence frequency of a full garbage collection might increase on systems in which a full garbage collection has occurred earlier. If occurrence frequency of full garbage collections creates a problem in the system, once again tune the memory size of the area used by JavaVM. For details on memory tuning, see 7. Memory tuning of JavaVM in the uCosminexus Application Server System Design Guide.
• The functionality for specifying classes to be excluded from the application of the Explicit Memory Management functionality does not let move objects of the classes specified in the configuration file, from among the objects of the Java heap referenced from objects in Explicit memory blocks, which are created by using automatic placement functionality, to Explicit heap. If you enable this functionality, because the objects that were moved to the Explicit heap move to Tenured area, the usage of Tenured area increases. Hence, occurrence frequency of full garbage collections might increase. If occurrence frequency of full garbage collections creates a problem in the system, once again tune the memory size of the area used by JavaVM. For details on memory tuning, see 7. Memory tuning of JavaVM in the uCosminexus Application Server System Design Guide.
• The functionality for specifying classes to be excluded from the application of the Explicit Memory Management functionality reads the configuration file when starting the J2EE server or the batch server. As a result, if you specify many classes in the configuration file, starting of the J2EE server or the batch server might take longer time. Compare the start time of the J2EE server or the batch server, and automatic release processing time, and review the use of this functionality.
• The functionality for specifying classes to be excluded from the application of the Explicit Memory Management functionality determines whether a class is excluded from the application of the Explicit Memory Management functionality, when loading the class. As a result, if you specify many classes in a configuration file, class loading time might increase.
• The functionality for specifying classes to be excluded from the application of the Explicit Memory Management functionality excludes objects of the classes specified in the configuration file from the target of the Explicit Memory Management functionality. As a result, if you specify class of an object, which is effective if placed in Explicit heap, in the configuration file, you might not achieve the effect of a full garbage collection inhibition.
• Because the functionality for specifying classes to be excluded from the application of the Explicit Memory Management functionality does not execute 8.6.5 Moving the objects from the Java heap to the Explicit memory block based on a reference relation, consider the objects as excluded from the application of the Explicit Memory Management functionality. As a result, if you specify direct generation of an object in an application, the object is generated in Explicit memory block even if you specify class of that object in the classes to be excluded from the application of the Explicit Memory Management functionality. For details on direct generation of objects in an application, see 8.6.3 Directly generating objects in Explicit memory block.
  If you specify the objects stored in an HTTP session in the classes to be excluded from the application of the Explicit Memory Management functionality, the objects are excluded from the application of the Explicit Memory Management functionality and they do not move to the Explicit memory block. For details on the objects stored in an HTTP session, see 8.4.1 Objects related to HTTP session.
  
• You cannot execute a full garbage collection or automatic release processing while inhibiting full garbage collection when debugging an application. Because you cannot obtain the object release rate information even if you execute eheapprof command by specifying -freeratio option while inhibiting garbage collection, only the object statistics in Explicit memory block is output to Explicit heap details of thread dump and the object release rate information is not output.