3 ms·
I take it you didn't switch the graphs to the latency view.
by thrownaway2424 14y ago
I take it you didn't switch the graphs to the latency view.
- DennisP 14y agoBecause of your comment I checked the latency view and found Go doing quite well, sometimes in the second or third spot. Perhaps I'm missing your point?
- thrownaway2424 14y agoWell, in the database access test with multiple queries, Go has an outrageous max latency of 19 seconds, and a stddev of 3x the mean, which is terrible.
- JulienSchmidt 14y agoThis is probably caused by running all the queries in their own goroutine (if you don't know what this is just think of it as a thread - but much cheaper). This causes the queries to be handled in more or less random order. We'll fix this for Round 5 ;-)
- thrownaway2424 14y agoYou think so? I think it is probably cases by Go's single threaded stop the world garbage collector.
- DennisP 14y agoGuess we'll find out in Round 5!