Hapi: Hapi not under the first ten

Created on 14 Jan 2014  路  5Comments  路  Source: hapijs/hapi

Most helpful comment

@brewing please don't take this personally. I just get this question a lot and I'm taking my frustration out on your issue. This is not aimed at you.

Fuck that!

I need to write a proper blog post about this but here is my short answer: no.

That would be a huge waste of time. Those benchmarks are idiotic, pointless, and miss the entire point of benchmarking which is to identify bottlenecks and optimize those. I'll also offer you these two points:

  1. You can't expect a framework that provides so much functionality out of the box to compete with frameworks that provide nothing. You need to load up express with 20+ middleware modules to get close. And removing hapi features is a no-go. Don't you want protection against out of memory? What about event queue delay? What about client request timeout? Server response timeout? Protection against aborted requests? Built-in request lifecycle logging? Which one of these is optional?
  2. Hapi was able to handle all of Walmart mobile Black Friday traffic with about 10 CPU cores and 28Gb RAM (of course we used more but they were sitting idle at 0.75% load most of the time). This is mind blowing traffic going through VERY little resources. Why on earth would I spend engineering resources making it look good on some pointless benchmark when reality is clearly saying it is doing just fine.

All 5 comments

@brewing please don't take this personally. I just get this question a lot and I'm taking my frustration out on your issue. This is not aimed at you.

Fuck that!

I need to write a proper blog post about this but here is my short answer: no.

That would be a huge waste of time. Those benchmarks are idiotic, pointless, and miss the entire point of benchmarking which is to identify bottlenecks and optimize those. I'll also offer you these two points:

  1. You can't expect a framework that provides so much functionality out of the box to compete with frameworks that provide nothing. You need to load up express with 20+ middleware modules to get close. And removing hapi features is a no-go. Don't you want protection against out of memory? What about event queue delay? What about client request timeout? Server response timeout? Protection against aborted requests? Built-in request lifecycle logging? Which one of these is optional?
  2. Hapi was able to handle all of Walmart mobile Black Friday traffic with about 10 CPU cores and 28Gb RAM (of course we used more but they were sitting idle at 0.75% load most of the time). This is mind blowing traffic going through VERY little resources. Why on earth would I spend engineering resources making it look good on some pointless benchmark when reality is clearly saying it is doing just fine.

@hueniverse :+1:

@hueniverse please don't take this personally === no ( i wanna make a joke ) i like Hapi really .

I just hope you do not take it personally

@brewing I didn't. You shouldn't either ;-)

Was this page helpful?
0 / 5 - 0 ratings

Related issues

foobar1123 picture foobar1123  路  3Comments

RohovDmytro picture RohovDmytro  路  4Comments

mahnunchik picture mahnunchik  路  4Comments

arb picture arb  路  4Comments

jney picture jney  路  4Comments