I dropped the CSV file in a google spreadsheet. https://spreadsheets.google.com/ccc?key=0ApsYm0HWlUhPdDluVzd6MnBUbDl3Ni1uYlYxbjRYeVE&hl=en&authkey=CLvQuRI
-Frans On Sun, Sep 26, 2010 at 9:02 AM, Sheet Spotter <sheet.spot...@gmail.com>wrote: > I created a crude profiling tool to determine where to focus on improving > the performance of OpenJPEG v2. > > The profiling tool records the number of function calls and combined > execution time for every function in the main source files (openjpeg.c, > j2k.c, dwt.c, tcd.c, t1.c, mqc.c, and raw.c). > > Results from running the test harness on the 748 files from the > "local_assets" folder were recorded in a CSV (Comma-Separated Value) > format. > The results were placed here: > http://pastebin.com/7K9PCFcB > > The three columns in the file are: > 1. Function name > 2. Number of times the function was called > 3. Combined execution time for the function. > The order the rows appear in the file is not significant. (You can sort the > rows in any order you like after importing the file into a spreadsheet.) > > Enabling the profiling tool definitely distorts the results. Overall > execution time for the test increased from 21 seconds to 129 seconds. > > The crude profiling tool was able to identify where most of the decoding > time is spent. Only a small number of routines are responsible for most of > the execution time. Hopefully this information can lead to improvements in > the performance of the OpenJPEG v2 library. > > > Sheet Spotter >
_______________________________________________ Policies and (un)subscribe information available here: http://wiki.secondlife.com/wiki/OpenSource-Dev Please read the policies before posting to keep unmoderated posting privileges
