[cairo] Text Grid Performance

[Gerdus van Zyl]

(For future newb reference)
I just learned how to make dll files smaller, it's called a little
utility called strip. My dlls are now the same size as the ones from
gtk.org, so i'm happy. By examining the makefile ( CFLAGS )  it looks
like debug info is always there (gcc -g) and also optimize more (gcc
-O2).
So by using strip to remove the debugging info you basically get a
release dll. I suppose messing with compiler options won't yield much
improvement, else they would be there already.
I may be wrong on all the above, i'm new to this :-]

~g

On Feb 6, 2008 9:52 PM, Gerdus van Zyl <gerdusvanzyl at gmail.com> wrote:
> No i'm using the 1.5.8 snapshot that does not include any
> Makefile.win32 files. How are they different? or are they for the
> Microsoft compilers? I would recommend adding to the INSTALL file
> explaining that.
>
> ~g
>
>
> On Feb 6, 2008 8:26 PM, Antoine Azar <cairo at antoineazar.com> wrote:
> >
> > >I finally got a cairo build env working today - mingw/msys. :-) Is it
> > >documented anywhere how to compiler optimize and minimize the DLL
> > >built? How does one invoke a release or debug build? Sorry I am a
> > >total C build system newbie.
> >
> > Hey Gerdus,
> > are you using the Makefile.win32 files? if so, they don't have
> > different build configurations, but you can tweak the parameter
> > switches given to the compiler. You'll have to rebuild everything
> > everytime you switch from one config to the other though.
> > I modified those makefiles to properly support debug and release, but
> > I still need to land that patch. It should arrive shortly, otherwise
> > I can send you my makefiles by email.
> >
> > Antoine
> >
> >
> >
> > >~Gerdus
> > >
> > >On Feb 6, 2008 5:37 PM, Gerdus van Zyl <gerdusvanzyl at gmail.com> wrote:
> > > > Alternatively I need to only draw that part of the screen that can be
> > > > done within the timeframe as in partial rendering. Does anyone have a
> > > > design pattern for that?
> > > >
> > > > ~G
> > > >
> > > >
> > > > On Feb 5, 2008 8:42 PM, Gerdus van Zyl <gerdusvanzyl at gmail.com> wrote:
> > > > > Ok, thanks for the feedback. Firstly I am on windows (windowsXP),
> > > > > 2.4ghz amd, ati radeon 9500. I am using the win32 backend.
> > > > >
> > > > > In the text-scroll.py program Owen attached I get: 100 frames in
> > > > > 7480.99994659 ms, 13.3671969942 FPS, which is fairly consistent with
> > > > > my previous results considering event handling/reflow overhead.
> > > > >
> > > > > The clip is a rectangle and so far I know device-pixel aligned (I
> > > > > don't use scale and all x,y,width,height is int). Tested
> > > > > identity_matrix but made no difference.
> > > > >
> > > > > Top functions by cumulative time is:
> > > > > ncalls  tottime  percall  cumtime  percall filename:lineno(function)
> > > > > 67    1.280    0.019   20.128    0.300 platformwin32c.py:384(OnPaint)
> > > > > 67    0.399    0.006   18.848    0.281 uxpwindowapp.py:1219(event_paint)
> > > > > 6466/66    2.674    0.000   16.366    0.248
> > > uxpwindowapp.py:1038(_renderone)
> > > > > 6334    6.415    0.001   10.892    0.002 uxbase.py:1079(showText)
> > > > > 6334    0.717    0.000   13.226    0.002 uxlabel.py:15(renderctx)
> > > > > The rendering flow in my program is OnPaint -> event_paint ->
> > > > > _renderone(x250) -> renderctx -> showText. Which to my eye looks like
> > > > > cairo being the bottleneck.
> > > > >
> > > > > Thanks.
> > > > > ~Gerdus
> > > > >
> > > > >
> > > > >
> > > > > On Feb 5, 2008 7:49 PM, Vladimir Vukicevic <vladimir at pobox.com> wrote:
> > > > > >
> > > > > > On Feb 5, 2008, at 7:10 AM, Gerdus van Zyl wrote:
> > > > > > >
> > > > > > > My text rendering for each element is basically:
> > > save,clip,render text
> > > > > > > using pango,restore
> > > > > >
> > > > > > Just off the top of my head -- is the clip a rectangle, and if so, is
> > > > > > it device-pixel aligned?  If not, that could account for the
> > > > > > performance that you're seeing.
> > > > > >
> > > > > >      - Vlad
> > > > > >
> > > > > >
> > > > >
> > > >
> > >_______________________________________________
> > >cairo mailing list
> > >cairo at cairographics.org
> > >http://lists.cairographics.org/mailman/listinfo/cairo
> >
> >
>