On 9/1/06, Rafael Rodríguez <[EMAIL PROTECTED]> wrote:
El Viernes, 1 de Septiembre de 2006 03:20, escribió: > The only way to really know if your changes make any difference is to > profile the code. When I tried my hands at improving poppler speed, I > was rather surprised at which part were expensive > (http://blog.kowalczyk.info/archives/2006/08/14/performance-optimization-st >ory/). Have those changes been backported to poppler?
No. I've submitted the patches: https://bugs.freedesktop.org/buglist.cgi?bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&bug_status=NEEDINFO&email1=kkowalczyk%40gmail.com&emailtype1=exact&emailassigned_to1=1&emailreporter1=1
> Test program can measure loading time of the whole PDF and rendering > of each page. I run it to verify that I've actually made some speedups > (I usually run it 10 times on the same PDF and use an average time, > after rejecting times that differ too much from average). Thanks a lot, it was what i was looking for :)
You might also be interested in a python scripts that I just wrote for automating performance comparisons. In the past when making performance evaluation of my changes, I would have the reference pdftest.exe without the changes and pdftest.exe with the changes, I would run both several times with -timings flag, import dumped timings into a spreadsheet and calculate averages. Rather time consuming. I wrote a runanddifftimes.py that automates that and just prints the final results (time difference in percent for the loading stage and rendering of each page). It's in sumatra sources (http://blog.kowalczyk.info/software/sumatrapdf/develop.html). -- kjk Sumatra (PDF Viewer for Windows): http://blog.kowalczyk.info/software/sumatrapdf _______________________________________________ poppler mailing list [email protected] http://lists.freedesktop.org/mailman/listinfo/poppler
