[Bf-committers] Blender performance measuring instrumentation improvement proposal

[Sergey Sharybin]

Martijn, thinking of something similar to current Debug Timer operator (or
even an extension of it) which will perform some operation N times (N >=
10) and report total/average time on it. The operations could be:

- Viewport draw (which we already have)
- Full scene depsgraph evaluation
- Scene depsgraph evaluation caused by timesource changes
- Specified object evaluation
- Internal datastructures performance testing (similar to ghash performance
tests)
- More extremes, which i'm not really sure how to do in a nice way: Cycles
scene export time, Cycles BVH build time
- Some more stuff which we can define in the future.

IMO goal should be to make all those tests as reproachable as possible and
much independent from external factors as possible. That's why idea of
fps-based thing is something i consider unusable for reliable testing
(since video driver might easily ruing your day with that).

The work from Campbell about making it possible to run given code from a
command line argument is handy, but not totally crucial for performance
framework (since it could all be done in a .py file)


On Wed, Jun 10, 2015 at 1:44 PM, Martijn Berger <martijn.berger at gmail.com>
wrote:

> Hi Sergey,
>
> I agree that the overall timer + playback has limited use cases compared to
> proper full instrumentation of all parts of blender.
> But I don't really suggest it does.
>
> What things would be good to be able to make this thing do in order to
> extract better information?
>
> Martijn
>
> On Wed, Jun 10, 2015 at 1:38 PM, Sergey Sharybin <sergey.vfx at gmail.com>
> 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 <ideasman42 at gmail.com>
> > 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
> > > Bf-committers at blender.org
> > > http://lists.blender.org/mailman/listinfo/bf-committers
> > >
> >
> >
> >
> > --
> > With best regards, Sergey Sharybin
> > _______________________________________________
> > Bf-committers mailing list
> > Bf-committers at blender.org
> > http://lists.blender.org/mailman/listinfo/bf-committers
> >
> _______________________________________________
> Bf-committers mailing list
> Bf-committers at blender.org
> http://lists.blender.org/mailman/listinfo/bf-committers
>



-- 
With best regards, Sergey Sharybin