I read up on some HTTP queue handling and stumbled on this.

In default Domino (6, 6.5, 7 and 8) HTTP queue handling a round robin method of assigning work to the HTTP threads is used. This could potentially leave a lot of HTTP threads idling and others doing hard work like performing agent-url's.
If you are unlucky you might be queued after such a URL and have to wait for the other one to finish - even though there are idling http threads!

If you enable HTTPQueueMethod=2 you will have assignment to the HTTP-thread with the least workload. There is a small price in OS overhead - switching threads.

If you do recursive calls to a domino server you might end up with a deadlock with the standard setting: Your first requests do a request for a XML-page on the same server and that second request ends up behind the first request. Classic deadlock scenario!

You can of course deadlock even with method 2 but it is less likely.

Domino does NOT support recursive requests!

I will try this one out and do some timings. Anyone has any experience with this one?

Hi,

 

I believe that the HTTPQueueMethod=2 way of doing things was the standard way in version 5 actually (which performed better than the new way under certain circumstances). There was a thread regarding this on notes.net one year ago (if i remember correctly). The penalty is higher memory consumption (but hey, memory is cheap, right ;))

 

regards

 

Daniel

Yes I think I saw that thread.

My preliminary tests do not show that much difference in response time. In fact I have a hard time finding any difference.

I will probably have to have more load on the server. Unless you have a high load on your sever - do not bother with this one.

Update: Starting with 8.5.1 HTTPQueueMethod is default 2 again.

I think this is a good thing. If there are long running requests on the server it will not bring down performance for all users.

Read more here:
http://www-10.lotus.com/ldd/dominowiki.nsf/dx/httpqueuemethod