It would be nice to be able to separate this total performance time to sub-costs, otherwise it would indeed difficult to make out something out of that number apart from "performance changed" - which indeed says little, performance changes with every change.
On 10 June 2015 at 13:38, Sergey Sharybin <[email protected]> wrote: > I didn't say it's difficult, i only mentioned that it is to be thought much > more careful defining which exact information is useful for us and how to > gather it. > > On Wed, Jun 10, 2015 at 1:25 PM, Campbell Barton <[email protected]> > wrote: > >> Hi Martijn, think its fine to have more comprehensive performance tests >> (which can include extending, bpy.ops.wm.redraw_timer or add related >> operators to give more comprehensive info). >> >> This seems like 2 separate projects, >> >> - ability to perform tests and collect feedback. >> - extend existing performance tests. >> >> Second needs review of each kind of test added, but that can be done >> on case-by-case basis, to see whats really useful to measure. >> >> >> Ability to execute operators directly from command line is handy, >> uploaded patch. >> https://developer.blender.org/D1347 >> _______________________________________________ >> Bf-committers mailing list >> [email protected] >> http://lists.blender.org/mailman/listinfo/bf-committers >> > > > > -- > With best regards, Sergey Sharybin > _______________________________________________ > Bf-committers mailing list > [email protected] > http://lists.blender.org/mailman/listinfo/bf-committers _______________________________________________ Bf-committers mailing list [email protected] http://lists.blender.org/mailman/listinfo/bf-committers
