Node.js Versus Nginx: Bare Bones Test

Published on Dec 4, 2012 by Jamie Munro

This is a quick follow up to yesterday’s post on Node.js Versus Apache2: Bare Bones Test where I performed a straight HTML test of Node.js versus Apache.  With my recent switch to Nginx, I thought it prudent to perform this exact same test swapping out Apache for Nginx.  The results are much more interesting to yesterday’s since there is no total destruction (sorry for the spoiler if you didn’t read yesterday’s article).

Read more >

Tags: Optimization | speed comparison | nginx | Theory | JavaScript | node | apache

Node.js Versus Apache2: Bare Bones Test

Published on Dec 3, 2012 by Jamie Munro

I've written a few recent articles on Node.js, mostly to familiarize myself with the effort involved in creating basic applications with it.  I have yet to use it in production, mostly because I’m just not sure how ready I am to use it on a large project…

I have been quite curious with performance compared to the standard tools that I've used forever and ever.  In the following article, I’m going to do some basic comparisons between Node and Apache2 performance.

Read more >

Tags: Optimization | speed comparison | Theory | JavaScript | node | apache

PHP: Single Quotes versus Double Quotes

Published on Oct 9, 2012 by Jamie Munro

I always enjoy doing interviews and asking potential candidates what the difference between single quotes and double quotes are in PHP.  Most people have the basic understanding that single quotes are not interpreted by the compiler whereas double quotes are processed while the page is being executed.  The follow up question is typically which one they prefer; this answer is always 50/50.  I have always been a fan of single quotes thinking them to be faster…

Read more >

Tags: Optimization | php | speed comparison | Theory | PHP | quotes

A Simple But Effective Speed Comparison

Published on Sep 4, 2012 by Jamie Munro

A little while ago, I wrote a simple .NET application that performs X amount of requests and calculates an average speed of those requests.  It does this by dropping the highest and lowest request times, then taking an average speed on the remaining requests.

This does a decent job for a straight up speed test.  However, a few possibilities could arise, such as CPU hogging that could skew the results.  Instead, I've made a few alterations and converted the speed tester to not be based on the number of requests, but instead based on a specific amount of time.  This should help eliminate some inconsistencies of doing a straight number of requests.

Read more >

Tags: Optimization | ASP.NET | timer | speed comparison | .net | Theory