On 18-Apr-2013 06:08, Nicolas Dufour wrote:
I've just noticed the tweak tool is very slow, far slower than the select tool. Moving the tweak cursor, even with a blank new document maximized, can take up to half a second if the window is maximized.
This may be hideously painful to do in practice, but since there is a gprof in mingw, in theory you could locate the section of code which is now slow. Maybe. Change the compile flag to use -pg -g -O0 and build fast and slow versions of Inkscape. Run them, and carry out exactly the same sets of operations in each. In between copy the gmon.out file to some other name, so a subsequent run does not overwrite it. Then analyze the gmon.out files with gprof. If you are really, really lucky, then some particular method will jump way up the 'time used' list, possibly even with line numbers.
Based on my own past results with gprof I estimate this method has about a 25% chance of showing something useful. If I had to guess the slow down is actually taking place in a library used by inkscape, and not in inkscape itself. That was the situation with the 15% CPU issue. gprof won't show anything useful about the contents of those libraries unless you rebuild them with -pg, which may be very hard to do. The method is unlikely to show you exactly where the issue is, because it is not good at measuring (huge iterations ) X (tiny times), but numbers one or two levels up, where this integrated time can be measured, may give you a clue where the problem is.
Regards,
David Mathog mathog@...1176... Manager, Sequence Analysis Facility, Biology Division, Caltech