{"id":1185,"date":"2013-01-25T10:47:18","date_gmt":"2013-01-25T02:47:18","guid":{"rendered":"http:\/\/www.strongd.net\/?p=1185"},"modified":"2013-06-18T17:08:36","modified_gmt":"2013-06-18T09:08:36","slug":"nginx-1-2-0-versus-resin-4-0-29-performance-tests","status":"publish","type":"post","link":"https:\/\/www.strongd.net\/?p=1185","title":{"rendered":"NginX 1.2.0 versus Resin 4.0.29 performance tests"},"content":{"rendered":"

Recently, we decided to spend some extra time improving Resin’s performance and scalability. Since we like challenges, we set a goal of meeting or beating nginx, a fast C-based web server. When working on performance, we use benchmarks to see which proposed changes improve Resin’s performance, and which proposed changes do not. The autobench\/httperf benchmark is particularly interesting because it simulates high load rates and exposes scalability issues better than some other benchmarks like ab. After completing the Resin performance work, it turned out that we exceeded our goal and were actually able to beat nginx, and thought we’d share our results.<\/p>\n

We have recently run some performance benchmarks comparing Resin 4.0.29 versus NginX 1.2.0. These benchmarks show that Resin Pro matches or exceeds NginX’s throughput.<\/p>\n

We tested 0k (empty HTML page), 1K, 8K and 64K byte files. At every level Resin matched or exceeded NginX performance.<\/p>\n

 <\/p>\n

 <\/p>\n

\n\n\n\n
\n
\n

Contents<\/h2>\n<\/div>\n