addressalign-toparrow-leftarrow-rightbackbellblockcalendarcameraccwchatcheckchevron-downchevron-leftchevron-rightchevron-small-downchevron-small-leftchevron-small-rightchevron-small-upchevron-upcircle-with-checkcircle-with-crosscircle-with-pluscrossdots-three-verticaleditemptyheartexporteye-with-lineeyefacebookfolderfullheartglobegmailgoogleimageimagesinstagramlinklocation-pinmagnifying-glassmailminusmoremuplabelShape 3 + Rectangle 1outlookpersonplusprice-ribbonImported LayersImported LayersImported Layersshieldstartickettrashtriangle-downtriangle-uptwitteruseryahoo

One million benchmark propagandas per second! By Sadek Drobi, co-creator of Play

One million benchmark propagandas per second! Your way out with Play framework.

It is certainly amusing to throw lots of requests at different servers, collect numbers, arrange them in grids and ... blog about it! It is especially easy and not time consuming. Does it solve a problem, not so sure. It is particularly ignorant to most performance challenges: what are you benchmarking in your "hello world" app? How fast a framework is at writing a sequence of characters to a socket? What happens if you have a complex database query, a long computation, or an IO call taking some time? When you have a bottleneck in your app that will only allow you dozens of requests per seconds, what do you do with other thousands of requests? the worst will be keeping them in waiting forever consuming uselessly resources like sockets and memory. Same thing applies to messages, what happens if a particular user can't receive as many messages per seconds as your app is trying to push? there is no one answer, some time buffering is good, dropping old or new messages can be a choice or even sometimes closing that particular socket.

There is no obvious solution to these problem and the best is to start with understanding your App, its bottleneck, isolate some parts and design your own app failure. And to do that, Play web framework gives you the necessary low level signals with a higher level concepts and API allowing you to take necessary decisions to optimize your app.

Sadek Drobi (@sadache) is the CTO of Zenexity and co-creator of the Play Framework.

Join or login to comment.

  • Mehboob A.

    I knew nothing about scala, and I still don't.. but I did enjoy the talk :)

    2 · June 13, 2013

  • Jonathan R.

    Good talk. Sadek is engaging and knowledgeable. The Q&A was good, too.

    1 · June 13, 2013

  • Artem Z.

    Great job. Thanks

    June 13, 2013

  • Sajit K.

    Was fantastic

    June 13, 2013

  • Mikolaj S.

    can't make it, sorry :(

    June 13, 2013

  • Rajib D.


    June 12, 2013

  • Yves J.

    I got a conflict.

    June 10, 2013

  • Hugh G.

    Has anybody heard of Hystrix?

    May 31, 2013

  • Jim P.

    Would love to, but can't.

    May 31, 2013

  • Yves J.

    I'm in

    May 31, 2013

Our Sponsors

  • Yoppworks

    Pizza and Beer

  • Spotify

    An amazing Space and fridge full of beer! Thanks Spotify!

  • Canary

    A truly amazing space! Thanks Canary!

People in this
Meetup are also in:

Sign up

Meetup members, Log in

By clicking "Sign up" or "Sign up using Facebook", you confirm that you accept our Terms of Service & Privacy Policy