• Share
  • ?
  • Profiles ▼
  • Communities ▼
  • Apps ▼

Blogs

  • My Blogs
  • Public Blogs
  • My Updates
  • Administration

This community can have members from outside your organization. ColinPaice Blog

  • Log in to participate
c4142f9d-6cf1-44ef-a44a-b09428ad96d1 Blog

▼ Tags

 

▼ Archive

  • June 2018
  • May 2018
  • April 2018
  • March 2018
  • February 2018
  • January 2018
  • December 2017
  • November 2017
  • October 2017
  • September 2017
  • August 2017
  • July 2017
  • June 2017
  • May 2017
  • April 2017
  • March 2017
  • February 2017
  • January 2017
  • December 2016
  • November 2016
  • October 2016
  • September 2016
  • August 2016
  • June 2016
  • April 2016
  • March 2016
  • February 2016
  • January 2016
  • November 2015
  • October 2015
  • September 2015
  • August 2015
  • May 2015
  • April 2015
  • March 2015
  • February 2015
  • January 2015
  • December 2014
  • November 2014
  • October 2014
  • September 2014
  • August 2014
  • May 2014
  • April 2014
  • March 2014
  • February 2014
  • December 2013
  • October 2013
  • September 2013
  • August 2013

▼ Blog Authors

ColinPaice Blog

View All Entries
Clicking the button causes a full page refresh. The user could go to the "Entry list" region to view the new content.) Entry list

Impact of using TLS/SSH on throughput should not be noticable

ColinPaice 120000E7BQ | ‎ | 4,381 Views

While we were discussing TLS throughput over TCPIP I found an interesting fact - but it should make no difference!

  • When using a channel without TLS, MQ cuts the messages into chunks of up to 32KB.
  • When using a channel with TLS, The call to the crypto facility does it in chunks of 16KB and then MQ sends it.   This means that to send 32KB of data, there are now two send requests each of 16KB.

Sending the data as two 16KB chunks instead of one 32KB chunk should make little difference, as you should be using large TCP window sizes ( eg send many chunks before the remote end sends back the TCP ACK).
It may make a difference if your network is not fine tuned, and so there is more data flowing within TCP to ACKnowledge two chunks instead of one chunk.

  • Add a Comment Add a Comment
  • Edit
  • More Actions v
  • Quarantine this Entry
Notify Other People
notification_ex

Send Email Notification

Quarantine this entry

deleteEntry
duplicateEntry

Mark as Duplicate

  • Previous Entry
  • Main
  • Next Entry
Feed for Blog Entries | Feed for Blog Comments | Feed for Comments for this Entry