The GarbageCollection (GC) is a process that requires a lot of CPU and which requires one CPU for itself if more than one is available. Thus for example, in the output of the shell command top it occupies one of the top levels.
This is the reason why a connection between the GC and performance problems is often made.
In most cases, however, this has not proven to be true.
In 90% of all cases a write-intensive user-process which triggered the GC is the actual cause for the problems, as the GC does not communicate with the database process and normally runs on its own CPU.
The write-intensive user process on the other hand communicates intensely with the database, which then influences the performance of other user processes in a negative way.
Thus, you have to analyze when this kind of performance loss occurs using top, infosystem SYSLOG (or script syslog.sh), dattop.sh as described in the chapter "Administration and Configuration" -> "Procedure if performance is bad" in the Online Help, and where it actually originated.
