4 ms·
Under the hood web.go is using the http package, so it should benefit from all the improvements, you are talking about. What I wonder more about is if the benc
by fs111 15y ago
Under the hood web.go is using the http package, so it should benefit from all the improvements, you are talking about.
What I wonder more about is if the benchmark is setting the GOMAXPROCS env variable according to the number of CPUs on his system, otherwise he has 4 cores and 3 are idling around...
- enneff 15y agoThat web.go handlers return a string severely handicaps its performance. It forces you to allocate for each http request, probably several times. For large responses this is crazy. The go http package lets you write directly to the tcp socket, and as such is capable of being way more efficient.