Skip to Content

Java heap > 2GB (NW 7.0 64-bit): reasons for or against?

Hi Gurus -

We are upgrading to ERP 6.0 SP12.

Our portal servers are Java-only NW 7.0 SP14 (64-bit Unix Solaris 9). We have one CI and one DI, both 4-CPU, 16GB. The CI and DI both have three server nodes, each with 2G heap.

In recent load tests almost all server nodes had time-consuming full GCs with tenured objects deleted. These full GCs ran from 15 to 60 seconds). We use only standard ESS/MSS portal content. There was no indication of excessive load in the R/3 backend.

Note 723909 seems to indicate that for 64-bit you can use a heap size > 2GB, but SAP recommends additional server nodes with 2GB as a solution. I think this is because of GC performance with large heap sizes.

Is anyone out there using heap > 2GB with good results?

Are there other reasons (besides GC performance) why we should (or should not) use heap > 2GB?

Thanks in advance for your help - Jeff

Add comment
10|10000 characters needed characters exceeded

  • Get RSS Feed

1 Answer

  • Jul 07, 2008 at 08:41 PM

    OSS opened a thread for me on this question. It's getting better response than my thread 😊

    Here's the link:

    SAP Note #723909 Clarification needed: > 2G heap for server nodes

    Add comment
    10|10000 characters needed characters exceeded