Where olpc machine spending time when using web broswer

[Adam Jackson]

On Thu, 2007-03-15 at 14:06 -0700, Carl Worth wrote:
> On Thu, 15 Mar 2007 16:38:05 -0400, Adam Jackson wrote:
> > That Render includes transforms and filters is very nearly academia
> > levels of solipsism.  You just can't make them go fast in software, and
> > we already had a working API for doing them in hardware.  Using Render
> > for untransformed alpha blending is at least reasonable to do in
> > software; Render ought to have stopped there.
> 
> I think getting worked up about the Render interface isn't
> worthwhile. No applications that I'm aware of are coding directly to
> Render---none. The interface that is being used in applications is
> cairo, so all we have to do is make sure that cairo hits the right
> paths.
> 
> And yes, cairo is currently calling into Render for transformations.
> 
> Are you saying that cairo should be using something else instead and
> it will get better performance today? If so, I'm all ears. What should
> I be using instead to make cairo go faster?

I don't think there is a better API, atm.  I think we've reinvented a
lot of GL poorly in Render, but that's not a fight I'm ever likely to
win.

Cairo should probably consider caching the transformed image if the same
image/transform pair is being used repeatedly, and if the transform
operation is sufficiently slow.  At this point in time you can consider
anything besides nearest scaling to be sufficiently slow, since there's
no transform acceleration paths in EXA.

But.  Try nearest scaling first.  It'll probably look fine.

- ajax