Cycles is consistently slower in 2.74 #44337

Closed
opened 2015-04-10 08:32:53 +02:00 by gandalf3 · 10 comments
Member

System Information
Archlinux 64

Blender Version
Broken: 2.74
Worked: 2.73

Short description of error
While rendering this test scene (originally made to test the new black background optimization in 2.74),
I found that cycles is consistently slower in 2.74. I ran a test scene five times each in both 2.73 and 2.74 (downloaded from blender.org).
All the 2.74 render times are slower than even the slowest 2.73 time.
The average render times from my tests:

2.73: 3:33.20
2.74: 3:41.67

I can't see any subjective difference in noise level (just by looking at it the renders anyway).
Renders were done from the CLI.

Exact steps for others to reproduce the error

  1. Open black_bg_performance_test.blend
  2. Render
**System Information** Archlinux 64 **Blender Version** Broken: 2.74 Worked: 2.73 **Short description of error** While rendering this test scene (originally made to test the new black background optimization in 2.74), I found that cycles is consistently slower in 2.74. I ran a test scene five times each in both 2.73 and 2.74 (downloaded from blender.org). All the 2.74 render times are slower than even the slowest 2.73 time. The average render times from my tests: 2.73: `3:33.20` 2.74: `3:41.67` I can't see any subjective difference in noise level (just by looking at it the renders anyway). Renders were done from the CLI. **Exact steps for others to reproduce the error** 1. Open [black_bg_performance_test.blend](https://archive.blender.org/developer/F160409/black_bg_performance_test.blend) 2. Render
Author
Member

Changed status to: 'Open'

Changed status to: 'Open'
Author
Member

Added subscriber: @gandalf3

Added subscriber: @gandalf3
Sergey Sharybin was assigned by Bastien Montagne 2015-04-10 12:03:12 +02:00

Added subscriber: @mont29

Added subscriber: @mont29

Sergey, I think to remember you have worked on that already?

Sergey, I think to remember you have worked on that already?

I've solved some typos in the distance heuristic in QBVH and did some workarounds for MSVC stupidness.

It' unclear from the report if it's CPU or GPU rendering, plus attaching system-info.txt is always a good idea.

I've solved some typos in the distance heuristic in QBVH and did some workarounds for MSVC stupidness. It' unclear from the report if it's CPU or GPU rendering, plus attaching system-info.txt is always a good idea.
Author
Member

CPU rendering (sorry, I don't know how I forgot to mention that..).
system-info.txt

CPU rendering (sorry, I don't know how I forgot to mention that..). [system-info.txt](https://archive.blender.org/developer/F160744/system-info.txt)
Member

Added subscriber: @Blendify

Added subscriber: @Blendify
Author
Member

On GPU 2.74 is slightly faster than 2.73, so it seems this only affects CPU rendering.

I did notice that GPU renders of the scene are noticeably more noisy than CPU renders with the same number of samples. In particular near the spotlight source.

On GPU 2.74 is slightly faster than 2.73, so it seems this only affects CPU rendering. I did notice that GPU renders of the scene are noticeably more noisy than CPU renders with the same number of samples. In particular near the spotlight source.

Changed status from 'Open' to: 'Resolved'

Changed status from 'Open' to: 'Resolved'

You wouldn't see difference in the noise in this particular scene. The reason of slowdown is caused by watertight nature of ray-triangle intersection now, which was compensated with QBVH for more complex scenes.

I've committed some memory optimization (828abaf) which also caused better utilization of CPU cache and solves speed regression in your particular file. But it's still possible some other files are still slower and this needs investigation.

But for now considering the report solved.

You wouldn't see difference in the noise in this particular scene. The reason of slowdown is caused by watertight nature of ray-triangle intersection now, which was compensated with QBVH for more complex scenes. I've committed some memory optimization (828abaf) which also caused better utilization of CPU cache and solves speed regression in your particular file. But it's still possible some other files are still slower and this needs investigation. But for now considering the report solved.
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#44337
No description provided.