Debugging Slow Performance in iManager on NetWare



A Forum reader recently asked:

"I have iManager 2.6 SP3 running on a Linux box (OES SP2) and on a NetWare Box (OES SP2). The difference in speed is like night and day. How can I get the NetWare iManager up to speed, or better yet, what's slowing it down? Rendering the Login Page takes from 15-30 Seconds. Logging on can take up to 5 minutes. The NetWare machine does nothing else, just iManager. It has 2GB RAM and a 5GB SYS, which has 3GB free."

And here's the response from Marcel Cox ...


While iManager on NetWare is typically slower than on Linux, that should not lead to such extreme slowness you reported. For instance, a 5-minute login sounds like a serious configuration issue and not like a platform platform in general. In my experience, there are two things that can potentially cause long delays at login time:

1) Name resolution. iManager infortunately has its own name resolution code and does not always user your system settings, especially for SLP name resolution. This means that if you login with your tree name, depending on your environment, iManager can sometimes waste up to a minute trying to resolve your tree name. In this case, entering the IP address of a server with a replica will eliminate this delay caused by bad name resolution.

2) Sometimes an RBS configuration can cause iManager to scan the whole tree at login. If you have a big tree with replicas on remote sides, this can sometimes cause extreme slowdown at login. To debug whether you have an RBS related problem, try disabling rBS altogether by adding the following to your config.xml file in sys:\tomcat\4\webapps\nps\WEB-INF -


For further debugging, enable maximum logging in iManager.


How To-Best Practice
Comment List