Posted: Mon Jul 07, 2008 1:50 am Post subject: Slow First Request - for Http Input Node.
Voyager
Joined: 02 Feb 2007 Posts: 93 Location: Scotland
Hi,
Have a scenario in which a flow is doing http -> transform -> MQ.
However on first request ( or request after a period of no activity - about 10 mins ) it takes on average 1 second longer. In our production scenario - this is not acceptable.
It seems to be the biphttplistener that has an overhead- as when we run a MQ -> transform-> MQ we dont have the issue.
I appreciate that it is good working practices to "move out" components that have not been accessed in X seconds. But in this situation I need to keep this in an always active state.
I found this information in a developerWorks article. I am not sure if this will help you:
There is a configurable property called maxKeepAliveRequests that specifies how many requests can be send down a single connection.
The default Message Broker value is 100. Therefore, when an HTTP client connects, it can send 100 requests before Message Broker issues a Connection: close and closes the socket. The next request the client sends creates a new socket and again can send up to 100 requests. In many environments this setting may be enough. But when maximum throughput is required, you may need to set this value higher or make it unlimited, in order to achieve the desired throughput.
Here is the command: mqsichangeproperties MyBroker -b httplistener -o HTTPConnector -n maxKeepAliveRequests -v 0
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