If your programs allocate many small, short lived objects, the heap could be filling and triggering GC too regularly. Try increasing the initial and maximum heap sizes as per 5.5 How do I increase the runtimes initial and maximum heap size?
• RE – array accesses. We have sub-optimal runtime checking code, and the compiler is still not so smart about automatically removing array checks. If your code is ready, and it doesn’t rely on them, try compiling with –no-bounds-check. • Try static linking. On many platforms, dynamic (PIC) function calls are more expensive than static ones. In particular, the interaction with boehm-gc seems to incur extra overhead when shared libraries are used. • If your Java application doesn’t need threads, try building libgcj using –enable-threads=none. Portions of the libgcj runtime are still more efficient when single-threaded.
Related Questions
- If your programs allocate many small, short lived objects, the heap could be filling and triggering GC too regularly. Try increasing the initial and maximum heap sizes as per 5.5 How do I increase the runtimes initial and maximum heap size?
- Why is commercial demonstration of CLP limited to relatively short (less than 100 miles) and relatively small (less than 5 million tons per year) projects?
- Is the master teacher function required in districts with targeted programs and a small universe? If so, how can it be fulfilled?
