4 ms·
The majority of it is written in Go. Not a good or a bad thing per se, just some info I looked up.
by makapuf 5y ago
The majority of it is written in Go. Not a good or a bad thing per se, just some info I looked up.
- secondcoming 5y agoSeems an add choice of language. Wouldn't GC drop calls?
- iSloth 5y agoWhy would GC drop calls? I know a few high volume networks using .Net based platforms without any issues, Go would run circles around them performance wise.
- withinboredom 5y ago.NET GC is pretty configurable though. I don’t know about the Go one.
- electroly 5y ago.NET's GC is faster than Go's GC. They had a big head start.
- Cthulhu_ 5y agoWhy would it? It feels like you're making assumptions about a lot of things.
- secondcoming 5y agoLast I remember, mobile signalling had quite strict timing requirements.
- wyldfire 5y agoYes, both unbound heap allocation times and GC pauses could stall and cause critical timing failures. But you could theoretically use these features in a system designed for low latencies.
- TobTobXX 5y agoGo is known to be quite usable a server programming language (Caddy is a well-known HTTP server written in Go), so I think the language choice is quite fit. You wouldn't say a HTTP server drops requests because it has GC / uses Go, so why would it drop calls?
- DaniloDias 5y ago
- DarylZero 5y agoGo's GC supposedly never runs longer than 1ms, so no.