Re: Performance question

[Michael O'Cleirigh]

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 using Detatchable models or for example storing the 
data in spring beans injectable using the @SpringBean annotation since 
in that case only the spring proxy is serialized not the
contained domain objects.

You could also put a breakpoint within the wicket page serialization 
process to try and see how big the serialized page is.

Mike
Did you ever determine the cause?  I am having a similar problem, it is not
acceptable.  



Ritesh Trivedi wrote:
  
Hi,

I have created first couple of pages of my wicket application but have
some performance concerns.

The pages (even the refresh alone takes 6-7 secs on Dual Core 2.2GHz
Pentium with 4GB of RAM). DB is located on the remote host, but has
caching at the application server - so thats not adding to the latency for
the refresh. Here is the requestlogger information for the home page
refresh couple of times

Can someone point me to the direction on going about finding out what is
taking this long other than (and may be simpler than) running a profiler
on the application - atleast initially.

My application is running in deployment mode and is running in tomcat.

=====

!!!!!!!!!!!!!!!!! before getting top nav menuitems 1208209856242
!!!!!!!!!!!!!!!!! after getting top nav menuitems 1208209860972 time taken
4730
2008-04-14 14:51:07,677 (http-0.0.0.0-8080-Processor12) [     
RequestLogger.jav
a:320:INFO ]
time=11567,event=BookmarkablePage[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
quests=4,totaltime=28472,activerequests=3,maxmem=532M,total=266M,used=56M

!!!!!!!!!!!!!!!!! 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
:320:INFO ]
time=6888,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=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
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.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