That was my fault too. encoding/json is slow, but not that slow. Unfortunately the title of this thread is a bit misleading. Apparently what is taking time here is reading the data off the wire, rather than decoding the data once it has arrived.
So it seems that that the slowness is probably nothing to do with json decoding and nothing to do with Go. Sarath says that a Ruby implementation is fast. So I would get tcpdump traces for both, and walk your way through the relevant sessions, and see what the differences are. On Saturday, 2 May 2020 03:54:47 UTC+1, Jason E. Aten wrote: > > you could try ffjson https://github.com/pquerna/ffjson > > > -- You received this message because you are subscribed to the Google Groups "golang-nuts" group. To unsubscribe from this group and stop receiving emails from it, send an email to golang-nuts+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/golang-nuts/0b481259-43d1-4140-a206-9b747809b311%40googlegroups.com.
