SPDY Load Testing Tools Resources

 
 
 
 
 
 
 

All the load testing tools that can help a website or intranet application developer to ensure good performance and no crash under stress.

 

 Resources
 What is Load Testing?
 Load vs Stress Testing
 Mobile Load Testing
 Cloud Load Testing
 WebSocket Load Testing
 Flex Load Testing
 GWT Load Testing
 SPDY Load Testing
 RTMP Load Testing
 Java Serialization Testing
 Siebel Load Testing
 Maximo Load Testing
 AJAX Push Load Testing
 Oracle Load Testing
 Silverlight Load Testing
 SOAP Load Testing

 Free Load Testing Tools

 NeoLoad

 LoadRunner

 JMeter
 

What is SPDY Application Load Testing?

The main goal of SPDY is to reduce web page load time. This is achieved by prioritizing and multiplexing the transfer of web page subresources so that only one connection per client is required. TLS encryption is nearly ubiquitous in SPDY implementations, and transmissions are gzip or deflate compressed by design. Moreover, servers may hint or even push content instead of awaiting individual requests for each resource of a web page.

The SPDY project defines and implements an application layer protocol for the web which strongly reduces latency. The goals for SPDY are:

  • To target a 50% reduction in page load time.
  • To minimize deployment complexity. SPDY uses TCP as the underlying transport layer, so requires no changes to existing networking infrastructure.
  • To avoid the need for any changes to content by website authors. The only changes required to support SPDY are in the client user agent and web server applications.
  • To bring together like-minded parties interested in exploring protocols as a way of solving the latency problem.
  • To allow many concurrent HTTP requests to run across a single TCP session.
  • To reduce the bandwidth currently used by HTTP by compressing headers and eliminating unnecessary headers.
  • To define a protocol that is easy to implement and server-efficient.
  • To make SSL the underlying transport protocol, for better security and compatibility with existing network infrastructure. Although SSL does introduce a latency penalty, we believe that the long-term future of the web depends on a secure network connection. In addition, the use of SSL is necessary to ensure that communication across existing proxies is not broken.
  • To enable the server to initiate communications with the client and push data to the client whenever possible.

SPDY does not replace HTTP; it modifies the way HTTP requests and responses are sent over the wire. This means that all existing server-side applications can be used without modification if a SPDY-compatible translation layer is put in place. When sent over SPDY, HTTP requests are processed, tokenized, simplified and compressed.

Load testers will need now to test and code their scripts on both, HTTP and SPDY protocol.

Learn More about Performance with SPDY



mod_spdy is a SPDY module for Apache 2.2 that allows your web server to take advantage of SPDY features like stream multiplexing and header compression.


Recommended Tool

NeoLoad is a performance testing tool which supports SPDY application testing.



You've liked this content? Please recommend us on Google+1:

 

contact us
  © Copyright 2004-2017 by load-testing-tools.com