[cairo] performance of cairo in a larger application

Carl Worth cworth at east.isi.edu
Tue Jul 27 07:15:36 PDT 2004

On Thu, 17 Jun 2004 01:58:25 +0200, =?ISO-8859-1?Q?=D8yvind_Kol=E5s?= wrote:
> The application is usable when using glitz, apart from a small issue
> when closing[6], but during use it is fantastic. Is there any part of
> the code in the stack of the xlib/xrender based backend that could use
> a couple of eyeballs?


As you've noticed, there are still quite a few spots where cairo needs
to be faster. We'll get there, but I am glad that you have found it to
be usable in the meantime.

I'm still focusing on correctness and completeness, so profiling and
optimization will come later. But, I do have a couple of thoughts right

1) Keith and I are involved in a rewrite of the tessellation and
   rasterization stages right now. We're doing this to make it correct
   and more robust, but it looks like the new version will also be a
   fair amount faster.

2) I don't know if you are using clipping, but if you are then you know
   it is dog slow. Keith says that what's missing there is an
   accelerated implementation of the IN operator, (which he also claims
   wouldn't be too much work). So if somebody wants to take a look at


More information about the cairo mailing list