4 ms·
I can confirm some of the statements in that Blog as someone using both also in production. Memory footprint is a lot lower than node like 5-10x times what I've
by lossolo 10y ago
I can confirm some of the statements in that Blog as someone using both also in production. Memory footprint is a lot lower than node like 5-10x times what I've observed on similar code. Go has also very efficient GC, that can be used on large heaps with low latency.
- qaq 10y agoI think would be cool to know at least app type. For something that has a ton of ws connections node will generally have smaller memory footprint.
- lossolo 10y agoWe are using Go for a lot of internal tooling, text processing, also for websockets and web API. Can you provide some more data about memory footprint in node with websockets? How much memory per connection you saw? From my experience it's the other way around. But the most important point is that while both can have a lot of connections active, when you start sending messages thru that websocket connections you will see a LOT higher latency in node.
- qaq 10y agoafter looking at it you are right it is higher for node