<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta http-equiv="content-type" content="text/html; charset=ISO-8859-1">
</head>
<body text="#000000" bgcolor="#ffffff">
<small>Hi,<br>
<br>
Currently pixman is used as a lowlevel backend for various
applications.<br>
For doing analysis on performance, it might be desirable to
provide some<br>
performance statistics information to developers.<br>
<br>
The basic idea is based on siarhei's slow-path-reporter. I
extended it to<br>
accumulate information of every composite paths. Final result will
be<br>
shown at the end of the application when destructor is called.
Each paths<br>
are sorted by the amount of time they spent.<br>
<br>
The main purpose of this utility is to profile cairo traces. We
can easily<br>
figure out hot spots and real world usage patterns.<br>
<br>
You can see it from here.<br>
<br>
<a
href="http://cgit.freedesktop.org/%7Epodain/pixman/?h=perf_stat">http://cgit.freedesktop.org/~podain/pixman/?h=perf_stat</a></small><br>
<br>
<small>You can give --enable-perf-stat option to configure script to
enable the<br>
performance statistics analyzer. (I'm not sure that this is done
right,<br>
because I'm not familiar with autoconf, but it works anyway)<br>
<br>
</small><small>Is it right or good to include this feature within
upstream? I think other<br>
developers can easily profile their applications and report the
statistics<br>
when they suffer from performance.<br>
<br>
I was thinking of some performance log channel, individual
composite<br>
event is printed though that log channel and statistics analysis
utilities<br>
to retrieve meaningful information from the log.<br>
<br>
All suggestions and comments are welcome.<br>
<br>
--<br>
Best Regards,<br>
Taekyun Kim<br>
</small>
</body>
</html>