new browser windows slower than first one

Hello,

just noticed a scroll performance-related problem:
When I create many browser windows (e.g. using the middle
mouse
button), srolling in these created windows causes more Xorg
CPU
usage than in the first one.
Maybe, scrolling in the new windows causes redraws from the
old
ones?

  Johannes

_______________________________________________
Dillo-dev mailing list
Dillo-devdillo.org
http://lists.auriga.wearlab.de/cgi-bin/mailman/
listinfo/dillo-dev

On Sat, Oct 20, 2007 at 08:14:47PM +0200, Johannes Hofmann
wrote:
> Hello,
> 
> just noticed a scroll performance-related problem:
> When I create many browser windows (e.g. using the
middle mouse
> button), srolling in these created windows causes more
Xorg CPU
> usage than in the first one.
> Maybe, scrolling in the new windows causes redraws from
the old
> ones?

Argh, fltk2 uses double-buffering by default. This uses
quite some
memory on the X-server side and slows things down.

--- a/src/ui.cc Sat Oct 20 17:59:33 2007 +0200
+++ b/src/ui.cc Sun Oct 21 14:47:49 2007 +0200
 -580,6
+580,7  UI::UI(int win_w, int win_h, const char*
 {
    int s_h = 20;
    resizable(this);
+   clear_double_buffer();
    begin();
      TopGroup = this;


switches double-buffering off. This makes quite a difference
for
scrolling here. However during rendering there is some
flicker now.
But the excessive redraws that cause the flicker should be
addressed anyhow.

  Johannes

_______________________________________________
Dillo-dev mailing list
Dillo-devdillo.org
http://lists.auriga.wearlab.de/cgi-bin/mailman/
listinfo/dillo-dev

Hi,

On Sun, Oct 21, 2007 at 03:35:49PM +0200, Johannes Hofmann
wrote:
> On Sat, Oct 20, 2007 at 08:14:47PM +0200, Johannes
Hofmann wrote:
> > Hello,
> > 
> > just noticed a scroll performance-related
problem:
> > When I create many browser windows (e.g. using the
middle mouse
> > button), srolling in these created windows causes
more Xorg CPU
> > usage than in the first one.
> > Maybe, scrolling in the new windows causes redraws
from the old
> > ones?
> 
> Argh, fltk2 uses double-buffering by default. This uses
quite some
> memory on the X-server side and slows things down.
> 
> --- a/src/ui.cc Sat Oct 20 17:59:33 2007 +0200
> +++ b/src/ui.cc Sun Oct 21 14:47:49 2007 +0200
>  -580,6 +580,7  UI::UI(int win_w, int win_h, const char*
>  {
>     int s_h = 20;
>     resizable(this);
> +   clear_double_buffer();
>     begin();
>       TopGroup = this;
> 
> 
> switches double-buffering off. This makes quite a
difference for
> scrolling here. However during rendering there is some
flicker now.
> But the excessive redraws that cause the flicker should
be
> addressed anyhow.

  Commited! This is will be very good for debugging screen
updates.


  Those not working in it can comment it out in src/ui.cc:
    +   //clear_double_buffer();

-- 
  Cheers
  Jorge.-

_______________________________________________
Dillo-dev mailing list
Dillo-devdillo.org
http://lists.auriga.wearlab.de/cgi-bin/mailman/
listinfo/dillo-dev

On Sun, Oct 21, 2007 at 03:35:49PM +0200, Johannes Hofmann
wrote:
> switches double-buffering off. This makes quite a
difference for
> scrolling here.

Scrolling an empty page at fullscreen now consumes 1.5% CPU
load
and not 100% as before. Fantastic!!! If the page has
content,
it's considerably more (at least 20%), most likely because
of
the many unneccessary redraws.

Cheers,
-- 
Matthias Franz

_______________________________________________
Dillo-dev mailing list
Dillo-devdillo.org
http://lists.auriga.wearlab.de/cgi-bin/mailman/
listinfo/dillo-dev

Turning off double buffering means that the default code
from the tree
is unusably slow and annoying on my ancient(*) computer.
This might dissuade
someone who comes along at the wrong time intending to give
the fltk dillo
a look.

Though admittedly it might be my configuration...


* Computers never get slow; software gets slow!
 

_______________________________________________
Dillo-dev mailing list
Dillo-devdillo.org
http://lists.auriga.wearlab.de/cgi-bin/mailman/
listinfo/dillo-dev

Hi,

On Mon, Oct 22, 2007 at 06:39:09PM +0000, place wrote:
> Turning off double buffering means that the default
code from the tree
> is unusably slow and annoying on my ancient(*)
computer. This might dissuade
> someone who comes along at the wrong time intending to
give the fltk dillo
> a look.
> 
> Though admittedly it might be my configuration...

  I'll try to check this on wednesday, in a slow machine.


> * Computers never get slow; software gets slow!

  TRUE.

-- 
  Cheers
  Jorge.-

_______________________________________________
Dillo-dev mailing list
Dillo-devdillo.org
http://lists.auriga.wearlab.de/cgi-bin/mailman/
listinfo/dillo-dev