Blender 2.79 vs 2.8 - Viewport orbiting speed is heavily impacted #63925

Closed
opened 2019-04-27 03:33:39 +02:00 by Carlo Andreacchio · 15 comments

System Information
Operating system: Ubuntu 18.04
Graphics card: GTX 1080

Blender Version
Broken: 2.8
Worked: 2.79

Short description of error
Viewport orbiting speed is heavily impacted

Exact steps for others to reproduce the error

  1. Open attached blend file in blender 2.79
  2. middle mouse drag to orbit around, notice how it is slightly laggy, but not too bad to work with
  3. Open attached blend file in blender 2.8
  4. middle mouse drag to orbit around, notice how it is significantly laggy, and unworkable for a production scene.

This is the same production scene i have uploaded for other bug reports. I am trying to make blender 2.8 just as good as 2.79 for archviz style production scenes.

slowdown-2.blend

**System Information** Operating system: Ubuntu 18.04 Graphics card: GTX 1080 **Blender Version** Broken: 2.8 Worked: 2.79 **Short description of error** Viewport orbiting speed is heavily impacted **Exact steps for others to reproduce the error** 1) Open attached blend file in blender 2.79 2) middle mouse drag to orbit around, notice how it is slightly laggy, but not too bad to work with 3) Open attached blend file in blender 2.8 4) middle mouse drag to orbit around, notice how it is significantly laggy, and unworkable for a production scene. This is the same production scene i have uploaded for other bug reports. I am trying to make blender 2.8 just as good as 2.79 for archviz style production scenes. [slowdown-2.blend](https://archive.blender.org/developer/F6811442/slowdown-2.blend)

Added subscriber: @candreacchio

Added subscriber: @candreacchio
Member

Added subscribers: @fclem, @JacquesLucke

Added subscribers: @fclem, @JacquesLucke
Member

Just for reference:
image.png

There is nothing in particular that seems completely wrong to me here.

Just for reference: ![image.png](https://archive.blender.org/developer/F6991585/image.png) There is nothing in particular that seems completely wrong to me here.

Added subscriber: @YAFU

Added subscriber: @YAFU

Hi.

I can reproduce the problem here on Kubuntu 18.04, It is laggy and choppy in 2.8.
i7-3770. GTX 960

My CPU graph:
cpu.jpg

GPU usage While Orbit:
2.79 - peaks of 40%
2.80 - 100%

Hi. I can reproduce the problem here on Kubuntu 18.04, It is laggy and choppy in 2.8. i7-3770. GTX 960 My CPU graph: ![cpu.jpg](https://archive.blender.org/developer/F6991626/cpu.jpg) GPU usage While Orbit: 2.79 - peaks of 40% 2.80 - 100%
Clément Foucault was assigned by Sebastian Parborg 2019-04-29 19:20:58 +02:00

Added subscribers: @Sergey, @brecht

Added subscribers: @Sergey, @brecht

The issue is the way we render the particle instances. We are iterating over all the particles and the depsgraph is taking 1/3 of the drawing time to iterate over them.

Draw Cache & Render time could also be reduce if treating particle instances as a special case but that's more complicated because a lot of the complexity is abstracted by the depsgraph currently.

Tagging @brecht & @Sergey maybe you have ideas on how to fix this.

The issue is the way we render the particle instances. We are iterating over all the particles and the depsgraph is taking 1/3 of the drawing time to iterate over them. Draw Cache & Render time could also be reduce if treating particle instances as a special case but that's more complicated because a lot of the complexity is abstracted by the depsgraph currently. Tagging @brecht & @Sergey maybe you have ideas on how to fix this.

In 2.79 the particle dupli stuff takes even more of the time.
dupli_particles.png

So I'm not sure if fixing that performance is needed to get things back to 2.79 level, I think there is something else going on here as well.

To improve the (particle) dupli performance we should ideally cache the duplis on the object that generates them. There may also be some improvements possible in the particle code to generate them. I'm not sure we can do this for 2.80 though.

In 2.79 the particle dupli stuff takes even more of the time. ![dupli_particles.png](https://archive.blender.org/developer/F6994910/dupli_particles.png) So I'm not sure if fixing that performance is needed to get things back to 2.79 level, I think there is something else going on here as well. To improve the (particle) dupli performance we should ideally cache the duplis on the object that generates them. There may also be some improvements possible in the particle code to generate them. I'm not sure we can do this for 2.80 though.

I am not 100% sure how the code works behind the scenes, but are all of the bugs I have reported in regards to performance all linked to this same code slowdown? (#62511 #62511 #58188 and this one #63925 )

Would be great to get this in 2.80, but totally understand that it may require a bit more of a rework.

I am not 100% sure how the code works behind the scenes, but are all of the bugs I have reported in regards to performance all linked to this same code slowdown? (#62511 #62511 #58188 and this one #63925 ) Would be great to get this in 2.80, but totally understand that it may require a bit more of a rework.

The selection issue is a different bug.

This report may be the same as #58188, something in the wire overlay drawing code that is not optimal. I hope we can fix that for 2.80.

The selection issue is a different bug. This report may be the same as #58188, something in the wire overlay drawing code that is not optimal. I hope we can fix that for 2.80.

Is this still targeted for blender 2.8?

Is this still targeted for blender 2.8?

Not really, I wanted to but refactoring was too deep and would have made too many changes too close to release. It will be in 2.81. See progress made by D4997 (not even up to date).

Not really, I wanted to but refactoring was too deep and would have made too many changes too close to release. It will be in 2.81. See progress made by [D4997](https://archive.blender.org/developer/D4997) (not even up to date).

Is it still a target for 2.81?

Is it still a target for 2.81?

Changed status from 'Open' to: 'Resolved'

Changed status from 'Open' to: 'Resolved'

I believe D4997 has been applied.

I believe [D4997](https://archive.blender.org/developer/D4997) has been applied.
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#63925
No description provided.