Automated performance benchmarks for geometry nodes/modifiers #92969

Open
opened 2021-11-09 19:22:40 +01:00 by Hans Goudey · 7 comments
Member

We should have a way to make sure we avoid performance regressions, and a simpler way to test performance improvements for further work

There is now a system for automated performance benchmarks:

A similar system shouldn't be too hard for modifiers. It should measure the time that the modifier stack takes to run.

We could add many of the files created for Nodevember to have an initial set of "real world" files.

We should have a way to make sure we avoid performance regressions, and a simpler way to test performance improvements for further work There is now a system for automated performance benchmarks: - https://wiki.blender.org/wiki/Tools/Tests/Performance - https://developer.blender.org/diffusion/B/browse/master/tests/performance/tests/animation.py A similar system shouldn't be too hard for modifiers. It should measure the time that the modifier stack takes to run. We could add many of the files created for Nodevember to have an initial set of "real world" files.
Author
Member

Changed status from 'Needs Triage' to: 'Confirmed'

Changed status from 'Needs Triage' to: 'Confirmed'
Author
Member

Added subscriber: @HooglyBoogly

Added subscriber: @HooglyBoogly

Added subscriber: @GeorgiaPacific

Added subscriber: @GeorgiaPacific

Added subscriber: @mod_moder

Added subscriber: @mod_moder

Added subscriber: @Garek

Added subscriber: @Garek

I can give the same way to this:
Addon for automated testing of groups of nodes and modifiers

  • Right now there is no way for this to evaluate the execution time from the api
  • For modifiers, there is no infrastructure to record the running time and output it to the api
  • For automation, at least the ability to set constant fields according to a template is required in order to find out the influence of the field. I think this will be the only option.
    Also, for groups, this would require not only the upper speed measurement, but also the calculation of the operating time of all nodes.
    There is a reason for this - the execution times of nodes do not add up correctly, like the time of parallel processes
    So, for a more reliable result, a separate output would be preferable

I also think that if this addon would create output in the form of text, then it would be more convenient to make charts and tables.
Also, this is a smaller codebase for c++
And such a tool can be used by users
But since the evaluator is being updated now, the structure for logging (new) GeoTreeLog is also changing.
I think when this is completed, it will be possible to pay attention to accessing node logging from the api.
But I'm not sure about modifiers.

I can give the same way to this: Addon for automated testing of groups of nodes and modifiers - Right now there is no way for this to evaluate the execution time from the api - For modifiers, there is no infrastructure to record the running time and output it to the api - For automation, at least the ability to set constant fields according to a template is required in order to find out the influence of the field. I think this will be the only option. Also, for groups, this would require not only the upper speed measurement, but also the calculation of the operating time of all nodes. There is a reason for this - the execution times of nodes do not add up correctly, like the time of parallel processes So, for a more reliable result, a separate output would be preferable I also think that if this addon would create output in the form of text, then it would be more convenient to make charts and tables. Also, this is a smaller codebase for c++ And such a tool can be used by users But since the evaluator is being updated now, the structure for logging (new) `GeoTreeLog` is also changing. I think when this is completed, it will be possible to pay attention to accessing node logging from the api. But I'm not sure about modifiers.

This issue was referenced by 3a41e0f611

This issue was referenced by 3a41e0f611bd8a64df9ce4b93386569d8f0cb498
Sign in to join this conversation.
No Label
Interest
Alembic
Interest
Animation & Rigging
Interest
Asset Browser
Interest
Asset Browser Project Overview
Interest
Audio
Interest
Automated Testing
Interest
Blender Asset Bundle
Interest
BlendFile
Interest
Collada
Interest
Compatibility
Interest
Compositing
Interest
Core
Interest
Cycles
Interest
Dependency Graph
Interest
Development Management
Interest
EEVEE
Interest
EEVEE & Viewport
Interest
Freestyle
Interest
Geometry Nodes
Interest
Grease Pencil
Interest
ID Management
Interest
Images & Movies
Interest
Import Export
Interest
Line Art
Interest
Masking
Interest
Metal
Interest
Modeling
Interest
Modifiers
Interest
Motion Tracking
Interest
Nodes & Physics
Interest
OpenGL
Interest
Overlay
Interest
Overrides
Interest
Performance
Interest
Physics
Interest
Pipeline, Assets & IO
Interest
Platforms, Builds & Tests
Interest
Python API
Interest
Render & Cycles
Interest
Render Pipeline
Interest
Sculpt, Paint & Texture
Interest
Text Editor
Interest
Translations
Interest
Triaging
Interest
Undo
Interest
USD
Interest
User Interface
Interest
UV Editing
Interest
VFX & Video
Interest
Video Sequencer
Interest
Virtual Reality
Interest
Vulkan
Interest
Wayland
Interest
Workbench
Interest: X11
Legacy
Blender 2.8 Project
Legacy
Milestone 1: Basic, Local Asset Browser
Legacy
OpenGL Error
Meta
Good First Issue
Meta
Papercut
Meta
Retrospective
Meta
Security
Module
Animation & Rigging
Module
Core
Module
Development Management
Module
EEVEE & Viewport
Module
Grease Pencil
Module
Modeling
Module
Nodes & Physics
Module
Pipeline, Assets & IO
Module
Platforms, Builds & Tests
Module
Python API
Module
Render & Cycles
Module
Sculpt, Paint & Texture
Module
Triaging
Module
User Interface
Module
VFX & Video
Platform
FreeBSD
Platform
Linux
Platform
macOS
Platform
Windows
Priority
High
Priority
Low
Priority
Normal
Priority
Unbreak Now!
Status
Archived
Status
Confirmed
Status
Duplicate
Status
Needs Info from Developers
Status
Needs Information from User
Status
Needs Triage
Status
Resolved
Type
Bug
Type
Design
Type
Known Issue
Type
Patch
Type
Report
Type
To Do
No Milestone
No project
No Assignees
5 Participants
Notifications
Due Date
The due date is invalid or out of range. Please use the format 'yyyy-mm-dd'.

No due date set.

Dependencies

No dependencies set.

Reference: blender/blender#92969
No description provided.