Handling 1M Requests per Minute with Go (2015)

#1

Post by rcarmo » Mon, Jan 15, 2018, 1:28 PM UTC

Handling 1M Requests per Minute with Go (2015)
marcio.io

Re: Handling 1M Requests per Minute with Go (2015)

#2

Post by qaq » Mon, Jan 15, 2018, 2:16 PM UTC

Since when did per minute become a thing? 16K/sec is typical for a node app on fairly avg server.

Re: Handling 1M Requests per Minute with Go (2015)

#3

Post by kasey_junk » Mon, Jan 15, 2018, 2:19 PM UTC

qaq wrote: post #2

Since when did per minute become a thing? 16K/sec is typical for a node app on fairly avg server.

It’s not a thing and it’s fairly trivial to get to that load on a typical go app as well.

Re: Handling 1M Requests per Minute with Go (2015)

#4

Post by qaq » Mon, Jan 15, 2018, 2:24 PM UTC

kasey_junk wrote: post #3

qaq wrote: post #2

Since when did per minute become a thing? 16K/sec is typical for a node app on fairly avg server.

It’s not a thing and it’s fairly trivial to get to that load on a typical go app as well.

I am sure Go can do at the very least 2x-3x vs node for the same workload.

Re: Handling 1M Requests per Minute with Go (2015)

#5

Post by fastest963 » Mon, Jan 15, 2018, 2:27 PM UTC

Why didn't he keep the first single-channel solution and just listen on the channel from multiple go routines? I don't see the advantage that a tiered approach gets you over that.

Re: Handling 1M Requests per Minute with Go (2015)

#6

Post by gazarullz » Mon, Jan 15, 2018, 2:29 PM UTC

qaq wrote: post #4

kasey_junk wrote: post #3

Earlier quoted context omitted.

It’s not a thing and it’s fairly trivial to get to that load on a typical go app as well.

I am sure Go can do at the very least 2x-3x vs node for the same workload.

Since you are sure, do you have any examples or proof to back that ?

Re: Handling 1M Requests per Minute with Go (2015)

#7

Post by mbrumlow » Mon, Jan 15, 2018, 2:32 PM UTC

Seems like they just had a misunderstanding of how range worked. And now they have complicated code.

Re: Handling 1M Requests per Minute with Go (2015)

#8

Post by qaq » Mon, Jan 15, 2018, 2:38 PM UTC

gazarullz wrote: post #6

qaq wrote: post #4

Earlier quoted context omitted.

I am sure Go can do at the very least 2x-3x vs node for the same workload.

Since you are sure, do you have any examples or proof to back that ?

A random result from Google http://blog.digg.com/post/141552444676/making-the-switch-fro.... My day job is writing large scale node services that service over million concur. clients doing fairly intensive data acquisition/processing so I am not hating on Node :)

Re: Handling 1M Requests per Minute with Go (2015)

#9

Post by segmondy » Mon, Jan 15, 2018, 2:46 PM UTC

qaq wrote: post #2

Since when did per minute become a thing? 16K/sec is typical for a node app on fairly avg server.

A million sounds nice.

Re: Handling 1M Requests per Minute with Go (2015)

#10

Post by gazarullz » Mon, Jan 15, 2018, 2:48 PM UTC

qaq wrote: post #8

gazarullz wrote: post #6

Earlier quoted context omitted.

Since you are sure, do you have any examples or proof to back that ?

A random result from Google http://blog.digg.com/post/141552444676/making-the-switch-fro... . My day job is writing large scale node services that service over million concur. clients doing fairly intensive data acquisition/processing so I am not hating on Node :)

Don't get me wrong, I don't intend to mock your statement in any way but a statement backed by some data and/or actual examples adds a lot of credibility to it.