Forum .LRN Q&A: Re: Appreciate help with dotLRN performance

Collapse
Posted by Jeff Davis on
AOLserver is multithreaded so what you are seeing is multiple threads in one process, not processes that fail to exit.

Using apache might improve your situation immensely but I doubt it will do so if you intend to run OpenACS.

Collapse
Posted by Shankar Venkatagiri on

Thanks for the pointer, Jeff. I reported the server's response to ps almost 10 minutes after my last interaction with dotLRN. The same processes linger on even now, five hours after I last posted the previous message. Could this indicate un-exiting processes?

I will go ahead and test dotLRN out with apache. I do not, however, seem to understand the distinction between OpenACS and dotLRN. My bad!

Shankar

Collapse
Posted by Jeff Davis on
Neither dotLRN nor OpenACS will work under apache (well, you might be able to fight with mod_aolserver for a few months and get it to run acceptibly but I certainly would not recommend it). I don't really think of dotLRN as being seperate from OpenACS (rather it is a particular install of OpenACS).

You also don't seem to understand the difference between a thread and a process. AOLServer is multithreaded, it creates threads within the server process to handle requests and typically those threads do not go away until the server process exits. ps on linux has the annoying -- not sure if you would call it a feature or a bug -- that it displays threads like they are processes, these don't really take any extra memory than is already taken by the server (note how they are all listed as being the same size and were all created at the same time -- thats because its all just the same server process).