That first devtalk link is really interesting. 2x performance increase here, 1.4x there… and that’s without Metal 3 improvements. That would bring that 1:37 render down to 35 seconds or so, then w/ Metal 3 I imagine it’ll drop to sub 30 seconds or maybe even sub 20 seconds. It’ll be interesting to see what it takes to get within spitting distance of that 15 second Optix render.In March, one of the Apple engineers working on the metal backend for Blender's Cycles wrote:
Cycles Apple Metal device feedback
The structure of the renderer is much aligned with the existing path taken for CPU and CUDA, with little leverage of Apple Silicon’s more unique architecture as of yet. We do leverage the unified memory architecture to avoid duplication of resources, but there’s much more to do on this front and...devtalk.blender.orgBlender Archive - developer.blender.org
developer.blender.org
Eevee, Blender's other renderer, will also have a Metal backend, most likely in Blender 3.4.
2022-06-13 Eevee/Viewport Module Meeting
Attendees: Clement Foucault Brecht van Lommel Omar Emara Jeroen Bakker Dalai Felinto Release 3.2 [T98708] should be added to a corrective release. It fixes an issue on platforms That supports OpenGL 4.3, but not the conservative depth extension. [T98620] is fixed in master, but was to late...devtalk.blender.orgMetal Viewport
**Status:** `?` Initial stages of development --- **Description** Bringing Metal support to the Blender viewport for optimal performance on macOS. This will be implemented as a new GPU Backend within Blender's GPU Module. **GHOST** * - [x] Encapsulate use of OpenGL within GHOST_ContextCGL * -...developer.blender.org
Edit: It’s also quite interesting to see the large amount of effort the Apple software engineers are putting into discrete GPU support for the Metal Cycles renderer. Metal for Cycles requires at least macOS 12.3, so it’s not like this is a legacy thing.
Last edited: