Handling 1M Requests per Minute with Go

Re:Handling 1M Requests per Minute with Go by tptacek on Tuesday July 07, 2015 @12:02PM (#9846257)

It's less about Go being incredibly fast than about Ruby being anomalously slow. It makes sense if you start from the presumption that Go is the only "fast" language they're considering.

[ Parent | on HN ]

Re:Handling 1M Requests per Minute with Go by vidarh on Tuesday July 07, 2015 @03:00PM (#9847412)

Frankly, if you're going to be processing requests and shuffling them to S3, Ruby is nowhere near being the limiting factor unless you do something pathologically bad.

Having spent time recently optimizing a setup that does pretty much exactly what they're doing (in Rails; I don't like Rails, but in this case Rails is not a problem), the time saved doing things like eliminating unnecessary buffering all over the place (e.g. POSTs gets buffered by pretty much everything that likes to consider itself a web server, sometimes multiple times; if you e.g. run Nginx in front of pretty much any Ruby web servers running Rails, worst case you may end up with things passed through at least 3, possibly 4 buffers).

Basically they should be IO bound.

[ Parent | on HN ]

Re:Handling 1M Requests per Minute with Go by fixxer on Tuesday July 07, 2015 @12:08PM (#9846300)

But that would prevent the knee-jerk tribal language war response.

[ Parent | on HN ]