More of a concern is that every single JSP page gets compiled to a servlet.

This becomes an issue where (as commonly do with ASP here) use JSP for every
page on the site to get say a parameterized include feature, or browser
customization.

You could get the case where the entire Web site would be loaded into
memory, which could become quite unscalable.

It is possible to have JSP pages garbage collectable by giving each its own
classloader, but I don't know if either this method is used by the JSP
engines, or whether a typical runtime uses it effectively.


Tom


Tom Clarke                         665 Broadway
Senior Technical Consultant        New York, NY 10012
AGENCY.COM                         V 212.358.8220 x2798
                                   F 212.982.3105
                                   B [EMAIL PROTECTED]

-----Original Message-----
From: Kirkdorffer, Daniel <[EMAIL PROTECTED]>
To: [EMAIL PROTECTED] <[EMAIL PROTECTED]>
Date: Monday, April 12, 1999 4:58 PM
Subject: Re: Memory concerns


>Interesting question.
>
>I suspect the question comes down to how much memory does a servlet take
up.
>The servlet is always "running" once it has been initialized, but what are
>the memory requirements and does server side garbage collection work its
>magic?  Our systems use the model 2 approach and tend to use multiple
>servlets because we create servlets for specific tasks or specific screens.
>We've never had a concern so far, but I'm interested in what the JSP
>community thinks.
>
>Dan
>--
>Daniel Kirkdorffer
>Sr. Consultant, Syllogistics LLC
>Web:   http://www.syllogistics.com/
>Email: [EMAIL PROTECTED]
>
>
>> ----------
>> From:         Christopher Cobb[SMTP:[EMAIL PROTECTED]]
>> Reply To:     [EMAIL PROTECTED]
>> Sent:         Monday, April 12, 1999 1:08 PM
>> To:   [EMAIL PROTECTED]
>> Subject:      Memory concerns
>>
>> <<File: ccobb.vcf>>
>> I am starting development on a web site that may have a dozen or so web
>> pages.  Since I want these to be login-protected (and I have pretty much
>> concluded that I will have to use an SSI-based approach which requires
>> that all pages be jsp's) I'm going to have a whole bunch of servlets
>> hanging around.
>>
>> (My last applet-based project got away with a single servlet to service
>> all of the applets needs.)
>>
>> Is anyone else concerned that having so many servlets hanging around in
>> memory is going to place undo memory burdens on the web server?
>>
>> Chris
>>
>>
>
>===========================================================================
>To unsubscribe, send email to [EMAIL PROTECTED] and include in the body
>of the message "signoff JSP-INTEREST".  For general help, send email to
>[EMAIL PROTECTED] and include in the body of the message "help".
>

===========================================================================
To unsubscribe, send email to [EMAIL PROTECTED] and include in the body
of the message "signoff JSP-INTEREST".  For general help, send email to
[EMAIL PROTECTED] and include in the body of the message "help".

Reply via email to