Topic: server-manager too slow

[james]

I have a p133 with 80Mb RAM, and access to the server manager is painfully slow! my client is connected to the server at 100Mbit/s. Does anyone have any tips for speeding up the server-manager CGI, other than upgrading hardware? I can add more RAM if that will help.

james.

[Greg Zartman]

(From Mitel Website)

Minimum System Requirements:

400Mhz PCI-based Pentium-class processor,
128MB or RAM,
etc,
etc,
etc.

OK, now you tell me what your best course of action should be to speed things up???

Greg Zartman

[james]

well according to http://edocs.mitel.com/ a cat 1 server with use of server manager needs 90Mhz minimum! Obviously the manager would run quicker if I upgraded the cpu, but I was hoping for a more inspired answer! e.g. optimising apache even further for CGI execution. Does the CGI use mod_perl?

[james]

well, it seems i may have an answer to my own question after all! I have found a guide to enabling mod_perl for SME 5.x

http://www.leiinc.com/repository/Linux/Mitel_SME_Server/HowToGuides/mod_perl-howto.htm

I'm going to port server manager CGI to mod_perl so hopefully it will be noticably quicker not having to fire up perl for each script. I'll post the results after this weekend... would be interested to know if anyone has altready tried this.

[Shad Lords]

The problem with doing this is all mod_perl scripts run with the userid of the webserver.  Most (All?) of the server-manager scripts need to run as other users and so porting them to mod_perl although a good idea will more than likely fail.

-Shad

[Michael Smith]

More RAM certainly won't hurt anything, and maybe you can find a 200 MHz Pentium around for $10 or so.  One of my test boxes is a trusty old AST Bravo Pentium 200 w/192 megs of RAM and I don't die of boredom waiting for Server Manager to come up.

As a matter of fact:

http://www.computersurplusoutlet.com/showproduct.asp?category=4&subcategory=11

Good luck!  I should note that the Bravo functions perfectly adequately as a file server for small networks; I dropped it in as an emergency stopgap server for a 25-node network and *nobody complained*, even running two multi-user Access databases!  Plus the machine was acting as a gateway/router and handling email.  Too bad they insisted on having their Exchange server back after I fixed it.

[james]

Hi everyone just wanted to thank you for your comments on my question. I'm still looking into mod_perl for the server-manager when i get time.

thanks

[Charlie Brady]

james wrote:
 
> Hi everyone just wanted to thank you for your comments on my
> question. I'm still looking into mod_perl for the
> server-manager when i get time.

This suggests to me that you haven't fully digested Shad's point above. The problem he has identified is far from trivial.

Charlie