Does anyone know how to increase the screen buffer for the Admin server console? I am trying show a mail directory as xml, but a good majority of the output is lost due to the screen buffer size.
Subject: Admin Console Screen Buffer Size
Only click top left hand corner->options. on a 6.5.3 I thought I saw improvements when increasing size from 50->100.
Does anyone know if increase does have any impact and if so, how large is it sensible to have this buffer?
As a standard we of course run with insert/quick edit mode disabled. enabling them may bring your console to a halt, then later also servers (experienced with earlier versions of QP/ST)
Subject: Server Console Screen Buffer Size + more - new observations
Well now, we’ve been pondering over what can at first glance be seen as weird Domino Console behavior. Over time we’ve observed Domino behavior depending on:
a) operative system default settings for DOS prompt/Console window (2000/2003)
b) Operative system console behavior on various Domino versions
c) change of behavior/performance depending on various Console settings (2000/2003)
Case:
It all began with some problems with a 6.5.3 server allocating huge blocks of memory without any sign of user/process /CPU load that comparably. nServer/AMgr and nHTTP grew very fast over time. While this is not a problem when runninng R5/R6 on servers with lots of RAM(>2GB) with lesser ram it could in fact “eat up” most of the resources.
The behavior of the server led to memory allocation growth to a point where Domino/processes began to release memory blocks. As it did, server tasks/processes went into a spin, and server said “not responding” while the memory was being released. This pattern repeated itself in various tempos, depending on a)active threads, no. of users and serving tasks.
NB! On our 6.5.3 servers, number of process handles grows steadily. This will of course lead to a point where windows cannot allocate more handles (because you’re out of range). Letting Domino run till this point can result in Panic Lookup Handle, with total freeze. Then you might find yoruself in a funky position. For at least in all my tests, it’s then almost impossible to kill a server remotely without taking the power.
TIP. I’ve let a Domino/QP server with Task corruption run upto around 75 500 process handles. Don’t know the exact figure but it will eventually crash! Normal on most of our servers are (stable) in the range of 14-23000 handles depending on various circumstances.
Well anyway…I didn’t set up these servers myself from before have two QP208/R508 that has been running VERY stable for over 4 yrs(upgraded over time). So this being so long ago I began to analyse/compare all settings on our QP/Domino cluster with the new servers. Indeed I found a great many things, might be obvious to some but perhaps not all.
Disable of Quick Edit/insert mode, both able to intercept Domino processes and bring server to a stall/halt and/or huge growth of memAlloc. I began to remember some stuff from years back that at least then seemed to resolve abnormal Domino behavior.
- Screen Buffer Size: Where I before mentioned range 100-250, this proved wrong. Settings I used on R508/QP208 4yrs ago was 6055(!). This is a best practise for at least me, or until someone else can offer a better idea. These QP servers have had an uptime >99,98% or higher per anno(we reboot them automatically once per 14 days)
When using this setting, open/closing console doesn’t affect server if you work on it for a while. But pay attention to the growth of allocated mem for primary tasks(!)
Leaving server console open in W2Server seems to cause abnormal growth of RAM. Then one gets the release pattern (See above) with subequent server Hick-ups (flushing blocks). But then again, it may happen with console minimized as well (still checking on that)
Last obervations shows that with >6000 Screen Buffer size setting, I can open/close Server console and see memory released without services/tasks or server being brought to a halt. Open/close of console on Windows causes release instantaneously. Yet I don’t know how release of RAM with work with console minimized or if that will change release behavior pattern (NOT causing server/tasks to go bananas)
I now run with console on server minimized unless I am doing work there. This seems to stabilize memory growth considerably. However, I am not entirely sure of the reason behind the strange release/not responding issues.
I hope that others may have tips, perhaps something that will add a final resolve to the “mysteries” of Domino Live console on the server (not remote).
The Memory growth of the server, and how much it is reported using in Windows task manager I find completely and entirely out of proportions compared to ongoing tasks. Therefore this memo/observation is as much a plead to IBM specialists to present some formulas that may stabilize and resolve at least what we are experiencing.
I know there are several notes.ini parameters that could be applied but have also found some of these “fixes” to provoke other strange things to happen.
Sorry for the length of this memo, but it’s not easy to describe it all with few words, without images. IBM, is it about time that you present something where we can add screenshots etc, attached to the postings???
I have now worked with Domino products for about 9-10 yrs but I am not a certified “specialist”. Yet I have seen a great many things where the general feel is that IBM/Lotus COULD indeed present better guidelines, explanation and/or direction re. things mentioned here.
Additional Note: am investigating how GS (McAfee GroupShield latest release) and NAI/McAfee ver. 7/8 may affect server tasks/performance with various settings + on R5.0.13a+6.5.3. More about this later (when I have time for it). Appreciate contribution from others using any of these versions!
Thanks & Rgds
Knut
Subject: RE: Server Console Screen Buffer Size + more - new observations
I am having the same issue. Any resolution?Thanks,
Dave
Subject: I don’t think you can adjust that buffer.
On the other hand, the -xml output is really meant to be used for programmatic usage, like via a remote console cmd from lotusscript, etc… what are you trying to achieve by “looking” at it in the admin client?
Subject: RE: I don’t think you can adjust that buffer.
Good point Tom. I have found it useful without having to write an LS agent, etc. It seems though that perhaps one will be necessary for more advanced and/or large data grabs, etc.