Scenario: Evaluating Web Client Performance

Contents

Hardware

Scenarios were run entirely on the following hardware:

  • Model Name: MacBook Pro
  • Model Identifier: MacBookPro8,2
  • Processor Name: Intel Core i7
  • Processor Speed: 2.5 GHz
  • Number of Processors: 1
  • Total Number of Cores: 4
  • L2 Cache (per Core): 256 KB
  • L3 Cache: 8 MB
  • Memory: 8 GB
  • Boot ROM Version: MBP81.0047.B27

Operating System

  • XP 64-bit SP2 in Parallels 8 on Mac
  • OS X 10.8.3

Software

  • Iguana 6.0-snapshot
  • Apache 2.2.25 (Win32)

Iguana Channel Setup

  • Source component = From Translator
  • Destination component = To Translator*

*This component makes the HTTP GET and POST requests to the web server.

Example Headers

request header

[‘Keep-Alive’]=’timeout=5, max=10000′

[‘Connection’]=’Keep-Alive’

response header

[‘Connection’]=’Keep-Alive’

[‘Date’]=’Tue, 03 Sep 2013 01:02:09 GMT’

[‘Content-Type’]=’text/plain’

[‘ETag’]=’\”40000000376e6-5e-4e56cb57702bb\”‘

[‘Last-Modified’]=’Mon, 02 Sep 2013 20:49:30 GMT’

[‘Keep-Alive’]=’timeout=5, max=99′

[‘Content-Length’]=’94’

[‘Accept-Ranges’]=’bytes’

[‘Server’]=’Apache/2.2.25 (Win32)’

  • The ‘timeout’ header parameter indicates the time that a connection will be allowed to remain idle before it is closed
  • The ‘max’ header parameter indicates the maximum number of requests that will be permitted before the connection is closed
  • ‘Connection=Keep-Alive’ is the critical header attribute sent by both client and server to ensure that the conversation reused the socket
  • ‘Content-Length’ should also be provided and correctly set