Tag: DCT

HTTP_MaxActiveThreads and Lotus Notes Traveler

Scott O’Keefe recently released new rules for the Domino Configuration Tuner. One of this rules watches the “Max Active Threads” setting in the server document.

The HTTP_MaxActiveThreads setting, found on the Internet Protocols/HTTP tab of the server document should be set to keep the CPU sufficiently busy and by default, it has a value of 40. DCT recommends to set this value between 40 and 80.

I ran a scan against my test server and DCT reported that HTTP_MaxActiveThreads has a value of 100 which is not a recommended setting.  So I edited the server document and changed the value to the default value.

After saving the document, I restarted the server for the changes to take effect.

This is the point, where Lotus Notes Traveler enters the scene. I looked at the console and saw the following:

serverDocHTTP3

Aha, Lotus Traveler is restarting the HTTP task. Well, nothing strange about this. In the end both, Traveler and HTTP worked as usual.

I ran the DCT scan again and was very surprised that once again the HTTP_MaxActiveThreads rule reports a not recommended value of 100.

I opened the server doc to verify the value and indeed, the value had changed from 40 to 100 again.

I once again changed the setting and restarted the server. Same result.

I reconfigured the server to not start traveler at server startup. This time, the setting did not change automatically.

Does anybody know something about this behaviour? Is this a bug or a feature? Maybe it is documented somewhere. Any hint is appreciated.

Edit: Forgot to mention that the server and Lotus Traveler are  8.5.1


FTOTM

Yesterday was FTOTM. FTOTM?? Yes, it was The First Tuesday Of The Month!

(Actually) on this day, Scott O’Keefe releases new rules and updates of existing rules for Domino Configuration Tuner.

dct010909

Check out this site for the latest updates for DCT.


Confusing DCT results

The Domino Configuration Tuner (DCT) evaluates server settings according to a growing catalog of  best practices. All servers in a single domain can be evaluated together. DCT generates reports that explain the issues DCT uncovers, suggest mitigations, and provide references to supporting publications.

DCT is intended to provide customers with easy-to-use self-service configuration analysis so that their installations are more robust and experience better performance.

Today I wanted to show this tool to a new administrator and ran a scan. After the scan completed, I reviewed the result and saw this entry:

NagleOFF1

Well, ok, so let us do what is recommended …

After a new scan I found this entry in the scan results:

NagleOFF2

Huh!! How confusing is this?

I have seen this in an earlier version of DCT, but before I ran the first scan, I updated both, the rules and the design of the DCT database.