Get started Bring yourself up to speed with our introductory content.

Troubleshooting a slow Lotus Domino Server

Our server is slow. So far restarting the server is the only effective way to get it to speed. We restart the server on Sundays. It is fine up to Wednesday and starts to slow down. By Friday it gets very slow to the point that the backup that usually finishes at 8:00 am won't even be done by noon. Some mornings we come to the office to find that the server crashed around 2:00 am and even the operating system is not responsive. We are running Domino 6.5.3 on Windows 2000, with 2.5GB of memory, and we have about 500 Notes client users.

View member feedback to this Ask the Expert Q&A.

You definitely have a problem. Domino should run for 100+ days with no errors at all. You need to use some of the analysis tools built into the Domino Admin console, or within Win2000 to see what is happening. I suspect a memory leak.

Start by shutting down every server task that is non-essential and removing every third-party product from the Domino box. If that helps, you have found (or narrowed down) the source of the problem.


I have experienced the same issue and each time it was replication of a large database. If you have a database with lots (1 million+) of documents in it, then Domino 'seems' to have to generate a list of every document in the database when it replicates, eventually both Domino and the windows on the server stop responding, as if the server has run out of resources. We fixed this by having the ini setting restrict the percentage of available resources that Domino may use. This allows Domino and the TCIP stack to respond, but does not fix the underlying issue of replication of large databases.

Also (just to check the simple stuff) check that your Quick edit and Insert mode are deselected, as although the server seems to be okay, clicking in the server window pauses the console, and eventually, bit by bit, Domino stops responding.

—Brian S.


We have a similar issue with Domino 6.5.3 on WIndows NT 4.0 and one on Windows 2003. If you normally keep the Domino window maximized, it leaks memory. Pull up Task Manager and look at the amount of memory being used. Now minimize Domino and watch the amount of memory drop, sometimes by hundreds of MBs. If we maximize and minimize the Domino window every morning (and keep it minimized), we seem to have a lot less issues with the server being sluggish than if we left it alone. We now only reboot the server once a month. However, we'll be going to 6.5.4 soon, and I'm not sure if this will correct the problem.

Overall, this seems to be a bigger problem on our hub than on the mail server, although the hub does have more processes running, such as a virus scanner. The memory leak is definitely there.

—Harold G.


The suggestion by Brian S. will solve the problem mentioned by Harold G.

—Doug J.


The problem mentioned by Harold G. has been reported regarding other applications too: Thus, it seems to be not a problem of Domino at all, but perhaps a problem of the Windows Task Manager reporting wrong values in the Mem Usage column of the Processes window. The drop of memory usage after minimizing the application should be also reflected in the Performance window of the Task Manager, but it doesn't.

—Dietmar D.


That's why we always use Windows Services to launch Lotus and the parameters -jc and -c to have a console.

—F. Maisonneuve

Do you have comments on this Ask the Expert question and response? Let us know.

Dig Deeper on Lotus Notes Domino Performance

  • Favorite iSeries cheat sheets

    Here you'll find a collection of valuable cheat sheets gathered from across the iSeries/ community. These cheat ...