Viewport Performance #61060
Labels
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
8 Participants
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: blender/blender#61060
Loading…
Reference in New Issue
No description provided.
Delete Branch "%!s(<nil>)"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
System Information
Operating system: Windows 10 1803
Graphics card: 1x RTX 2080 / 2x RTX 2070
GPU Driver: 417.71
CPU: 2x Intel Xeon E5-2697v2
Ram: 64 GB
Blender Version
Broken:
2.80.43
Short description of error
When Playing the annimation in the Viewport iam only getting 15 fps. That`s in Evvee and Shade mode. If i use Solid mode i get 30 fps. On another Workstation:
CPU: I7 8700K
GPU: RTX 2080
Ram: 64GB
I have 30 FPS in Every Shading mode.
Exact steps for others to reproduce the error
Hit the Spacebar to Play the Annimation in the Viewport.
Added subscriber: @ok-4
Added subscriber: @WilliamReynish
Can you supply an example blend where this applies?
Montagevideo.blend
Added subscriber: @ZedDB
If I get this correctly, you are saying that you get 30fps on one of your computers but 15fps on an other computer?
What is your CPU usage like? Is it maxed out?
I guess the point he is trying to make, is that it runs faster on an ostensibly slower system with an older GPU than a faster one. I also get 30 fps here on an Intel Core i5 in Solid mode, but very low performance in LookDev or Rendered mode.
Yes you are right. My Workstation must have better performance considering it`s specs. See the Screenshot{F6464564}
As you can see here: https://browser.geekbench.com/processors/1034
The single core performance of the Xeon is way lower than that of a i5 or i7 (because of lower clocks).
So if I took a wild guess, this is because the Xeon is now bottle necked by it's single core performance in this case and thus can only manage 15fps.
But we won't know until we check the CPU usage.
You can see the CPU usage in my last Picture attachment. It`s 6%.
@ok-4 how does the CPU usage look on the i7?
With I7-5820K we have 10%
I mean the usage on all cores. In you xeon cpu usage picture we could see that one core has a lot higher usage than the others (seems that core has around 80% usage or so).
I have taken another screenshot from the I7 Workstation.
Added subscriber: @fclem
Yeah, it seems like only one core is being stressed on both systems (and the GPU usage doesn't seem high either).
And on your i7 system it seems like the single core is being used less.
@fclem, do you think there could be something else dragging down the performance in viewport?
@ok-4 BTW, could you set the screen resolution to be the same on both computers and test?
I have set the Resolution on both PC to 1920x1200. FPS is stil bad. In my Scene is a Collection called "Annimierte Objekte". If you click on the Eyedroper to hide it while you Play the animation the performance is significantly better. But in my Opinion the animated objetcts in this Collection should be easily handeld by an RTX 2080 GPU.
Yes the drawing code is still not multi-threaded. More works needs to be done before it happens.
Do you think this bad performance comes from the CPU or GPU?
You can see how much time is spend on both by setting the debug value (F3 > debug value) to 23. Everything above GPU Memory stats is CPU related.
Do note that theses timings are not very precise but can reveal a bottleneck.
Added subscriber: @brecht
The i7 has much better single core performance than the Xeon, so the FPS would make sense if this was single threaded CPU bound.
Thank you for your help so far. Here is a Picture with the Debug Mode on. With and without the "Annimierte Objekte" Collection. Could you explain me what causes the Bottelneck? Is there to much geometry for one CPU Core to handle?
Yes it seems that the bottleneck is the time to prepare the animated geometry on the CPU.
The gpu timings seems quite higher too but I would say it's because of driver overheads that are more noticeable on the Xeon that is less optimized for Single Threaded task.
Added subscriber: @mont29
@fclem assigning to you for now, feel free to re-assign.
Okay thank you for your advice. Is it possible to implement the preparation of the animated geometry to be multi-threaded? Maybe in 2.81?
Added subscriber: @Matthewv1998
Amd user here with a 1700x. I’ve overclocked the bugger to 3.9ghz. Even then viewport performance is terrible. Even going into local view, which in 2.79 boosted fps and you could animate in that mode, that doesnt work in 2.8. Another note is that stuff hidden, it still effects the fps. The only fix ive sorta found is to go and move what ever rig you have, into another file out of the scene and animate it there. Or bite the bullet and go back to 2.79.
Added subscriber: @mano-wii
Changed status from 'Confirmed' to: 'Needs User Info'
Is this problem still seen in the latest blender builds?
https://builder.blender.org/download/
Also, can you provide the
system-info.txt
generated by blender on each computer (Help -> Save System Info
)?Changed status from 'Needs User Info' to: 'Archived'
Since apparently nobody else was able to reproduce this problem and the report has no activity for more than a week, as per the tracker policy we assume the issue is gone and can be closed.
Thanks for the report. If the problem persists please open a new report with the required information.