You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@wicket.apache.org by dtoffe <dt...@yahoo.com.ar> on 2009/03/12 19:25:19 UTC
Modal Window performance problem
Hi,
I'm having performance problems when opening a modal window. This
problem occurs on a lower end POS touchscreen box (Celeron 900, 512 RAM),
where the modal window takes some 6-9 seconds to open. I've tried in other
lower end machines with better processor and the delay is not so big.
Out of curiosity, I've profiled the modal window javascript with
Firebug, and found that disableFocusElement() in modal.js, line 1374, calls
itself recursively, and in the profiler output it's listed at the top with
1049 calls.
Since the problem occurs mostly only on that machines, I'm not blaming
the javascript code, but I wonder if anyone else has had similar problems
and if there is some way of avoiding the recursive calls.
Almost forgot to say, I'm using Wicket 1.3.5 and Firefox 3.0.7/MSIE 7.0.
Thanks for your comments,
Daniel
--
View this message in context: http://www.nabble.com/Modal-Window-performance-problem-tp22482640p22482640.html
Sent from the Wicket - User mailing list archive at Nabble.com.
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
For additional commands, e-mail: users-help@wicket.apache.org
Re: Modal Window performance problem
Posted by dtoffe <dt...@yahoo.com.ar>.
Just in case it's useful to you, I've tried what you suggested and the
recursive calls doesn't show in the profiler anymore, but the performance in
that box is just as bad.
Even if there might be some room for improvement, in this case I blame
the crappy hardware, since the performance is ok in the other machines I've
tried it.
Daniel
Matej Knopp-2 wrote:
>
> Hi,
>
> there is good reason why dissablefocuselement is called. Altough there
> certainly is room for performance improvements. Still, it's
> javascript, so you can replace disablefocuselements in modal window
> prototype with an empty function if you don't need it or it causes you
> problems.
>
> -Matej
>
>
--
View this message in context: http://www.nabble.com/Modal-Window-performance-problem-tp22482640p22543282.html
Sent from the Wicket - User mailing list archive at Nabble.com.
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
For additional commands, e-mail: users-help@wicket.apache.org
Re: Modal Window performance problem
Posted by Matej Knopp <ma...@gmail.com>.
Hi,
there is good reason why dissablefocuselement is called. Altough there
certainly is room for performance improvements. Still, it's
javascript, so you can replace disablefocuselements in modal window
prototype with an empty function if you don't need it or it causes you
problems.
-Matej
On Thu, Mar 12, 2009 at 7:25 PM, dtoffe <dt...@yahoo.com.ar> wrote:
>
> Hi,
>
> I'm having performance problems when opening a modal window. This
> problem occurs on a lower end POS touchscreen box (Celeron 900, 512 RAM),
> where the modal window takes some 6-9 seconds to open. I've tried in other
> lower end machines with better processor and the delay is not so big.
> Out of curiosity, I've profiled the modal window javascript with
> Firebug, and found that disableFocusElement() in modal.js, line 1374, calls
> itself recursively, and in the profiler output it's listed at the top with
> 1049 calls.
> Since the problem occurs mostly only on that machines, I'm not blaming
> the javascript code, but I wonder if anyone else has had similar problems
> and if there is some way of avoiding the recursive calls.
> Almost forgot to say, I'm using Wicket 1.3.5 and Firefox 3.0.7/MSIE 7.0.
>
> Thanks for your comments,
>
> Daniel
>
> --
> View this message in context: http://www.nabble.com/Modal-Window-performance-problem-tp22482640p22482640.html
> Sent from the Wicket - User mailing list archive at Nabble.com.
>
>
> ---------------------------------------------------------------------
> 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