This site uses cookies to improve your experience. To help us insure we adhere to various privacy regulations, please select your country/region of residence. If you do not select a country, we will assume you are from the United States. Select your Cookie Settings or view our Privacy Policy and Terms of Use.
Cookie Settings
Cookies and similar technologies are used on this website for proper function of the website, for tracking performance analytics and for marketing purposes. We and some of our third-party providers may use cookie data for various purposes. Please review the cookie settings below and choose your preference.
Used for the proper function of the website
Used for monitoring website traffic and interactions
Cookie Settings
Cookies and similar technologies are used on this website for proper function of the website, for tracking performance analytics and for marketing purposes. We and some of our third-party providers may use cookie data for various purposes. Please review the cookie settings below and choose your preference.
Strictly Necessary: Used for the proper function of the website
Performance/Analytics: Used for monitoring website traffic and interactions
On Tuesday of this week, we kicked off a pair of EC2 instances and a pair of our i7 workstations to produce updated data. We dive right in with the EC2 JSON test results, but please read to the end where we include important notes about what has changed since last week. First up is data from the EC2 m1.large large instances.
This is an EC2 test run on a pair of Large instances. Netty , Vert.x , and Java servlets are fast, but we were surprised how much faster they are than Ruby , Django , and friends. And let us simply draw the curtain of charity over the Cake PHP results. We ran each test on EC2 and our i7 hardware. Starting again with EC2.
This is an EC2 test run on a pair of Large instances. Netty , Vert.x , and Java servlets are fast, but we were surprised how much faster they are than Ruby , Django , and friends. And let us simply draw the curtain of charity over the Cake PHP results. We ran each test on EC2 and our i7 hardware. Starting again with EC2.
This round adds Bottle (Python), Dancer (Perl), Kelp (Perl), MicroMVC (PHP), Mojolicious (Perl), Phalcon (PHP), RingoJS (JavaScript), Spark (Java), and Wai (Haskell). As with previous rounds, the developer community has contributed several additional frameworks for Round 4, bringing the total to 57!
Round 3 includes Snap on Haskell; Elli and Cowboy on Erlang; Openresty on Lua; Tornado on Python; Onion on C; Slim, Codeigniter, Phreeze, Kohana, Lithium, Laravel, Silex, Fuel, and Symphony2 on PHP; Grizzly-Jersey and Play1 on Java; Scalatra, Lift, Unfiltered, and Finagle on Scala. Openresty takes the lead for multiple queries on EC2.
Furthermore, due to the modestly rushed nature (at least on our side) of Round 12, we elected to not capture Amazon EC2 results for this Round. The plain PHP, Slim, and Laravel tests have been upgraded to PHP 7. All JVM-hosted tests have been upgraded to Java 8. View the full results of Round 12. Other notable changes.
And I hope you are not running on Cake PHP when you see these numbers. In looking at these numbers, seeing Cake PHP at 500x slower, Ruby-Rails and Django at 50x slower really surprised me. I was also surprised by the performance improvement on dedicated hardware as compared to EC2 instances of roughly 10x.
We organize all of the trending information in your field so you don't have to. Join 5,000+ users and stay up to date on the latest articles your peers are reading.
You know about us, now we want to get to know you!
Let's personalize your content
Let's get even more personalized
We recognize your account from another site in our network, please click 'Send Email' below to continue with verifying your account and setting a password.
Let's personalize your content