dope sheet zooming oddity regarding cpu usage #42732

Closed
opened 2014-11-26 21:38:58 +01:00 by Sanc Tuary · 9 comments

System Information
xp 32bits

Blender Version
Broken: (example: 2.69.7 4b206af, see splash screen)
Worked: (optional)
not really applicable as it's not broken, but there's something is very strange see below

Short description of error
zooming in/out behaviour in dopesheet can increase CPU use a lot depending on how you zoom

Exact steps for others to reproduce the error

  • i change the 3D view to the dope sheet
  • i open whatever CPU usage monitoring program i have
  • i zoom in continuously with -mousewheel- (important)
    (i don't stop moving your mousewheel to zoom)
  • i observe the CPU usage increase progressively until +/- 54% during the mousewheel use

now other method :

  • i stop zooming in with your mousewheel
  • i hold CTRL , i hold your mousewheel button (or hold middle mouse button if you have one) and move the mouse to zoom that way, as before, i don't stop moving your mouse
  • first noticable difference is that the zooming that way is not only much faster, but it's very much smoother
  • 2nd noticable difference is that the CPU usage does not increase and stay very low actually.

After testing with past versions of Blender i noticed the last version in which the mousewheel zoom didn't had that odd CPU increase was 2.69, this apparently started with 2.70
(additionally i don't have a mouse manager program that could go crazy, it's all xp native mouse support)

As said it's not a bug to me as i usually use the hold CTRL hold MMB to zoom, just an oddity i observed and prefered to report in case it's not related to unsupported OS (as i'm on XP) but hide something else with windows.
I remember there was a CPU overuse problem on windows some time ago with OpenMP and the new mscv2013 compiller.

**System Information** xp 32bits **Blender Version** Broken: (example: 2.69.7 4b206af, see splash screen) Worked: (optional) not really applicable as it's not broken, but there's something is very strange see below **Short description of error** zooming in/out behaviour in dopesheet can increase CPU use a lot depending on how you zoom **Exact steps for others to reproduce the error** - i change the 3D view to the dope sheet - i open whatever CPU usage monitoring program i have - i zoom in continuously with -mousewheel- (important) (i don't stop moving your mousewheel to zoom) - i observe the CPU usage increase progressively until +/- 54% during the mousewheel use now other method : - i stop zooming in with your mousewheel - i hold CTRL , i hold your mousewheel button (or hold middle mouse button if you have one) and move the mouse to zoom that way, as before, i don't stop moving your mouse - first noticable difference is that the zooming that way is not only much faster, but it's very much smoother - 2nd noticable difference is that the CPU usage does not increase and stay very low actually. After testing with past versions of Blender i noticed the last version in which the mousewheel zoom didn't had that odd CPU increase was 2.69, this apparently started with 2.70 (additionally i don't have a mouse manager program that could go crazy, it's all xp native mouse support) As said it's not a bug to me as i usually use the hold CTRL hold MMB to zoom, just an oddity i observed and prefered to report in case it's not related to unsupported OS (as i'm on XP) but hide something else with windows. I remember there was a CPU overuse problem on windows some time ago with OpenMP and the new mscv2013 compiller.
Author

Changed status to: 'Open'

Changed status to: 'Open'
Author

Added subscriber: @sanctuary

Added subscriber: @sanctuary

Added subscriber: @FloridaJo

Added subscriber: @FloridaJo

I tried this on OSX and could only get up to 15% both ways, and same with 3D view zooming as well. No anomalies here.

I tried this on OSX and could only get up to 15% both ways, and same with 3D view zooming as well. No anomalies here.

Added subscribers: @MartijnBerger, @ThomasDinges, @Psy-Fi

Added subscribers: @MartijnBerger, @ThomasDinges, @Psy-Fi

I can't see too much of a difference on linux either. Maybe a windows dev can check things here? @ThomasDinges or @MartijnBerger?

I can't see too much of a difference on linux either. Maybe a windows dev can check things here? @ThomasDinges or @MartijnBerger?
Author

I managed to get a friend that had the same OS as me to try and he didn't observed much difference between the 2 zoom methods in term of CPU usage.
The bigger difference was that his system has 3 cores while i have 2 but unsure at that point if it's part of the problem.

The oddity to me is that this cpu noticable increase really only happen in the dopesheet with only the 1st zooming method, i have no such problem in the 3D view or when sculpting by example, i even tried the UV editor as it's 2D too and there again no problem, it seems to happen only in the dopesheet for me.

I managed to get a friend that had the same OS as me to try and he didn't observed much difference between the 2 zoom methods in term of CPU usage. The bigger difference was that his system has 3 cores while i have 2 but unsure at that point if it's part of the problem. The oddity to me is that this cpu noticable increase really only happen in the dopesheet with only the 1st zooming method, i have no such problem in the 3D view or when sculpting by example, i even tried the UV editor as it's 2D too and there again no problem, it seems to happen only in the dopesheet for me.
Member

Changed status from 'Open' to: 'Archived'

Changed status from 'Open' to: 'Archived'
Julian Eisel self-assigned this 2014-11-30 14:44:33 +01:00
Member

Hey @sanctuary,
I had a look at this and can confirm CPU usage of > 50% with really fast zooming (using a mouse that can disengage the mousewheel, making really fast scrolling possible). However, this is sort of expected, as the CPU has to recalculate and redraw the entire region (I guess the most CPU power is needed to calculate the grid in the background). You can also recreate this in the Node Editor or the Timeline. I had a look at pre-2.7 versions, too, with the same result.

So thanks a lot for the report @sanctuary, but luckily no bug here :)

Hey @sanctuary, I had a look at this and can confirm CPU usage of > 50% with really fast zooming (using a mouse that can disengage the mousewheel, making really fast scrolling possible). However, this is sort of expected, as the CPU has to recalculate and redraw the entire region (I guess the most CPU power is needed to calculate the grid in the background). You can also recreate this in the Node Editor or the Timeline. I had a look at pre-2.7 versions, too, with the same result. So thanks a lot for the report @sanctuary, but luckily no bug here :)
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
4 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#42732
No description provided.