I would agree it's not always going to give much mileage. Given that there
is no heavy weight initialization going on with pages I would tend to agree.
The JVM should be able to cope with many 10's of thousands of objects
created & destroyed per sec, more or less system dependent, so long as they
are all young gen objects. And with parallel gc this should result in
minimal effect on an application.
--------------------------------------------------
From: "Martijn Dashorst" <[EMAIL PROTECTED]>
Sent: Sunday, May 18, 2008 12:42 PM
To: <[email protected]>
Subject: Re: Page pooling (for stateless pages)
We are not tapestry 5. :D
Seriously: page pooling is not good for scalabity. You need to apply
locks to prevent multiple threads to access the same instance, etc.
There is a whole lot of additional stuff you need to make this work,
adding complexity for little or quite possibly no gain at all.
Martijn
On 5/18/08, Joel Halbert <[EMAIL PROTECTED]> wrote:
Johan,
Although the pages are stateless, they can still be pooled, and
"re-initialised" (their state cleared out) between requests.
This is indeed what many java servlet containers do with stateless
Servlets.
It is also the a technique used by Tapestry 5 to achieve greater
scalability.
Rgs,
Joel
--------------------------------------------------
From: "Johan Compagner" <[EMAIL PROTECTED]>
Sent: Sunday, May 18, 2008 12:27 PM
To: <[email protected]>
Subject: Re: Page pooling (for stateless pages)
> For stateless pages??
> The whole point of stateless is that they arent kept in the
session/memory.
>
> And pooling pages is not really what you want any way, you can only
> pool then for a single user/sessiion so you would have a pool for
> every session.
>
> And when do you decide to return a pooled page?
>
> On 5/18/08, Joel Halbert <[EMAIL PROTECTED]> wrote:
>
> > Hi,
> >
> > I was wondering whether it was possible to implement "pooling" of
stateless
> > pages? Possibly using a custom PageMap implementation?
> >
> > Although newer JVM's are good at performing GC, pooling is a
> > reasonable
> > additional technique to use for achieving that extra bit of
> > scalability.
> >
> > If anyone has tried to do this, or has any suggestions on the best
> > way
> > forward I'd be really interested to know.
> >
> > Many Thanks,
> >
> > Joel
> >
>
>
---------------------------------------------------------------------
> To unsubscribe, e-mail:
[EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail:
[EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
--
Buy Wicket in Action: http://manning.com/dashorst
Apache Wicket 1.3.3 is released
Get it now: http://www.apache.org/dyn/closer.cgi/wicket/1.3.3
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
