Blender Log: Property Group Perfomance Issues #253

New Issue

Nick Alberelli · 2024-03-04T23:16:09+01:00

Nick Alberelli commented

2024-03-04 23:16:09 +01:00

Reported buy @SimonThommes there does appear to be a performance hit when using the Blender Log Add-On, this manifests as a 2-3 second delay/freeze when switching too/from the Blender Log Panel in the Sidebar.

I have narrowed the issue down to the BlenderLog_Manager property group. When accessing data in this group, for example the logs at blender_log.active_category.logs , there can be a noticable hit to performance.

# Perfomance Test for BlenderLog_Manager Property Group

import bpy
import time

start_time = time.time()
print(list(bpy.context.scene.blender_log.active_category.logs))
end_time = time.time()


print(f"{end_time-start_time} seconds")

Resulted in: 25.141098976135254 seconds on my PC when running this script in the mikassa-shading.blend file

Reported buy @SimonThommes there does appear to be a performance hit when using the Blender Log Add-On, this manifests as a 2-3 second delay/freeze when switching too/from the Blender Log Panel in the Sidebar. I have narrowed the issue down to the `BlenderLog_Manager` property group. When accessing data in this group, for example the logs at `blender_log.active_category.logs` , there can be a noticable hit to performance. ```python # Perfomance Test for BlenderLog_Manager Property Group import bpy import time start_time = time.time() print(list(bpy.context.scene.blender_log.active_category.logs)) end_time = time.time() print(f"{end_time-start_time} seconds") ``` Resulted in: `25.141098976135254 seconds` on my PC when running this script in the `mikassa-shading.blend` file

Nick Alberelli added the

labels 2024-03-04 23:16:09 +01:00

Nick Alberelli commented

2024-03-05 17:12:09 +01:00

This issue can be resolved by refreshing the Blender Log entries for some reason, the file mikassa-shading.blend had a single entry in it that was causing this issue. Refreshing the Logs clears the issue. Closing this issue now, wil investigate futher if this issue comes up again.

Blender Studio users can refresh logs by running Prepare Sync in the Asset Pipeline add-on's advanced menu.

This issue can be resolved by refreshing the Blender Log entries for some reason, the file `mikassa-shading.blend` had a single entry in it that was causing this issue. Refreshing the Logs clears the issue. Closing this issue now, wil investigate futher if this issue comes up again. Blender Studio users can refresh logs by running `Prepare Sync` in the Asset Pipeline add-on's advanced menu.

Nick Alberelli closed this issue

2024-03-05 17:12:10 +01:00

Sign in to join this conversation.

No Milestone

No project

No Assignees

1 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: studio/blender-studio-pipeline#253

Download

What's New

Blender Studio

Manual

Developers Blog

Documentation

Benchmark

Blender Conference

Development Fund

One-time Donations

Blender Log: Property Group Perfomance Issues #253