Skip to Content
avatar image
Former Member

Usage of Effective Old Space

Hello everybody

In a EWA of one of our ABAP+JAVA system we get this alert:

Usage of Effective Old Space

The resource utilization is critical and leaves no room to cope with sudden high-load situations.

The higher the value, the harder it is to cope with high load situations. If more than 80% of old space is used, high-load situations can lead to rapid growth phases within the old space and therefore to sudden resource outages. As a result, average values that are higher than 80% can indicate critical resource utilization.


If persistently high values of effective old-space usage are observed, related parameters (such as the old-space growth rate) should be analyzed as a preliminary measure. If growth rates are observed within the cluster-high old space, this may be due to high baseline resource utilization.

In some cases, adding additional server nodes to use the available resources more efficiently may be recommended in order to reduce the overall baseline usage. It may be advisable to enlarge the heap, depending on the type of application deployed and the operating system used. However, an increased heap size will also increase the average time required for a full garbage collection, and so any changes will have to be analyzed carefully using the parameters defined here.

Any help will be apperciate.

Best regards


Add comment
10|10000 characters needed characters exceeded

  • Get RSS Feed

2 Answers

  • avatar image
    Former Member
    Nov 17, 2010 at 03:31 AM

    Hi Ruben,

    Did you ever resolve this issue?

    We are experiencing the same messages in our EWA reports.


    Tony Lewis

    Add comment
    10|10000 characters needed characters exceeded

  • Nov 17, 2010 at 03:02 PM


    This suggest that your tenured memory is set to low. Could be that the application footprint is growing e.g. due to more users working on the system or heavier usage per user. High effective old space usage could lead to more frequent garbage collection or out of memory dumps. You could try to increase the max heap size (-Xmx), but this could also lead to longer garbage collection times. You could also try to create another server node, to load balance the work (and application footprint).

    Afterwards check with Wily Introscope the effective old space usage.



    Add comment
    10|10000 characters needed characters exceeded