g controls to fairly large nested Java Objects. Other than
>> making sure to use LoadableDetachable models where possible are there any
>> other strategies for making sure performance is optimal? For example,
>> would
>> setting the model on the form rather than on
han
making sure to use LoadableDetachable models where possible are there any
other strategies for making sure performance is optimal? For example, would
setting the model on the form rather than on each control have any
performance benefit?
Thanks
--
View this message in context:
http://apache
> would
> setting the model on the form rather than on each control have any
> performance benefit?
>
> Thanks
>
>
>
> --
> View this message in context:
> http://apache-wicket.1842946.n4.nabble.com/Model-performance-question-tp4659771.html
> Sent from the U
on each control have any
performance benefit?
Thanks
--
View this message in context:
http://apache-wicket.1842946.n4.nabble.com/Model-performance-question-tp4659771.html
Sent from the Users forum mailing list archive at Nabble.com.
---
On Sun, 25 Jan 2009, Johan Compagner wrote:
> I guess wicket should dump the page serialized size in development
> mode. So that users see them when developing.
Yep, we have in one project debug logging doing just that so
you more or less notice right away when something starts to
hog memory.
I'v
I guess wicket should dump the page serialized size in development
mode. So that users see them when developing.
On 21/01/2009, Michael O'Cleirigh wrote:
> Hello,
>
> A big delay in refreshing can be a sign that your pages are serializing
> your domain object graph as part of the page serializati
rkablePage[com.neobits.web.pages.Index],resp
>>>>>> onse=BookmarkablePage[com.neobits.web.pages.Index],sessionid=729B1C0D58665D15518
>>>>>> 044E5C8A63088.jvm1,sessionsize=1177,sessionstart=Mon Apr 14 14:38:51
>>>>>> PDT 2008,re
>>>>
before getting top nav menuitems 1208209878458
>>>>> ! after getting top nav menuitems 1208209878696 time
>>>>> taken 238
>>>>> 2008-04-14 14:51:25,266 (http-0.0.0.0-8080-Processor4) [
>>>>> RequestLogger.java
>&g
obits.web.pages.Index],sessionid=729B1C0D58665D1551804
>>>> 4E5C8A63088.jvm1,sessionsize=1177,sessionstart=Mon Apr 14 14:38:51 PDT
>>>> 2008,requ
>>>> ests=5,totaltime=35360,activerequests=3,maxmem=532M,total=266M,us
51 PDT
>>> 2008,requ
>>> ests=5,totaltime=35360,activerequests=3,maxmem=532M,total=266M,used=55M
>>>
>>> ! before getting top nav menuitems 1208209893292
>>> ! after getting top nav menuitems 1208209893526 time
>>> taken 23
Hello,
A big delay in refreshing can be a sign that your pages are serializing
your domain object graph as part of the page serialization process. In
my case it turned out that my AJAX autocompleting search page was
serializing a 50MB in memory index on each update.
I would investigate usin
ter getting top nav menuitems 1208209893526 time
>> taken 234
>> 2008-04-14 14:51:40,514 (http-0.0.0.0-8080-Processor6) [
>> RequestLogger.java
>> :320:INFO ]
>> time=7309,event=BookmarkablePage[com.neobits.web.pages.Index],respon
>> se=BookmarkablePage[com.neobits.
ookmarkablePage[com.neobits.web.pages.Index],respon
> se=BookmarkablePage[com.neobits.web.pages.Index],sessionid=729B1C0D58665D1551804
> 4E5C8A63088.jvm1,sessionsize=1177,sessionstart=Mon Apr 14 14:38:51 PDT
> 2008,requ
> ests=6,totaltime=42669,activerequests=4,maxmem=532M,total=266M,used=
; solve
>> my problem.
>> Could someone knowledgeable more elaborate on this problem/question
>> please ?
>> Thanks very much.
>>
>> Stefan Simik
>>
>>
>
>
--
View this message
chanism (TextTemplateCache) in sources, which could
> solve
> my problem.
> Could someone knowledgeable more elaborate on this problem/question please
> ?
> Thanks very much.
>
> Stefan Simik
>
>
--
View this message in context:
http://www.nabble.com/Templating-%2B-pe
-%2B-performance-question-tp17575292p17575292.html
Sent from the Wicket - User mailing list archive at Nabble.com.
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
arkablePage
[com.neobits.web.pages.Index],sessionid=729B1C0D58665D1551804
4E5C8A63088.jvm1,sessionsize=1177,sessionstart=Mon Apr 14 14:38:51
PDT
2008,requ
ests
=6,totaltime=42669,activerequests=4,maxmem=532M,total=266M,used=46M
--
View this message in context:
http://www.nabble.com/Performance-question-tp166909
,maxmem=532M,total=266M,used=46M
--
View this message in context:
http://www.nabble.com/Performance-question-tp16690935p16690935.html
Sent from the Wicket - User mailing list archive at Nabble.com.
-
To unsubscribe, e-mail: [EMA
1177,sessionstart=Mon Apr 14 14:38:51 PDT
> >> 2008,requ
> >>
> ests=5,totaltime=35360,activerequests=3,maxmem=532M,total=266M,used=55M
> >>
> >> ! before getting top nav menuitems 1208209893292
> >> !!!!! after getting top nav menuitems
; RequestLogger.java
> :320:INFO ]
> time=7309,event=BookmarkablePage[com.neobits.web.pages.Index],respon
>
> se=BookmarkablePage[com.neobits.web.pages.Index],sessionid=729B1C0D58665D1551804
> 4E5C8A63088.jvm1,sessionsize=1177,sessionstart=Mon Apr 14 14:38:51 PDT
> 2008,requ
> ests=6,totalti
top nav menuitems 1208209893526 time
>> taken
>> 234
>> 2008-04-14 14:51:40,514 (http-0.0.0.0-8080-Processor6) [
>> RequestLogger.java
>> :320:INFO ]
>> time=7309,event=BookmarkablePage[com.neobits.web.pages.Index],respon
>>
>> se=Bookmarkab
.0-8080-Processor6) [
> RequestLogger.java
> :320:INFO ]
> time=7309,event=BookmarkablePage[com.neobits.web.pages.Index],respon
>
> se=BookmarkablePage[com.neobits.web.pages.Index],sessionid=729B1C0D58665D1551804
> 4E5C8A63088.jvm1,sessionsize=1177,sessionstart=Mon Apr 14 14:38:51 PDT
[com.neobits.web.pages.Index],sessionid=729B1C0D58665D1551804
4E5C8A63088.jvm1,sessionsize=1177,sessionstart=Mon Apr 14 14:38:51 PDT
2008,requ
ests=6,totaltime=42669,activerequests=4,maxmem=532M,total=266M,used=46M
--
View this message in context:
http://www.nabble.com/Performance-question
23 matches
Mail list logo
