Limiting PageStore size

[Neil Curzon <ne...@gmail.com>]

Hi all,

We're in the process of going live with our wicket app, so we're trying to
figure out certain details, currently PageStore size.

I notice that by looking at the page store on disk, typically our pages add
10-20kb each to the pagemap. The default 10mb limit would store a lot of
pages, but we were thinking of using a smaller limit. I tried adjusting the
limit to 100kb, and as expected, the page store size capped out at about
100kb.

I was expecting the consequence of this to be that the back button would not
work all the way to the beginning. Actually, what happens is that, after my
page map size hits the limit and stops growing, even if I continue to click
around the app for a while, I can still hit the back button all the way back
to the login, without hitting our "page expired" page. This surprised me. Is
this expected behavior? If the back button works with a 100kb page map file,
why use a 10mb one?

Any help would be appreciated!

Thanks,
Neil

Re: Limiting PageStore size

[Matej Knopp <ma...@gmail.com>]

It's in the 2.0 in alternate future. Time travel is a tricky thing.

-Matej

On Fri, Dec 11, 2009 at 9:37 PM, Johan Compagner <jc...@gmail.com> wrote:
> did wicket 2.0 had a tardis??
> i am checking svn right now for those lost diamonds!
>
> On 11/12/2009, Igor Vaynberg <ig...@gmail.com> wrote:
>> maybe wicket 2.0 will come with a TardisPageStore :)
>>
>> -igor
>>
>> On Fri, Dec 11, 2009 at 8:56 AM, Neil Curzon <ne...@gmail.com> wrote:
>>> You are right, I was not testing correctly. The pages were just cached and
>>> clicking on any non-bookmarkable link in them caused a page expired.
>>>
>>> Thanks
>>>
>>> On Thu, Dec 10, 2009 at 6:11 PM, Matej Knopp <ma...@gmail.com>
>>> wrote:
>>>
>>>> Are you sure you have been testing it correctly? The pagestore is
>>>> cyclic. That means once it reaches it's limit it's the oldest pages
>>>> get overwritten.
>>>>
>>>> -Matej
>>>>
>>>> On Thu, Dec 10, 2009 at 11:56 PM, Neil Curzon <ne...@gmail.com>
>>>> wrote:
>>>> > Hi all,
>>>> >
>>>> > We're in the process of going live with our wicket app, so we're trying
>>>> to
>>>> > figure out certain details, currently PageStore size.
>>>> >
>>>> > I notice that by looking at the page store on disk, typically our pages
>>>> add
>>>> > 10-20kb each to the pagemap. The default 10mb limit would store a lot
>>>> > of
>>>> > pages, but we were thinking of using a smaller limit. I tried adjusting
>>>> the
>>>> > limit to 100kb, and as expected, the page store size capped out at
>>>> > about
>>>> > 100kb.
>>>> >
>>>> > I was expecting the consequence of this to be that the back button
>>>> > would
>>>> not
>>>> > work all the way to the beginning. Actually, what happens is that,
>>>> > after
>>>> my
>>>> > page map size hits the limit and stops growing, even if I continue to
>>>> click
>>>> > around the app for a while, I can still hit the back button all the way
>>>> back
>>>> > to the login, without hitting our "page expired" page. This surprised
>>>> > me.
>>>> Is
>>>> > this expected behavior? If the back button works with a 100kb page map
>>>> file,
>>>> > why use a 10mb one?
>>>> >
>>>> > Any help would be appreciated!
>>>> >
>>>> > Thanks,
>>>> > Neil
>>>> >
>>>>
>>>> ---------------------------------------------------------------------
>>>> To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
>>>> For additional commands, e-mail: users-help@wicket.apache.org
>>>>
>>>>
>>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
>> For additional commands, e-mail: users-help@wicket.apache.org
>>
>>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
> For additional commands, e-mail: users-help@wicket.apache.org
>
>

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
For additional commands, e-mail: users-help@wicket.apache.org

Re: Limiting PageStore size

[Johan Compagner <jc...@gmail.com>]

did wicket 2.0 had a tardis??
i am checking svn right now for those lost diamonds!

On 11/12/2009, Igor Vaynberg <ig...@gmail.com> wrote:
> maybe wicket 2.0 will come with a TardisPageStore :)
>
> -igor
>
> On Fri, Dec 11, 2009 at 8:56 AM, Neil Curzon <ne...@gmail.com> wrote:
>> You are right, I was not testing correctly. The pages were just cached and
>> clicking on any non-bookmarkable link in them caused a page expired.
>>
>> Thanks
>>
>> On Thu, Dec 10, 2009 at 6:11 PM, Matej Knopp <ma...@gmail.com>
>> wrote:
>>
>>> Are you sure you have been testing it correctly? The pagestore is
>>> cyclic. That means once it reaches it's limit it's the oldest pages
>>> get overwritten.
>>>
>>> -Matej
>>>
>>> On Thu, Dec 10, 2009 at 11:56 PM, Neil Curzon <ne...@gmail.com>
>>> wrote:
>>> > Hi all,
>>> >
>>> > We're in the process of going live with our wicket app, so we're trying
>>> to
>>> > figure out certain details, currently PageStore size.
>>> >
>>> > I notice that by looking at the page store on disk, typically our pages
>>> add
>>> > 10-20kb each to the pagemap. The default 10mb limit would store a lot
>>> > of
>>> > pages, but we were thinking of using a smaller limit. I tried adjusting
>>> the
>>> > limit to 100kb, and as expected, the page store size capped out at
>>> > about
>>> > 100kb.
>>> >
>>> > I was expecting the consequence of this to be that the back button
>>> > would
>>> not
>>> > work all the way to the beginning. Actually, what happens is that,
>>> > after
>>> my
>>> > page map size hits the limit and stops growing, even if I continue to
>>> click
>>> > around the app for a while, I can still hit the back button all the way
>>> back
>>> > to the login, without hitting our "page expired" page. This surprised
>>> > me.
>>> Is
>>> > this expected behavior? If the back button works with a 100kb page map
>>> file,
>>> > why use a 10mb one?
>>> >
>>> > Any help would be appreciated!
>>> >
>>> > Thanks,
>>> > Neil
>>> >
>>>
>>> ---------------------------------------------------------------------
>>> To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
>>> For additional commands, e-mail: users-help@wicket.apache.org
>>>
>>>
>>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
> For additional commands, e-mail: users-help@wicket.apache.org
>
>

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
For additional commands, e-mail: users-help@wicket.apache.org

Re: Limiting PageStore size

[Igor Vaynberg <ig...@gmail.com>]

maybe wicket 2.0 will come with a TardisPageStore :)

-igor

On Fri, Dec 11, 2009 at 8:56 AM, Neil Curzon <ne...@gmail.com> wrote:
> You are right, I was not testing correctly. The pages were just cached and
> clicking on any non-bookmarkable link in them caused a page expired.
>
> Thanks
>
> On Thu, Dec 10, 2009 at 6:11 PM, Matej Knopp <ma...@gmail.com> wrote:
>
>> Are you sure you have been testing it correctly? The pagestore is
>> cyclic. That means once it reaches it's limit it's the oldest pages
>> get overwritten.
>>
>> -Matej
>>
>> On Thu, Dec 10, 2009 at 11:56 PM, Neil Curzon <ne...@gmail.com>
>> wrote:
>> > Hi all,
>> >
>> > We're in the process of going live with our wicket app, so we're trying
>> to
>> > figure out certain details, currently PageStore size.
>> >
>> > I notice that by looking at the page store on disk, typically our pages
>> add
>> > 10-20kb each to the pagemap. The default 10mb limit would store a lot of
>> > pages, but we were thinking of using a smaller limit. I tried adjusting
>> the
>> > limit to 100kb, and as expected, the page store size capped out at about
>> > 100kb.
>> >
>> > I was expecting the consequence of this to be that the back button would
>> not
>> > work all the way to the beginning. Actually, what happens is that, after
>> my
>> > page map size hits the limit and stops growing, even if I continue to
>> click
>> > around the app for a while, I can still hit the back button all the way
>> back
>> > to the login, without hitting our "page expired" page. This surprised me.
>> Is
>> > this expected behavior? If the back button works with a 100kb page map
>> file,
>> > why use a 10mb one?
>> >
>> > Any help would be appreciated!
>> >
>> > Thanks,
>> > Neil
>> >
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
>> For additional commands, e-mail: users-help@wicket.apache.org
>>
>>
>

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
For additional commands, e-mail: users-help@wicket.apache.org

Re: Limiting PageStore size

[Neil Curzon <ne...@gmail.com>]

You are right, I was not testing correctly. The pages were just cached and
clicking on any non-bookmarkable link in them caused a page expired.

Thanks

On Thu, Dec 10, 2009 at 6:11 PM, Matej Knopp <ma...@gmail.com> wrote:

> Are you sure you have been testing it correctly? The pagestore is
> cyclic. That means once it reaches it's limit it's the oldest pages
> get overwritten.
>
> -Matej
>
> On Thu, Dec 10, 2009 at 11:56 PM, Neil Curzon <ne...@gmail.com>
> wrote:
> > Hi all,
> >
> > We're in the process of going live with our wicket app, so we're trying
> to
> > figure out certain details, currently PageStore size.
> >
> > I notice that by looking at the page store on disk, typically our pages
> add
> > 10-20kb each to the pagemap. The default 10mb limit would store a lot of
> > pages, but we were thinking of using a smaller limit. I tried adjusting
> the
> > limit to 100kb, and as expected, the page store size capped out at about
> > 100kb.
> >
> > I was expecting the consequence of this to be that the back button would
> not
> > work all the way to the beginning. Actually, what happens is that, after
> my
> > page map size hits the limit and stops growing, even if I continue to
> click
> > around the app for a while, I can still hit the back button all the way
> back
> > to the login, without hitting our "page expired" page. This surprised me.
> Is
> > this expected behavior? If the back button works with a 100kb page map
> file,
> > why use a 10mb one?
> >
> > Any help would be appreciated!
> >
> > Thanks,
> > Neil
> >
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
> For additional commands, e-mail: users-help@wicket.apache.org
>
>

Re: Limiting PageStore size

[Matej Knopp <ma...@gmail.com>]

Are you sure you have been testing it correctly? The pagestore is
cyclic. That means once it reaches it's limit it's the oldest pages
get overwritten.

-Matej

On Thu, Dec 10, 2009 at 11:56 PM, Neil Curzon <ne...@gmail.com> wrote:
> Hi all,
>
> We're in the process of going live with our wicket app, so we're trying to
> figure out certain details, currently PageStore size.
>
> I notice that by looking at the page store on disk, typically our pages add
> 10-20kb each to the pagemap. The default 10mb limit would store a lot of
> pages, but we were thinking of using a smaller limit. I tried adjusting the
> limit to 100kb, and as expected, the page store size capped out at about
> 100kb.
>
> I was expecting the consequence of this to be that the back button would not
> work all the way to the beginning. Actually, what happens is that, after my
> page map size hits the limit and stops growing, even if I continue to click
> around the app for a while, I can still hit the back button all the way back
> to the login, without hitting our "page expired" page. This surprised me. Is
> this expected behavior? If the back button works with a 100kb page map file,
> why use a 10mb one?
>
> Any help would be appreciated!
>
> Thanks,
> Neil
>

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
For additional commands, e-mail: users-help@wicket.apache.org