You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@tomcat.apache.org by Javier Gonzalez <ja...@gmail.com> on 2006/06/07 22:20:14 UTC
few "fat" contexts of many "lean" contexts?
Hi,
I'm running a tomcat that provides services for a lot of clients.
Each "client" one has a number of services (via axis) on their "own"
context. Now I'm migratingto a bigger machine, and I got the doubt: is
it better (for performance) to "group as many services as possible by
context", or have each service live in it's own context?
In more general terms, is it better to group as much functionality as
possible per context, or try to separate where it can be done?
Thanks in advance,
--
Javier González Nicolini
---------------------------------------------------------------------
To start a new topic, e-mail: users@tomcat.apache.org
To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
For additional commands, e-mail: users-help@tomcat.apache.org
Re: few "fat" contexts of many "lean" contexts?
Posted by Tim Funk <fu...@joedog.org>.
Duplicate libraries wasting some extra memory is a tiny penalty compared to
being trapped, unable to upgrade web service when another service relies on
the same library(and is incompatible with newer versions). (Or replace
service with webapp)
-Tim
Javier Gonzalez wrote:
> Actually, I don't - this server provides web services only and *very
> small* set of reports pages, so going through the hassle of setting up
> Apache in front of tomcat wasn't deemed to be worth it.
>
> It doesn't have any impact on performance? I would have thought that
> multiple contexts would eventually lead to duplicated libraries which
> would ultimately lead to wasting memory.
>
> Thanks for taking the time to answer my question.
>
> On 6/7/06, Tim Funk <fu...@joedog.org> wrote:
>
>> From a performance point of view - it doesn't matter.
>>
>> From a maintenaince point of view - I prefer many lean clients. That
>> way -
>> if one of them behaves badly - off they go into a new JVM (assuming
>> you have
>> apache in front of tomcat)
>>
---------------------------------------------------------------------
To start a new topic, e-mail: users@tomcat.apache.org
To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
For additional commands, e-mail: users-help@tomcat.apache.org
Re: few "fat" contexts of many "lean" contexts?
Posted by Javier Gonzalez <ja...@gmail.com>.
Actually, I don't - this server provides web services only and *very
small* set of reports pages, so going through the hassle of setting up
Apache in front of tomcat wasn't deemed to be worth it.
It doesn't have any impact on performance? I would have thought that
multiple contexts would eventually lead to duplicated libraries which
would ultimately lead to wasting memory.
Thanks for taking the time to answer my question.
On 6/7/06, Tim Funk <fu...@joedog.org> wrote:
> From a performance point of view - it doesn't matter.
>
> From a maintenaince point of view - I prefer many lean clients. That way -
> if one of them behaves badly - off they go into a new JVM (assuming you have
> apache in front of tomcat)
>
>
>
> -Tim
>
> Javier Gonzalez wrote:
> > Hi,
> >
> > I'm running a tomcat that provides services for a lot of clients.
> >
> > Each "client" one has a number of services (via axis) on their "own"
> > context. Now I'm migratingto a bigger machine, and I got the doubt: is
> > it better (for performance) to "group as many services as possible by
> > context", or have each service live in it's own context?
> >
> > In more general terms, is it better to group as much functionality as
> > possible per context, or try to separate where it can be done?
> >
> > Thanks in advance,
> >
>
> ---------------------------------------------------------------------
> To start a new topic, e-mail: users@tomcat.apache.org
> To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
> For additional commands, e-mail: users-help@tomcat.apache.org
>
>
--
Javier González Nicolini
---------------------------------------------------------------------
To start a new topic, e-mail: users@tomcat.apache.org
To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
For additional commands, e-mail: users-help@tomcat.apache.org
Re: few "fat" contexts of many "lean" contexts?
Posted by Tim Funk <fu...@joedog.org>.
From a performance point of view - it doesn't matter.
From a maintenaince point of view - I prefer many lean clients. That way -
if one of them behaves badly - off they go into a new JVM (assuming you have
apache in front of tomcat)
-Tim
Javier Gonzalez wrote:
> Hi,
>
> I'm running a tomcat that provides services for a lot of clients.
>
> Each "client" one has a number of services (via axis) on their "own"
> context. Now I'm migratingto a bigger machine, and I got the doubt: is
> it better (for performance) to "group as many services as possible by
> context", or have each service live in it's own context?
>
> In more general terms, is it better to group as much functionality as
> possible per context, or try to separate where it can be done?
>
> Thanks in advance,
>
---------------------------------------------------------------------
To start a new topic, e-mail: users@tomcat.apache.org
To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
For additional commands, e-mail: users-help@tomcat.apache.org