Hello all, Let's face it, I think the end users rarely report performance problems in pixman unless the performance is really notoriously bad (and not ignored because "it's software rendering, so it is expected to be slow"). Finding real performance bottlenecks in pixman requires running a profiler and being able to actually interpret its logs.
I wonder if it would make sense to add an extra configure option for the special profiling enabled pixman build which would do: 1. Avoid caching fast path lookup failures 2. Once hitting slow path, record the type of operation, image color formats and image flags. 3. For each unique slow path variant, accumulate the number of times it got hit, the total number of (destination?) pixels which got processed, the total number of scanlines. 4. Once per N minutes, spam into syslog with the current accumulated statistics. If some use cases trigger a lot of pixman slow paths, cairo traces can be obtained for them. -- Best regards, Siarhei Siamashka
signature.asc
Description: This is a digitally signed message part.
_______________________________________________ Pixman mailing list [email protected] http://lists.freedesktop.org/mailman/listinfo/pixman
