Any tips for quick performance analysis on Domino server?
Tags: Lotus Domino Question
I am running Domino 8.5 on a Windows 2003 server inside a vmware image. I suspect that the server is performing somewhat bad... I understand that I can read and learn a lot about real performance analysis - which seems to be an immensely huge area.
At this years Lotusphere I attended Daniel Nasheds presentation "SHOW102 - IBM Lotus Notes and IBM Lotus Domino on Linux 101 ". At the very last slides he presented some screendumps of Linux tools named vmstat and iostat. Just by looking at some of the numbers, he could quickly determine whether a server was "CPU bound" or "IO Bound" - very convenient!!
Does anybody know about similar tools or techniques on Windows servers? Looking at the Task Manager's Performance-tab, I guess I can see similar information, and I hope that someone can point out things like "If Commit Charge is larger than Physical Memory, then you have a problem with too little RAM" ... or something
I am running Domino 8.5 on a Windows 2003 server inside a vmware image. I suspect that the server is performing somewhat bad... I understand that I can read and learn a lot about real performance analysis - which seems to be an immensely huge area.
At this years Lotusphere I attended Daniel Nasheds presentation "SHOW102 - IBM Lotus Notes and IBM Lotus Domino on Linux 101 ". At the very last slides he presented some screendumps of Linux tools named vmstat and iostat. Just by looking at some of the numbers, he could quickly determine whether a server was "CPU bound" or "IO Bound" - very convenient!!
Does anybody know about similar tools or techniques on Windows servers? Looking at the Task Manager's Performance-tab, I guess I can see similar information, and I hope that someone can point out things like "If Commit Charge is larger than Physical Memory, then you have a problem with too little RAM" ... or something
Comments
Posted by Chris Mobley At 15:48:19 On 29.01.2009 | - Website - |
Posted by Robert Ibsen Voith At 15:58:36 On 29.01.2009 | - Website - |
press on the "+" (ok this isn't intuive but we're in in a MS world )
select Disk, then select "Avg Disk queue length", value > 0.7 is bad.
for the CPU/memory use window Task Manager on the server.
Of course you also can add counters on memory /CPU in the perfmon
Posted by Emmanuel Gleizer At 11:45:03 On 01.02.2009 | - Website - |