Hi all,
I would like to increase performance to domino server, I have to restart weekly to avoid freezing the system. It’s very strange and i cannot point in the correct way.
I’m thinking about in the notes.ini file there are many parameters that are not useful. Anybody can tell me what parameters are essential and which of them aren’t.
Thanks.
Subject: Increase Performance
Hi,
I think it is the wrong place to start - to wipe the notes.ini. I agree that may be a few settings which are needed but the major port is needed - I guess this is why they are there… As well to be able to tweak the server via the notes.ini requires you to know what exactly the parameters do and how e.g they are cal culated. I doubt that if you do this the problem with disappear… You say once a week; why dont you start added some debug on the server to see what actually is going on instead of guessing. Hang every week - agent running every week or antivirus being updated every week? Start by adding thread debug, debug for amgr and semaphores timeouts and make some NSDs. By doing this (maybe increase the debug) you will diffently be able to find out what is causing the server to hang/freeze.
//Kjeld
Subject: RE: Increase Performance
Ok, I agree.But, Could you point me in the correct way to start and manage the debug on the server side?
Thks
Subject: RE: Increase Performance
Hi,
Add following to notes.ini. The debug will first be active after next reboot:
;##################### SEMAPHORE #####################
DEBUG_OUTFILE=debug.txt
Debug_Capture_Timeout=10
Debug_Show_Timeout=1
Debug_ThreadID=1
DEBUG_AMGR=*
Log_AgentManager=1
;#####################################################
this will allow you to debug the amgr and log any semaphore timeouts on the server. Files named debug.txt and SEMDEBUG.TXT will be created. Next time the server hangs will you have to make a full NSD. And then it starts; check the SEMDEBUG.TXT for any processes locking other processes. Locate that process in the debug.txt and NSD and check out what it is doing; who starts it etc (debug.txt) and what the process is doing (NSD).
//Kjeld
Subject: RE: Increase Performance
Thanks a lot.But, one question more.
What are you referring when you say ‘make a full NSD’ ?
Subject: RE: Increase Performance
with full NSD I mean nsd without any parameters. Sometimes can it be usefull with a nsd -info which gives limited information.
//Kjeld
Subject: RE: Increase Performance
Ok, I’ll check.But, Why the domino server takes a lot of memory?
I’ve 2gb of ram, and all processes are taking about a lot of memroy, nserver, nupdate, nsched, nrouter, nmtc, etc…and also cpu.
Then if I don’t restart the load of cpu are in 100%, then it’s imposible to do nothing.
Thks for your support.
Subject: RE: Increase Performance
Domino is “greedy” – it will use up to 2GB of memory and release unused memory to its own pool. That is, there will be plenty of memory available to Domino, but it holds the memory so it doesn’t have to wait for other processes to release memory when it needs it.
Subject: RE: Increase Performance
Yes, I agree, but , are there any solution to prevent it? All the users are complaining to me.
Thks.
Subject: RE: Increase Performance
There are solutions to it. But you have to find the problem before you find the solution…
In the case of a memory leak check the IBM support site for instructions on how to troubleshoot this (nserver -m). You will have to find out what is leaking.
As Stan said, Domino is greedy and will not release/allocate the memory as expected. Study the parameter “PercentAvailSysResources=”. This is mostly used on Unix servers and servers with a large amount of RAM. It might help you in the case (dont ask what it should be said to - read about it and find out the number yourself).
When running Domino on Windows you shouldn’t use the task manager in Windows to look at the memory allocation - it tells you nothing! Enable the performance monitor which comes with Windows, and set it to log the memory allocation - verify if you see an encrease of the memory allocation and what process is doing it.
Have you collected some debug on the server? Again, weekly problems points very much to problems with antivirus or agents - Java agents are very easy to get leaking…
//Kjeld