- Wed Oct 28, 2015 5:12 pm
#389077
Would it be possible to multithread the export of an IMG from maxwell.exe, as well as the MXI merge that happens at the end of a cooperative render? I would think that it shouldn't be too difficult since it's all done on 2-dimensional graphics buffers (unless there's more to it than that). You could have it spawn different threads for each render channel or even have it slice up each channel into strips. The temporary merged MXI file could be assembled in RAM then pushed to disk once it's complete. It would consume more system resources, but it would optimize the process for export. The option to multithread vs single thread could be exposed in the preferences, in case you don't have enough resources to do it like this.
Just a thought. My new workstation has 48 threads, but each one caps at around 3.3 GHz when not under 100% load. It's about 2.9 GHz when everything is pegged. I'm working on images close to 10Mpx in size, so these exports are taking some time. This would also help with batch exports of animation frames.
Thanks Next Limit!
Just a thought. My new workstation has 48 threads, but each one caps at around 3.3 GHz when not under 100% load. It's about 2.9 GHz when everything is pegged. I'm working on images close to 10Mpx in size, so these exports are taking some time. This would also help with batch exports of animation frames.
Thanks Next Limit!
Regards,
Zack Parrish
-
Maxwell - 4.2.0.3
Maxwell 4 | 3ds Max - 4.2.4
336 capable Maxwell threads!
-
Workstation:
Dual E5-2680v3, 64GB, Quadro K5200
48 threads (HT) @ 139.2GHz
-
Render Farm:
288 threads (HT) @ 835.2GHz
Zack Parrish
-
Maxwell - 4.2.0.3
Maxwell 4 | 3ds Max - 4.2.4
336 capable Maxwell threads!
-
Workstation:
Dual E5-2680v3, 64GB, Quadro K5200
48 threads (HT) @ 139.2GHz
-
Render Farm:
288 threads (HT) @ 835.2GHz