JavaServerFaces (JSF) excessive heap new generation objects
Observing 10s - 100s MB of Java heap growth on 10s - 100s KB JSF pages. Observeing > 100:1 ratio (heap growth / page response).
Creation or growing many Collections and/or the underlying arrays without knowing the necessary final size can generate excessive garbage. This is not to say that this is in any way expensive. In fact, quite to the contrary, testing has proven that this type of garbage is often quite cheaply created and reclaimed. However, if many or large objects of this type live beyond a young generation GC cycle, they might very well spill into the tenured generation. If this occurs often enough, they will adversely affect full GC (stop-the-world) time.
Creation or growing many Collections and/or the underlying arrays without knowing the necessary final size can generate excessive garbage. This is not to say that this is in any way expensive. In fact, quite to the contrary, testing has proven that this type of garbage is often quite cheaply created and reclaimed. However, if many or large objects of this type live beyond a young generation GC cycle, they might very well spill into the tenured generation. If this occurs often enough, they will adversely affect full GC (stop-the-world) time.
Comments