Also see org.apache.wicket.devutils.inspector.RenderPerformanceListener
in wicket-devutils module. Enable it and then check the data with the
DebugBar (org.apache.wicket.devutils.debugbar.DebugBar)
On Sat, Aug 25, 2012 at 2:58 AM, steven.li steven...@skyworthglobal.com wrote:
Enable wicket debug
Enable wicket debug log, it will show the begin render and end render time in
log file.
log4j.logger.org.apache.wicket=debug
--
View this message in context:
http://apache-wicket.1842946.n4.nabble.com/Slow-rendering-tp4395082p4651490.html
Sent from the Users forum mailing list archive at
how to let it render lazily?
--
View this message in context:
http://apache-wicket.1842946.n4.nabble.com/Slow-rendering-tp4395082p4651491.html
Sent from the Users forum mailing list archive at Nabble.com.
-
To unsubscribe,
Hi,
thank you for your input on how to attack my problem... As it turned out,
the simplest way to see where the time is spent, was to override the
render method of various components. I had used onBeginRender and
onAfterRender
before, but they seem to be called asymetrically so I was not able
Hi Jürgen,
I just had a quick glance at the Component and MarkupContainer classes
and if I am not mistaken you should be able to override onRender() and
onComponentTag() which would give you a few more measuring points and
maybe more pointers on where to look further.
HTH, Christian
The
why is your tree rendering all the nodes ahead of time? shouldnt it
render them lazily as they are expanded?
-igor
On Thu, Feb 16, 2012 at 10:50 AM, Jürgen Lind juergen.l...@iteratec.de wrote:
Hi there,
I am currently encountering a problem that I don't know how to attack... We
have
Hi,
as I was saying in the original post, in rare cases the tree degenerates to a
plain
list - i.e a tree with one (hidden) root node and up to 5000 children that are
rendered
at the same time. Please do not ask me, why our customer would want that - it
is how
it is for the time being ;-)
J.
I'm so sorry but i could not understand the question. If it is in server
side than you can instrument it with JProfiler or JxInsight.
If it is on client side dynaTrace can help you or even google chrome
javascript can help you to detect the problem
On Thu, Feb 16, 2012 at 10:42 PM, Jürgen Lind
