On Tue, 18 Mar 2003, David Boyer wrote:

> Date: Tue, 18 Mar 2003 14:56:04 -0600
> From: David Boyer <[EMAIL PROTECTED]>
> Reply-To: Tomcat Users List <[EMAIL PROTECTED]>
> To: [EMAIL PROTECTED]
> Subject: 1,900 webapp contexts?
>
> We have about 1,900 students and faculty, and we create web space for
> all of them automatically. I'm interested in Tomcat-enabling their web
> space and have been testing it on a test server. There are approximately
> 1,900 username.xml files in /webapps/.
>

I've never tried it with 1900 users before, but you should check out using
the "User Web Application" special feature documented at:

  http://jakarta.apache.org/tomcat/tomcat-4.1-doc/config/host.html

This tells Tomcat to look at all your users, and make a directory in their
home directory (typically "public_html", similar to an equivalent feature
in Apache) be a webapp.  For me, the webapp context path would be:

  http://localhost:8080/~craigmcc/

> The problem is that it takes Tomcat 15-20 minutes to completely start
> (at 90%+ CPU utilization) as it looks at each xml file in webapps, and
> by then it's using ~200MB. I can give it more memory if needed, but the
> startup time is the real problem.
>

Not having to parse 1900 <Context> elements should help a lot, but you're
still likely to experience a fairly long startup time with this many
webapps.

> Partitioning the webapps across multiple JVMs won't really work since
> each JVM would then have a proportionately smaller chunk of the CPUs.
> I'd hate to use multiple servers since we have plenty of horsepower for
> everything except the startup it seems (2x850MHz PIII's, 1GB RAM).
>
> Are there smarter approaches to this? I've thought about using a just a
> single with the parent of the user webs being the docbase, but how do I
> approach users who want to use their own classes and jars?
>
> Any suggestions are appreciated!
>

Craig


---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to