New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Hapi not under the first ten #1326

Closed
DrMabuse23 opened this Issue Jan 14, 2014 · 5 comments

Comments

Projects
None yet
3 participants
@DrMabuse23

DrMabuse23 commented Jan 14, 2014

@hueniverse

This comment has been minimized.

Show comment
Hide comment
@hueniverse

hueniverse Jan 14, 2014

Member

@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.
Member

hueniverse commented Jan 14, 2014

@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 hueniverse closed this Jan 14, 2014

@poeticninja

This comment has been minimized.

Show comment
Hide comment
@poeticninja

poeticninja commented Jan 14, 2014

@DrMabuse23

This comment has been minimized.

Show comment
Hide comment
@DrMabuse23

DrMabuse23 Jan 14, 2014

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

DrMabuse23 commented Jan 14, 2014

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

@DrMabuse23

This comment has been minimized.

Show comment
Hide comment
@DrMabuse23

DrMabuse23 Jan 14, 2014

I just hope you do not take it personally

DrMabuse23 commented Jan 14, 2014

I just hope you do not take it personally

@hueniverse

This comment has been minimized.

Show comment
Hide comment
@hueniverse

hueniverse Jan 15, 2014

Member

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

Member

hueniverse commented Jan 15, 2014

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

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment