it's also a monster at processing binary data streams via pattern matching.
It all depends.
The BEAM GC each process isolately, which means that if a process die before a GC is needed, the BEAM just clean the whole process memory. No need for a GC.
That is what happens most of the time.
http://www.techempower.com/benchmarks/#section=data-r12&hw=p...
I have no idea how well the implementations are on each of these or how well each platform works within the constraints of this benchmark.
"They were testing JSON benchmarks through the :browser pipeline, complete with crsf token generation. They had a dev DB pool size of 10, where other frameworks were given of pool size of 100. And they also had heavy IO logging, where other frameworks did no logging. We sent a PR to address these issues, and I was hoping to see true results in the latest runs, but no preview was provided this time and we weren't able to work with them on the errors."