Click here to close now.


Java IoT Authors: Pat Romanski, Liz McMillan, AppDynamics Blog, Ed Featherston, Victoria Livschitz

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
The Internet of Everything is re-shaping technology trends–moving away from “request/response” architecture to an “always-on” Streaming Web where data is in constant motion and secure, reliable communication is an absolute necessity. As more and more THINGS go online, the challenges that developers will need to address will only increase exponentially. In his session at @ThingsExpo, Todd Greene, Founder & CEO of PubNub, will explore the current state of IoT connectivity and review key trends and technology requirements that will drive the Internet of Things from hype to reality.
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, will explore the IoT cloud-based platform technologies driving this change including privacy controls, data transparency and integration of real time context w...
The buzz continues for cloud, data analytics and the Internet of Things (IoT) and their collective impact across all industries. But a new conversation is emerging - how do companies use industry disruption and technology enablers to lead in markets undergoing change, uncertainty and ambiguity? Organizations of all sizes need to evolve and transform, often under massive pressure, as industry lines blur and merge and traditional business models are assaulted and turned upside down. In this new data-driven world, marketplaces reign supreme while interoperability, APIs and applications deliver un...
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....
Electric power utilities face relentless pressure on their financial performance, and reducing distribution grid losses is one of the last untapped opportunities to meet their business goals. Combining IoT-enabled sensors and cloud-based data analytics, utilities now are able to find, quantify and reduce losses faster – and with a smaller IT footprint. Solutions exist using Internet-enabled sensors deployed temporarily at strategic locations within the distribution grid to measure actual line loads.
You have your devices and your data, but what about the rest of your Internet of Things story? Two popular classes of technologies that nicely handle the Big Data analytics for Internet of Things are Apache Hadoop and NoSQL. Hadoop is designed for parallelizing analytical work across many servers and is ideal for the massive data volumes you create with IoT devices. NoSQL databases such as Apache HBase are ideal for storing and retrieving IoT data as “time series data.”
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.
The IoT market is on track to hit $7.1 trillion in 2020. The reality is that only a handful of companies are ready for this massive demand. There are a lot of barriers, paint points, traps, and hidden roadblocks. How can we deal with these issues and challenges? The paradigm has changed. Old-style ad-hoc trial-and-error ways will certainly lead you to the dead end. What is mandatory is an overarching and adaptive approach to effectively handle the rapid changes and exponential growth.
Today’s connected world is moving from devices towards things, what this means is that by using increasingly low cost sensors embedded in devices we can create many new use cases. These span across use cases in cities, vehicles, home, offices, factories, retail environments, worksites, health, logistics, and health. These use cases rely on ubiquitous connectivity and generate massive amounts of data at scale. These technologies enable new business opportunities, ways to optimize and automate, along with new ways to engage with users.
The IoT is upon us, but today’s databases, built on 30-year-old math, require multiple platforms to create a single solution. Data demands of the IoT require Big Data systems that can handle ingest, transactions and analytics concurrently adapting to varied situations as they occur, with speed at scale. In his session at @ThingsExpo, Chad Jones, chief strategy officer at Deep Information Sciences, will look differently at IoT data so enterprises can fully leverage their IoT potential. He’ll share tips on how to speed up business initiatives, harness Big Data and remain one step ahead by apply...
There will be 20 billion IoT devices connected to the Internet soon. What if we could control these devices with our voice, mind, or gestures? What if we could teach these devices how to talk to each other? What if these devices could learn how to interact with us (and each other) to make our lives better? What if Jarvis was real? How can I gain these super powers? In his session at 17th Cloud Expo, Chris Matthieu, co-founder and CTO of Octoblu, will show you!
As a company adopts a DevOps approach to software development, what are key things that both the Dev and Ops side of the business must keep in mind to ensure effective continuous delivery? In his session at DevOps Summit, Mark Hydar, Head of DevOps, Ericsson TV Platforms, will share best practices and provide helpful tips for Ops teams to adopt an open line of communication with the development side of the house to ensure success between the two sides.
SYS-CON Events announced today that ProfitBricks, the provider of painless cloud infrastructure, will exhibit at SYS-CON's 17th International Cloud Expo®, which will take place on November 3–5, 2015, at the Santa Clara Convention Center in Santa Clara, CA. ProfitBricks is the IaaS provider that offers a painless cloud experience for all IT users, with no learning curve. ProfitBricks boasts flexible cloud servers and networking, an integrated Data Center Designer tool for visual control over the cloud and the best price/performance value available. ProfitBricks was named one of the coolest Clo...
SYS-CON Events announced today that IBM Cloud Data Services has been named “Bronze Sponsor” of SYS-CON's 17th Cloud Expo, which will take place on November 3–5, 2015, at the Santa Clara Convention Center in Santa Clara, CA. IBM Cloud Data Services offers a portfolio of integrated, best-of-breed cloud data services for developers focused on mobile computing and analytics use cases.
SYS-CON Events announced today that Sandy Carter, IBM General Manager Cloud Ecosystem and Developers, and a Social Business Evangelist, will keynote at the 17th International Cloud Expo®, which will take place on November 3–5, 2015, at the Santa Clara Convention Center in Santa Clara, CA.
Developing software for the Internet of Things (IoT) comes with its own set of challenges. Security, privacy, and unified standards are a few key issues. In addition, each IoT product is comprised of at least three separate application components: the software embedded in the device, the backend big-data service, and the mobile application for the end user's controls. Each component is developed by a different team, using different technologies and practices, and deployed to a different stack/target - this makes the integration of these separate pipelines and the coordination of software upd...
Mobile messaging has been a popular communication channel for more than 20 years. Finnish engineer Matti Makkonen invented the idea for SMS (Short Message Service) in 1984, making his vision a reality on December 3, 1992 by sending the first message ("Happy Christmas") from a PC to a cell phone. Since then, the technology has evolved immensely, from both a technology standpoint, and in our everyday uses for it. Originally used for person-to-person (P2P) communication, i.e., Sally sends a text message to Betty – mobile messaging now offers tremendous value to businesses for customer and empl...
"Matrix is an ambitious open standard and implementation that's set up to break down the fragmentation problems that exist in IP messaging and VoIP communication," explained John Woolf, Technical Evangelist at Matrix, in this interview at @ThingsExpo, held Nov 4–6, 2014, at the Santa Clara Convention Center in Santa Clara, CA.
WebRTC converts the entire network into a ubiquitous communications cloud thereby connecting anytime, anywhere through any point. In his session at WebRTC Summit,, Mark Castleman, EIR at Bell Labs and Head of Future X Labs, will discuss how the transformational nature of communications is achieved through the democratizing force of WebRTC. WebRTC is doing for voice what HTML did for web content.
Nowadays, a large number of sensors and devices are connected to the network. Leading-edge IoT technologies integrate various types of sensor data to create a new value for several business decision scenarios. The transparent cloud is a model of a new IoT emergence service platform. Many service providers store and access various types of sensor data in order to create and find out new business values by integrating such data.