Click here to close now.


Java IoT Authors: Elizabeth White, Pat Romanski, Liz McMillan, Anders Wallgren, Betty Zakheim

Related Topics: Microservices Expo, Java IoT, Industrial IoT, Microsoft Cloud, IoT User Interface, Agile Computing

Microservices Expo: Article

Evaluating the Performance of SPDY-Enabled Web Servers

With all the advantages of SPDY, you may be wondering if there is a price to pay on the server side

As you may already know, SPDY (pronounced "SPeeDY") is a new networking protocol introduced by Google and designed to reduce the web latency associated with HTTP. With SPDY, web pages load up to 64 percent faster than HTTP alone, according to Google. It accomplishes this by adding a session layer between HTTP and SSL that supports concurrent, interleaved streams over a single TCP connection. The initial draft of HTTP/2.0, the future of the web, is based on SPDY, which is a welcome step forward considering that HTTP/1.0 was released in 1996. SPDY holds great potential for mobile devices, for which latency is more of an issue, and the market is catching on. As evidence of this, Microsoft recently announced the next version of Internet Explorer will support the new protocol.

Today, SPDY can be deployed on Apache by installing a single module (mod-spdy, the Apache SPDY module). No changes to website content are required. SPDY is now enabled by default on many of the latest modern browsers, including Chrome, Firefox, Opera, and Android Browser. (You can check your own browser's support by visiting

Simply by deploying the SPDY module on your Apache server, you can provide a large percentage of your users with better response times. More important, the response times of a website are correlated with the site's conversion rate and bounce rate - so SPDY can have a significant positive impact on your business!

With all the advantages of SPDY, you may be wondering if there is a price to pay on the server side. Moving from HTTP to SPDY adds encryption and compression overhead, which clearly requires more resources. It does, however, use fewer TCP connections. It wasn't immediately clear to me if all these changes in aggregate would cause noticeable drawbacks on the server.

To get to the bottom of this question, I thought it would be interesting to get some real-world performance metrics on SPDY, in particular its effect on the server side. To obtain this information, I used the new SPDY support in NeoLoad to run load tests of SPDY and compare its performance against HTTP and HTTPS.

Test Configuration Details
My approach was to test a server with a fairly typical configuration - not one that is finely tuned for a specific purpose. This setup provides a basis for comparing HTTP, HTTPS and SPDY. It's important to note here that changes to the application or the server configuration will produce different results - perhaps vastly different.

Test setup:
●     Server:
○     OS: Linux CentOS 6.3
○     Hardware:
■      Intel Core i3 CPU 540 @ 3.07GHz
■     4GB RAM
○     Apache
■     Version 2.2.15
■     worker MPM:
>StartServers    5
MaxClients      600
MinSpareThreads       50
MaxSpareThreads      150
ThreadsPerChild         50
MaxRequestsPerChild 0

■     SPDY module (mod-spdy-beta- Default SPDY optimization flags were used (uncommented suggested values):
●     SpdyMaxThreadsPerProcess 30
●     SpdyMaxStreamsPerConnection 100
●     Application:
○     1 web page: 1 HTML 9.5kB + 50 PNG icons (32x32).
○     The web page and all resources were served by the same server.
●     Load testing tool: NeoLoad 4.1.2
●     Tests:
○     Ramp-up from 1 to 1000 users for 20 minutes.
○     Scenario: 1 page call, wait for 5s, restart.
○     Chrome browser simulated, with 6 parallel connections to the server.
○     Emulated latency: 40ms in download, 45ms in upload.
○     Test HTTP, HTTPS, and SPDY under the same conditions.
○      Aggregation period of 30s for graphs. This smoothes variations to simplify comparison between several tests.

Results and Analysis
First I wanted to examine the hit rate (hits per second), average response time (duration), and number of errors as the number of concurrent users increased.

Here are the results for the HTTP test:

The plot illustrates the following:

  • At three minutes, the maximum number of page per second is reached. This maximum rate (16 pages/s or 827 request/s) is reached at 120 virtual users (VU), and the rate decreases as more concurrent users are added.
  • At the same time (the three-minute mark), response time starts to increase significantly.
  • The first errors (which investigation revealed to be timeouts) appear at 405 users.

The table below compares these metrics for HTTP, HTTPS, and SPDY:





Maximum pages/s

16.3 pages/s

after 3 minutes at 120 users

15.9 pages/s

after 3 minutes at 120 users

98 pages/s

after 14 minutes at 777 users

Page response time at 100 users




Page response time at 120 users

1.4 s



Page response time at 200 users




Page response time at 777 users




First error

405 Users

225 Users

884 Users

Service-level agreement violation (< 3s page load time)

133 Users

133 Users

794 Users


Based on a service-level agreement (SLA) of less than 3s for page load time, my test server handled almost six times as many users with SPDY than HTTP.

More users with fewer workers
To handle incoming requests in parallel, Apache web servers use worker threads to process each request. Because each thread consumes resources and memory, Apache lets the system administrator limit thread use, which has an effect on how incoming requests are handled.

My HTTP and HTTPS results are typical of a scenario known as thread starvation.

This is confirmed by the following graph, which shows busy workers in orange, page rate in green, and user load in blue:

The number of busy Apache workers (threads) hits its maximum at the same time the page rate reaches its maximum.

In contrast to HTTP/S, SPDY uses a single connection for all requests. The principal benefit of this is the decreased latency seen by the client, resulting in reduced response times for users. There is another great benefit on the server side: SPDY clients consume one worker instead of six. As a result it takes much longer (that is, many more users) for all workers to become busy:

SPDY enables the server to handle more users with the same number of workers.

Server CPU and memory consumption
So far, I showed how SPDY affects Apache worker usage with my test configuration. Next, I wanted to see how CPU usage and memory were affected by SPDY.

Here is a plot showing system idle time (low when the CPU is used intensively) for HTTP/HTTPS/SPDY:

No surprise here - as most HTTP/HTTPS requests are waiting to be served after the thread limit is reached, they don't consume much CPU. For the SPDY tests, Apache is below the worker limit for much longer, resulting in a higher page rate and consequently more CPU used. The curve plateau is reached when all workers are busy (around 11 minutes).

To better understand the behavior before the worker limit is reached, I focused on the numbers at two minutes, 88 virtual users, and 12.5 pages/s. The CPU idle time measurements are an average of six values taken over 30 seconds:





CPU Idle time at 2 minutes




The values are comparable; SPDY consumes slightly less CPU than HTTPS and slightly more than HTTP for this load.

On the memory side, here's the global overview:

Again, it's interesting to examine the memory used before the worker limit is reached. The numbers are an average of six measurements over 30 seconds.

System Memory



Difference = Consumed Memory


3,357 MB

3,416 MB

59 MB


3,500 MB

3,579 MB

79 MB


3,607 MB

3,631 MB

24 MB

The server consumed less memory when handling SPDY requests than when handling HTTP and HTTPS.

During this test, SPDY consumed just 41% of the memory consumed by HTTP, and just 30% of the memory consumed by HTTPS.

It's no surprise that SPDY improves response times on the client side; that's what it was designed to do. It turns out that SPDY also has advantages on the server side:

  • Compared to HTTPS, SPDY requests consume fewer resources (CPU and memory) on the server.
  • Compared to HTTP, SPDY requests consume less memory but a bit more CPU. This may be good, bad, or irrelevant depending on which resource (if either) is currently limiting your server.
  • Compared to HTTP/S, SPDY requires fewer Apache worker threads, which increases server capacity. As a result, the server may attract more SPDY traffic.

From these results, it's clear that Apache tuning performed for HTTP/S may not be appropriate after SPDY is enabled on the server. It's important to take the time to re-evaluate server sizing and retune the server before you start handling SPDY requests from your users.

As I mentioned earlier, the test results I've shared here are specific to my server configuration and the web page I used for the tests. It's important to understand how your server will perform under a realistic user load before you make SPDY available to the users on your site. I encourage you to test your own server and website using a load testing tool such as NeoLoad (there's a free 30-day trial if you want) to see how SPDY will affect your users' response times and your server's performance.

More Stories By Hervé Servy

Hervé Servy is a Senior Performance Engineer at Neotys. He has spent 10 years working for IBM-Rational and Microsoft pre-sales and marketing in France and the Middle East. During the past 3 years, as a personal project, Hervé founded a nonprofit organization in the health 2.0 area. If that isn’t techie enough, Hervé was also born on the very same day Apple Computer was founded.

Comments (0)

Share your thoughts on this story.

Add your comment
You must be signed in to add a comment. Sign-in | Register

In accordance with our Comment Policy, we encourage comments that are on topic, relevant and to-the-point. We will remove comments that include profanity, personal attacks, racial slurs, threats of violence, or other inappropriate material that violates our Terms and Conditions, and will block users who make repeated violations. We ask all readers to expect diversity of opinion and to treat one another with dignity and respect.

@ThingsExpo Stories
Continuous processes around the development and deployment of applications are both impacted by -- and a benefit to -- the Internet of Things trend. To help better understand the relationship between DevOps and a plethora of new end-devices and data please welcome Gary Gruver, consultant, author and a former IT executive who has led many large-scale IT transformation projects, and John Jeremiah, Technology Evangelist at Hewlett Packard Enterprise (HPE), on Twitter at @j_jeremiah. The discussion is moderated by me, Dana Gardner, Principal Analyst at Interarbor Solutions.
Too often with compelling new technologies market participants become overly enamored with that attractiveness of the technology and neglect underlying business drivers. This tendency, what some call the “newest shiny object syndrome” is understandable given that virtually all of us are heavily engaged in technology. But it is also mistaken. Without concrete business cases driving its deployment, IoT, like many other technologies before it, will fade into obscurity.
With all the incredible momentum behind the Internet of Things (IoT) industry, it is easy to forget that not a single CEO wakes up and wonders if “my IoT is broken.” What they wonder is if they are making the right decisions to do all they can to increase revenue, decrease costs, and improve customer experience – effectively the same challenges they have always had in growing their business. The exciting thing about the IoT industry is now these decisions can be better, faster, and smarter. Now all corporate assets – people, objects, and spaces – can share information about themselves and thei...
The Internet of Things is clearly many things: data collection and analytics, wearables, Smart Grids and Smart Cities, the Industrial Internet, and more. Cool platforms like Arduino, Raspberry Pi, Intel's Galileo and Edison, and a diverse world of sensors are making the IoT a great toy box for developers in all these areas. In this Power Panel at @ThingsExpo, moderated by Conference Chair Roger Strukhoff, panelists discussed what things are the most important, which will have the most profound effect on the world, and what should we expect to see over the next couple of years.
Growth hacking is common for startups to make unheard-of progress in building their business. Career Hacks can help Geek Girls and those who support them (yes, that's you too, Dad!) to excel in this typically male-dominated world. Get ready to learn the facts: Is there a bias against women in the tech / developer communities? Why are women 50% of the workforce, but hold only 24% of the STEM or IT positions? Some beginnings of what to do about it! In her Day 2 Keynote at 17th Cloud Expo, Sandy Carter, IBM General Manager Cloud Ecosystem and Developers, and a Social Business Evangelist, wil...
PubNub has announced the release of BLOCKS, a set of customizable microservices that give developers a simple way to add code and deploy features for realtime apps.PubNub BLOCKS executes business logic directly on the data streaming through PubNub’s network without splitting it off to an intermediary server controlled by the customer. This revolutionary approach streamlines app development, reduces endpoint-to-endpoint latency, and allows apps to better leverage the enormous scalability of PubNub’s Data Stream Network.
Discussions of cloud computing have evolved in recent years from a focus on specific types of cloud, to a world of hybrid cloud, and to a world dominated by the APIs that make today's multi-cloud environments and hybrid clouds possible. In this Power Panel at 17th Cloud Expo, moderated by Conference Chair Roger Strukhoff, panelists addressed the importance of customers being able to use the specific technologies they need, through environments and ecosystems that expose their APIs to make true change and transformation possible.
Microservices are a very exciting architectural approach that many organizations are looking to as a way to accelerate innovation. Microservices promise to allow teams to move away from monolithic "ball of mud" systems, but the reality is that, in the vast majority of organizations, different projects and technologies will continue to be developed at different speeds. How to handle the dependencies between these disparate systems with different iteration cycles? Consider the "canoncial problem" in this scenario: microservice A (releases daily) depends on a couple of additions to backend B (re...
I recently attended and was a speaker at the 4th International Internet of @ThingsExpo at the Santa Clara Convention Center. I also had the opportunity to attend this event last year and I wrote a blog from that show talking about how the “Enterprise Impact of IoT” was a key theme of last year’s show. I was curious to see if the same theme would still resonate 365 days later and what, if any, changes I would see in the content presented.
Apps and devices shouldn't stop working when there's limited or no network connectivity. Learn how to bring data stored in a cloud database to the edge of the network (and back again) whenever an Internet connection is available. In his session at 17th Cloud Expo, Ben Perlmutter, a Sales Engineer with IBM Cloudant, demonstrated techniques for replicating cloud databases with devices in order to build offline-first mobile or Internet of Things (IoT) apps that can provide a better, faster user experience, both offline and online. The focus of this talk was on IBM Cloudant, Apache CouchDB, and ...
Container technology is shaping the future of DevOps and it’s also changing the way organizations think about application development. With the rise of mobile applications in the enterprise, businesses are abandoning year-long development cycles and embracing technologies that enable rapid development and continuous deployment of apps. In his session at DevOps Summit, Kurt Collins, Developer Evangelist at, examined how Docker has evolved into a highly effective tool for application delivery by allowing increasingly popular Mobile Backend-as-a-Service (mBaaS) platforms to quickly crea...
With major technology companies and startups seriously embracing IoT strategies, now is the perfect time to attend @ThingsExpo 2016 in New York and Silicon Valley. Learn what is going on, contribute to the discussions, and ensure that your enterprise is as "IoT-Ready" as it can be! Internet of @ThingsExpo, taking place Nov 3-5, 2015, at the Santa Clara Convention Center in Santa Clara, CA, is co-located with 17th Cloud Expo and will feature technical sessions from a rock star conference faculty and the leading industry players in the world. The Internet of Things (IoT) is the most profound cha...
Internet of @ThingsExpo, taking place June 7-9, 2016 at Javits Center, New York City and Nov 1-3, 2016, at the Santa Clara Convention Center in Santa Clara, CA, is co-located with the 18th International @CloudExpo and will feature technical sessions from a rock star conference faculty and the leading industry players in the world and ThingsExpo New York Call for Papers is now open.
The cloud. Like a comic book superhero, there seems to be no problem it can’t fix or cost it can’t slash. Yet making the transition is not always easy and production environments are still largely on premise. Taking some practical and sensible steps to reduce risk can also help provide a basis for a successful cloud transition. A plethora of surveys from the likes of IDG and Gartner show that more than 70 percent of enterprises have deployed at least one or more cloud application or workload. Yet a closer inspection at the data reveals less than half of these cloud projects involve production...
Cloud computing delivers on-demand resources that provide businesses with flexibility and cost-savings. The challenge in moving workloads to the cloud has been the cost and complexity of ensuring the initial and ongoing security and regulatory (PCI, HIPAA, FFIEC) compliance across private and public clouds. Manual security compliance is slow, prone to human error, and represents over 50% of the cost of managing cloud applications. Determining how to automate cloud security compliance is critical to maintaining positive ROI. Raxak Protect is an automated security compliance SaaS platform and ma...
In his keynote at @ThingsExpo, Chris Matthieu, Director of IoT Engineering at Citrix and co-founder and CTO of Octoblu, focused on building an IoT platform and company. He provided a behind-the-scenes look at Octoblu’s platform, business, and pivots along the way (including the Citrix acquisition of Octoblu).
There are over 120 breakout sessions in all, with Keynotes, General Sessions, and Power Panels adding to three days of incredibly rich presentations and content. Join @ThingsExpo conference chair Roger Strukhoff (@IoT2040), June 7-9, 2016 in New York City, for three days of intense 'Internet of Things' discussion and focus, including Big Data's indespensable role in IoT, Smart Grids and Industrial Internet of Things, Wearables and Consumer IoT, as well as (new) IoT's use in Vertical Markets.
Today air travel is a minefield of delays, hassles and customer disappointment. Airlines struggle to revitalize the experience. GE and M2Mi will demonstrate practical examples of how IoT solutions are helping airlines bring back personalization, reduce trip time and improve reliability. In their session at @ThingsExpo, Shyam Varan Nath, Principal Architect with GE, and Dr. Sarah Cooper, M2Mi’s VP Business Development and Engineering, explored the IoT cloud-based platform technologies driving this change including privacy controls, data transparency and integration of real time context with p...
The Internet of Things (IoT) is growing rapidly by extending current technologies, products and networks. By 2020, Cisco estimates there will be 50 billion connected devices. Gartner has forecast revenues of over $300 billion, just to IoT suppliers. Now is the time to figure out how you’ll make money – not just create innovative products. With hundreds of new products and companies jumping into the IoT fray every month, there’s no shortage of innovation. Despite this, McKinsey/VisionMobile data shows "less than 10 percent of IoT developers are making enough to support a reasonably sized team....
We all know that data growth is exploding and storage budgets are shrinking. Instead of showing you charts on about how much data there is, in his General Session at 17th Cloud Expo, Scott Cleland, Senior Director of Product Marketing at HGST, showed how to capture all of your data in one place. After you have your data under control, you can then analyze it in one place, saving time and resources.