We have been having headache after headache since the upgrade to 6.5 Following the normal upgrade path, upgrading the server first then the clients. Because of the problems with the server crashing that I have posted before, further upgrades are on hold. So here we sit and now we have users complaining about how much slower their calendars load in particular, but also mail can be very slow.
On the server namgr.exe has been totally monopolizing CPU usage to the point of 100% for minutes at a time. As noted by those with memory leak issues (which are also happening to us) The issue can somewhat be resolved by minimizing the console window. (I have also added the lines ppl suggested for memory leaks in this forum, but cant reboot until later tonight.)
Minimizing the window seems to allow memory to be released and eventually the namgr.exe will let go of the CPU. It still pegs it for minutes on end at 100% though, but unlike with the console window open it will release it again. Is there anything different in this release that would cause such a bottleneck? Is there a better fix than making sure the console is minimized?
The other issue is that with the calendars of those who have not had thier client upgraded, about 95%, we are noticing that the calendar view is behaving erratically (4.6.7a template). I.e. All events showing up on the current day regardless of thier actual date. This doesnt seem to affect all users or perhaps we only see it in those that really use thier calendars. Mostly the copying over of the $Calendar view from a good copy seems to work.
***Odd though even copying that same view into the template and doing a file replace design does NOT work.
This server in its 4.6.7a state ran flawlessly for 2 1/2 years but I have had to spend 300% more time on it in the past month than in those 2.5 years and its driving me nuts.
Subject: RE: NAMGR.EXE monopolizing the CPU - More 6.5 upgrade woes
The agents that are running are agents in users mail files (mostly anti spam i.e. delete msgs with “Viagra”) While we are working on consolidating our anti spam efforts,we are leaving the existing rules in place util we are sure they arent needed. This seems to be an undocumented feature in Notes 6 that if you don’t Full Text Index any database that you run ANY agent on, whether it needs it for selection or not it will run like a dog all the time. After FTI every stupid DB (adding a gig of storage space) it seems to have tamed namgr.exe. Updater now is using much more CPU but nowhere near what amgr was. This worked absolutely fine in 4.6.7a without indexing and using all that wasted disk space!!!
Subject: RE: NAMGR.EXE monopolizing the CPU - More 6.5 upgrade woes
“The agents that are running are agents in users mail files (mostly anti spam i.e. delete msgs with “Viagra”)”
I am not sure what the agent problem is, but get those agents doing the anti spam stuff off the server, setup server based mail filtering, or switch to mail rules on the clients. I am on 6.5 from a 4.6.7a upgrade and noticed a significant improvement in performance from the same issue (antispam stuff as agents).
Subject: RE: NAMGR.EXE monopolizing the CPU - More 6.5 upgrade woes
From what I can tell there is no performance gain on rules vs agents, but as for the filtering, I havent found much in the way of content filtering, but I have enabled some of the blocking features. This still has the requirement for running an agent or a filter. I will try to test to see if there is an performance gain using rules over agents. Right now the indexing seems to have alieviated the problem, but i dont really want to index every mail file on the server.
Subject: RE: NAMGR.EXE monopolizing the CPU - More 6.5 upgrade woes
The problem is doing a full text search on a databases that are not full text indexed. I read an explanation in this forum from one of the developers that it creates a temporary index on the fly every time this happens. By the way, I get the following message on my server console when this happens:
"Warning: Agent is performing full text operations on database 'test.nsf' which is not full text indexed. This is extremely inefficient."
Subject: RE: NAMGR.EXE monopolizing the CPU - More 6.5 upgrade woes
I get what you are saying, but my point is that in 4.6x we had no such performance hits, so the “undocumented feature” introduced is most unwelcome if the same configuration cannot perform as well on an R6 server. Surely a mandate that you must fti all dbs to run agents was not a listed requirment to upgrade. I will now need approximately 20-30% more disk space on my server to serve up the same mail files.
The real shame of it is that >5% of my users will ever even use the FTI to actually search their mail files. This is a lot of overhead and cost that Lotus was not upfront about.