![]() What’s the bare minimum we see the next wave of M1 Metal optimizations and additions reach a stable build? I am guessing since this just got released you and the team will miss the 3.2 dev cycle, so 3.3 is the absolute minimum, and potentially 3.4? ![]() What challenges are present for getting Metal optimized for Blender, and will some of M1 performance in Blender always lag due to differences in design, or could we reach parity with nVidia cards that have similar TFLOPS after enough dev time? The current Blender render times for a M1 Max with 32 cores is around the processing of a 1660 Ti, while in other applications and raw benchmarks the 32c M1 Max should be around a 2080 or 3070. ![]() For M1 Metal architecture in cycles, how does it handle GPU processing? Does it do a 1:1 imitation of how a desktop PC would work, and only dump the processing into the GPU cores, or does it tap into the M1 neural engine and the AMX (Apple Matrix coprocessor) for assisting the GPU cores? Would the neural engine or AMX even matter much for Blender work? I know you were working hard just to get this finally released in a stable build, but I am curious if some of the unique perks of the M1 architecture were skipped to easily mimic a Windows PC workflow in order to not complicate the first round of Metal implementation. ![]()
0 Comments
Leave a Reply. |
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |