undefined | Better HN

0 pointsbilbo0s13y ago0 comments

I'm not sure many people would use webgo in real life. I don't know... maybe some people... certainly not pros.

Also, the 1.0.3 thing is probably dragging on the numbers a bit. 1.1 would boost it a little. Not enough to get it into the top tier... but a little.

Also, for Vert.x, they seem to be only running one verticle. Which would never happen in real life.

Play could be optimized a bit... but not much. What they have is, to my mind, a fair ranking for it.

Small issues with a few of the others but nothing major. I think Go and Vert.x are the ones that would get the biggest jumps if experts looked at them. And let's be frank... does Vert.x really need a jump?

So what they have here is pretty accurate... I mean... just based on looking through the code. But Go might fare better if it used tip. And Vert.x would DEFINITELY fair better with proper worker-nonworker verticles running.

0 comments

10 comments · 5 top-level

smandou13y ago· 2 in thread

The Play app uses MySql in a blocking way, while Nodejs uses mongo. It's not comparable.

bhauer13y ago

We have a pull request that changes the Play benchmark (thank you!) so we will be including that in a follow-up soon.

We tested node.js with both Mongo and MySQL. Mongo strikes us the more canonical data-store for node, but wanted to include the MySQL test out of curiosity.

nobleach13y ago

That is bad benchmarking!

jholla1413y ago· 1 in thread

The Play example was totally unfair since it blocks on the database query which will block the underlying event loop and really lower the overall throughput.

bilbo0sOP13y ago

Well... to be fair...

the Vert.x example, as configured, blocks massively as well waiting for mongodb queries.

goodwink13y ago· 1 in thread

Could you point me at an example of an idiomatic, non-trivial Go REST/JSON API server? I've been trying for a while to find something to read to get a better handle on good patterns and idiomatic Go, but I haven't really come up with anything. I've found some very good examples of much lower-level type stuff, but I think I have a decent handle on that type of Go already. What I really would like is a good example of how people are using the higher level parts of the standard library, particularly net/http etc.

bilbo0sOP13y ago

Sorry... I'm not really a book kind of guy when it comes to this stuff. The golang resources are mostly what I use.

pfalls13y ago· 1 in thread

for Vert.x, we specified the number of verticals in App.groovy, rather than on the command line, which we think is a valid way to specify it.

bilbo0sOP13y ago

OK... I ran the Vert.x test... runs a bit faster here with 4 workers instead of 8. I suspect what is happening there is that at times all 8 cores can be pinned by workers, while responses wait to be sent back on the 8 non workers. But not that big a change in speed actually. One thing more, when you swap in a couchbase persister for the mongo persister it's faster yet. The difference is actually much larger than the difference you get balancing the number of worker vs non worker verticles. Also thinking that swapping gson in for jackson would improve things... but I don't think that those are fair changes. (well... the couchbase may be a fair change)

Also tested Cake just because it had been a while since I have used it... and I couldn't believe it was that much worse than PHP. Your numbers there seem valid though given my test results. That's pretty sad.

Finally, tried to get in a test of your Go stuff. I'm making what I think are some fair changes ... but it did not speed up as much as I thought. In fact, initially it was slower than your test with 1.1.

So after further review... well done sir.

commentzorro13y ago

That first line is truly one of the best comments I've seen when discussing languages. I've clipped it and will use it from now on:

>> I'm not sure many people would use [xxx] in real life. I don't know... maybe some people... certainly not pros.

j / k navigate · click thread line to collapse

0 comments

10 comments · 5 top-level

smandou13y ago· 2 in thread

The Play app uses MySql in a blocking way, while Nodejs uses mongo. It's not comparable.

bhauer13y ago

We have a pull request that changes the Play benchmark (thank you!) so we will be including that in a follow-up soon.

We tested node.js with both Mongo and MySQL. Mongo strikes us the more canonical data-store for node, but wanted to include the MySQL test out of curiosity.

nobleach13y ago

That is bad benchmarking!

jholla1413y ago· 1 in thread

The Play example was totally unfair since it blocks on the database query which will block the underlying event loop and really lower the overall throughput.

bilbo0sOP13y ago

Well... to be fair...

the Vert.x example, as configured, blocks massively as well waiting for mongodb queries.

goodwink13y ago· 1 in thread

bilbo0sOP13y ago

Sorry... I'm not really a book kind of guy when it comes to this stuff. The golang resources are mostly what I use.

pfalls13y ago· 1 in thread

for Vert.x, we specified the number of verticals in App.groovy, rather than on the command line, which we think is a valid way to specify it.

bilbo0sOP13y ago

So after further review... well done sir.

commentzorro13y ago

That first line is truly one of the best comments I've seen when discussing languages. I've clipped it and will use it from now on:

>> I'm not sure many people would use [xxx] in real life. I don't know... maybe some people... certainly not pros.

j / k navigate · click thread line to collapse