There have been some problems with unified memory though. The tests concerned for now only viewports at 300 dpi rendered with custom renderworks on one side and redshift on the other, repeating the same operations with both machines. I can confirm that the data for now has defined a 50% faster CPU rendering time and 70% faster GPU rendering than a 13 'MBP with M1. Maybe in View refresh/navigation and saving files.īut depending on MBPs configuration, you will have much more reserves for projectĪnd how it behaves with TwinMotion? Have you tried using the Twinmotion, because that is a quick killer with the ram, that was my initial doubts, because i'm looking into the M1 Pro 32gb at least which should be more than enough for the VW with some RW, but essentially i want to be using both at the "same time". Plus, the more RAM by M1 Max/Pro, the more memory lanes and throughput.Īs long as you don't hit a RAM limit with VW, you may hardly notice any difference If Redshift uses both, GPU and CPU, it should be even faster than just by the additional Just RW Rendering in "Redshift" mode, by GPU, should be at least, nearly about twiceĪs fast than M1 (7 or 8 GPU cores), with M1 Max/Pro 16 GPU cores or 4x faster with (BTW Which is still about 1.5 times slower than my Ryzen 3950X) So, like for Cinebench multicore CPU Rendering, and RW CPU Rendering in VW M1 has 4 performance cores, M1 Pro/Max have 8 performance cores. That may use more than 4 (performance) Cores, if any at all. It could only be faster in rare multi-threaded VW tasks Single core Performance is on par with our M1s. I'm really curious to see the M1 Pro working,
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |