[poppler] pdf rendering performance on the olpc test boards

Jeff Muizelaar jeff at infidigm.net
Tue Nov 7 17:22:03 PST 2006


On Tue, Nov 07, 2006 at 12:46:28PM -0500, Jeff Muizelaar wrote:
> On Tue, Nov 07, 2006 at 06:11:50PM +0100, Tomeu Vizoso wrote:
> > After some profiling of page rendering on the board with sysprof, this
> > functions appeared using 45% of CPU time:
> > 
> > _XcmsLookupColorName
> > _XcmsSetGetColors
> > _XcmsInitScrnInfo
> > _XcmsResolveColorString
> 
> I have never seen these functions at the top of a profile. I wonder what
> is causing them to be there?
> > 
> > We are currently using the 0.5.4 version with the cairo backend. The
> > processor on the board is a Geode GX-500 [2], the floating point
> > performance of which is quite poor. Composition is currently done by
> > software.
> > 
> > Does this info make some sense to anybody? Is poppler who is eating our
> > CPU or should we look elsewhere? Can you recommend any compilation
> > options that could improve performance?
> > 
> > I can send the sysprof file, if anyone is interested in giving a look.
> 
> I'd be interested in the sysprof file.

It doesn't look like you are profiling the right thing. The sysprof you
gave me doesn't seem to have anything to do with poppler. i.e. The
functions you listed above are called by gobject_message_function by a
python program.

-Jeff


More information about the poppler mailing list