Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Handling 1M Requests per Minute with Go

marcio.io

Post reply on HN
Print view View original

21–30 of 109 posts

Re: Handling 1M Requests per Minute with Go

#21

Post by jbeja »

plydatbk wrote: post #17
Ao7bei3s wrote: post #13

Earlier quoted context omitted.

Go is 1-2 orders of magnitude faster than Ruby, and much easier to write concurrent code in. It makes perfect sense to me. What would you have recommended them, for a reasonably-high-performance server implementation? (Please don't say C.) https://benchmarksgame.alioth.debian.org/u64q/benchmark.php?...

Lua would beat go every day of the week.

As Clojure would beat Lua every second of a day.

Re: Handling 1M Requests per Minute with Go

#22

Post by zimbatm »

thwd wrote: post #3

Arguably, UploadToS3 should not be a method of *Payload. Suggestion: Make an S3-uploader package with _internal_ connection pooling, upload queueing and concurrency handling.

This. Each S3-uploader can then hold a http.Client instance that keeps the connection open to S3 between uploads.

Re: Handling 1M Requests per Minute with Go

#23

Post by mrfusion »

It's interesting this came up today. I'm looking for a new language to migrate my flask/uwsgi web service to. I'm having a terrible time making it scale.

Are there any tutorials/templates/best practices for writing a small web service in Golang?

Re: Handling 1M Requests per Minute with Go

#26

Post by plydatbk »

jbeja wrote: post #21
plydatbk wrote: post #17

Earlier quoted context omitted.

Lua would beat go every day of the week.

As Clojure would beat Lua every second of a day.

show me the clojure firewall and I'll take you seriously. Or the even something simple as an interesting clojure ML project. Java gross.

Re: Handling 1M Requests per Minute with Go

#27

Post by aikah »

ExpiredLink wrote: post #2

Go astroturfing continues ...

Would be interesting to have an app that display stats and trends about technologies hitting HN homepage. Regardless of any astro-turfing going on or other shenanigans. But it's true Go somehow gets a lot of exposure on HN, not unlike Nodejs a few years ago, or Rails before. Funny how people seem to discover hot water each time a new technology/hype hit the IT world. Soon one will read "How we went from 100000 LOC to 1000 by switching from Go to nim/crystal".

Re: Handling 1M Requests per Minute with Go

#28

Post by darksaints »

Does anybody here have any experience with Go's garbage collection pauses with large stack sizes? I've got a scala app that regularly consumes about 48G of ram, and I'm very happy with the response times during heavy loads like this, but the P99.5 is abysmal because of garbage collection. I've tried tuning it, but it doesn't seem like anything I do helps. I'll probably end up using an Azul JVM but I'm curious how other languages end up handling this problem.

Re: Handling 1M Requests per Minute with Go

#29

Post by bitcrusher »

jbeja wrote: post #21
plydatbk wrote: post #17

Earlier quoted context omitted.

Lua would beat go every day of the week.

As Clojure would beat Lua every second of a day.

If you're talking about raw performance, I'm afraid you're mistaken. If you're perhaps referring to the 'aesthetics' of the language syntax, that's pretty subjective, in which case you're right for your tastes.

Re: Handling 1M Requests per Minute with Go

#30

Post by f2f »

darksaints wrote: post #28

Does anybody here have any experience with Go's garbage collection pauses with large stack sizes? I've got a scala app that regularly consumes about 48G of ram, and I'm very happy with the response times during heavy loads like this, but the P99.5 is abysmal because of garbage collection. I've tried tuning it, but it doesn't seem like anything I do helps. I'll probably end up using an Azul JVM but I'm curious how oth…

this article discusses how they handled 69GB of heap and up to 6 seconds of pause times:

http://blog.golang.org/qihoo

the new garbage collector in 1.5 should improve things.

Post reply on HN