| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
  |
|
| IIB HTTP Connection Handling Reports |
« View previous topic :: View next topic » |
| Author |
Message
|
| inMo |
 Posted: Thu Oct 29, 2015 5:09 am Post subject: IIB HTTP Connection Handling Reports |
 |
|
Master
Joined: 27 Jun 2009
Posts: 216
Location: NY
|
| Is anyone aware of any IBM reports that highlight IIB v9's ability to manage HTTP/S connections? I'd like to learn more about upper boundaries. |
|
| Back to top |
|
 |
| mqjeff |
| Posted: Thu Oct 29, 2015 5:15 am Post subject: |
|
|
Grand Master
Joined: 25 Jun 2008
Posts: 17447
|
There should (?) be some stuff at least in the perf reports. It's also possible to tune the http listeners in much the same way as other http servers - buffers, concurrent threads, etc... Which is limited by memory and network bandwidth and all the usual things.
Are you concerned about the number of incoming connections? Or the throughput? If it's the throughput, you have to remember the time executing your flows.
Also, none of this has to do with *Request nodes. Those are simply part of the flow thread.
SSL has the same impact (or should) on performance as the same algorithms have with any other HTTP server...
(also remember to use TLS, not SSL...  )
_________________
chmod -R ugo-wx / |
|
| Back to top |
|
|
| inMo |
| Posted: Thu Oct 29, 2015 5:28 am Post subject: |
|
|
Master
Joined: 27 Jun 2009
Posts: 216
Location: NY
|
Thank you for the insight. Your question was spot on
| Quote: |
| Are you concerned about the number of incoming connections? |
I have a light memory from v6 of some references to a suggested upper limit of 2000 incoming HTTP connections. I'm looking to assess the risk of v9 expecting 2k, then 5K, then 10k, then 15k, etc... incoming connections to a single IIB node.
As for throughput of the those connections, I understand the different levers I can move manage those. I'm just not sure how many connections I can ask IIB to handle without pushing it beyond limits. |
|
| Back to top |
|
|
| mqjeff |
| Posted: Thu Oct 29, 2015 6:05 am Post subject: |
|
|
Grand Master
Joined: 25 Jun 2008
Posts: 17447
|
Most of the levers you need to play with are here (these apply to https as well as the biplistener)
In terms of upper limits... again, that's dependent on the memory of your system.
Also remember that as a socket comes into the listener, it gets handed off to the message flow. So you can scale the instances of the flow to match your overall rate of incoming connections - say you get 10,000 incoming connections a second, and your flows take 1/200th of a second to process. You would then have 20 instances of your flow. You should be able to more than reasonably handle this with the 200 connections at the http server level. Each connection would only be sitting in the https server until one instance of the flow was able to hold it.
So you absolutely don't need 10,000 connections at the http server.
Of course as you spread out more flows across the same listener (in the same eg or in the same broker depending on which listener you're using), you have to do more tuning.
And, again, using an external http server - config exported using the tools available with IIB as a config for either Apache mod-proxy or IHS - lets you simplify the ip/ports your apps need to know about *and* load-balance *and* handle more incoming connections. And, of course, give you a place to do more error handling of returns to adjust the messages to provide proper feedback to your applications.
Not that I'm biased about this architecture because I spent so much personal time arguing to get the export function developed...  
_________________
chmod -R ugo-wx / |
|
| Back to top |
|
|
|
|
|
| |
|
Page 1 of 1 |
|
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum
|
|
|
|
