Allocation rate impact for garbage collected languages
plumbr.eu
plumbr.eu
The worst consequence of Java GC is that sometimes an app can lock up for a few seconds. This is not the end of the world for a desktop app or the average web app but it is a big problem if you are running a financial exchange or other critical apps.
Because of the GIL, Python (for example) doesn't get anywhere near being suitable for these kind of applications. Haskell? Common LISP? Get out of here.
In Java one can see that there are implementations trying to support soft-realtime. Also concurrent GCs on multicore machines are provided, to lessen the problem of stalls due to GC.
In the Common Lisp world the response have been sophisticated GCs or avoiding GCs. For example G2 is a tool to develop soft realtime expert systems - written in a Common Lisp implementation with lots of manual memory management. G2 is used to for process and production control applications.