AWS Thinkbox Discussion Forums

Redshift C4D and GPUs per Task / GPU Affinity not working?

Hello everyone,
I just wanted ask if this is a known issue, bug or a limitation. Or maybe I am doing something wrong?

Batch submitting a Cinema 4D Job render with redshift always uses GPUs that are selected in the Redshift options inside of Cinema 4d. The GPUs per task or the GPU Affinity does not seem to change anything about this.

I am using Deadline 10.0.7.0. Cinema 4D r18, Redshift 2.6.14, Batch Plugin

What I do is I set the GPUs per task from 0 to 1. I have two GPUs. And I set the Concurrent tasks from 1 to 2. This should now render 2 tasks, one on each GPU. Instead it renders 2 tasks on 2 GPUs simultaneously, clogging the VRAM and ultimately crashing the renderer on heavy scenes.

Out of curiosity I tried setting the GPU Affinity in the Slave properties to 1. But The Jobs still render with 2 GPUs. Now when I deselect one GPU in the Redshift Cinema 4D Options inside of Cinema 4D, now it only uses one GPU no matter what GPUs per task or Affinity I set.

I seems like Deadline does not override the Redshift Cinema 4D settings at all?

Am I missing something?

Thanks!

Seems like the Batch Plugin was messing things up. Using the Non-Batch Plugin works.

Is this intended behaviour?

Thanks

forums.thinkboxsoftware.com/vie … 11&t=15979

got that same here, tried out latest script sent but still no progress

Hey blenderme,

Would you mind grabbing the render logs from the Cinema4D job and the Cinema4DBatch job? The code for redshift gpu affinity is very similar across the two plugins, but there might be a minor difference that could be causing some issues.

Cheers

in the mean time I was wondering if there is a way to control a slaves in way of bliocking an slave if other slave in specific group is active.
Lets say this scenario
4GPU render node, running 2 slaves each with 2 GPU affinity,
SlaveA-GPU0_1
SlaveB-GPU2_3

Now if you have running standard redshift job where all this works you wanna have both slaves working each using their assigned GPUs
But if octane job start with SlaveA-GPU0_1 assigned to octanegroup for examaple then wanna have SlaveB-GPU2_3 stopped, so it cant take any other redshift tasks for exmaple until octane task is done
That way octane wont use all GPUs on taht salve and at the same time taht slave trying to take 2 GPUs as well.

Makes sense?

I mean having proper GPU activity working would be best solution ofc but as temp solution… :slight_smile:

[attachment=0]renderlogs.txt[/attachment]

Hi,
I attached the renderlogs. Batch and non-batch. Both concurrent tasks=2 and gpus per task=1.

Does it have anything to do with this:
2018-07-21 09:55:21: 0: STDOUT: Redshift Info: Using explicit GPU Devices:
2018-07-21 09:55:21: 0: STDOUT: Redshift Info: GPU Ordinal:0 BusID:10 Device:‘GeForce GTX 1080 Ti’

Thanks!

Hey blenderme,

I meant to reply earlier but seemed to have lost my earlier message. I’ve made a fix for the plugin based off the Deadline version you’ve indicated (10.0.7.0). It now matches the same format on the command-line as the Cinema4D plugin. If you’ve got some time, could you give this a test run?

  • Back up your current DeadlineRepository\plugins\Cinema4DBatch\Cinema4DBatch.py
  • Unzip and copy the attached file to that location

Let me know how it goes!

Cheers


Hi Mepp,
Thank you this seems to be working! I rendered with GPUs per Task = 1 and concurrent tasks = 1 and checked it with gpu-z and there only is one gpu rendering. The Task Reports though have now become very short. No more info about Buckets rendering and the like.

I am on Deadline 10.0.17.7 now, maybe this is why the plugin isn’t reporting stdout from redshift anymore?

[code]=======================================================
Log

2018-08-02 10:08:34: 2: Loading Job’s Plugin timeout is Disabled
2018-08-02 10:08:36: 2: Executing plugin command of type ‘Sync Files for Job’
2018-08-02 10:08:36: 2: All job files are already synchronized
2018-08-02 10:08:36: 2: Plugin Cinema4DBatch was already synchronized.
2018-08-02 10:08:36: 2: Done executing plugin command of type ‘Sync Files for Job’
2018-08-02 10:08:36: 2: Executing plugin command of type ‘Initialize Plugin’
2018-08-02 10:08:36: 2: INFO: Executing plugin script ‘C:\Users\Rendernode01\AppData\Local\Thinkbox\Deadline10\slave\rendernode1\plugins\5b62b86547069424203a160d\Cinema4DBatch.py’
2018-08-02 10:08:37: 2: INFO: About: Cinema 4D Batch Plugin for Deadline
2018-08-02 10:08:37: 2: INFO: Render Job As User disabled, running as current user ‘Rendernode01’
2018-08-02 10:08:37: 2: INFO: The job’s environment will be merged with the current environment before rendering
2018-08-02 10:08:37: 2: Done executing plugin command of type ‘Initialize Plugin’
2018-08-02 10:08:37: 2: Start Job timeout is disabled.
2018-08-02 10:08:37: 2: Task timeout is disabled.
2018-08-02 10:08:37: 2: Loaded job: deadline_test.c4d (5b62b86547069424203a160d)
2018-08-02 10:08:37: 2: Skipping Z: because it is already mapped
2018-08-02 10:08:37: 2: Executing plugin command of type ‘Start Job’
2018-08-02 10:08:40: 2: INFO: Executing global asset transfer preload script ‘C:\Users\Rendernode01\AppData\Local\Thinkbox\Deadline10\slave\rendernode1\plugins\5b62b86547069424203a160d\GlobalAssetTransferPreLoad.py’
2018-08-02 10:08:40: 2: INFO: Looking for AWS Portal File Transfer…
2018-08-02 10:08:40: 2: INFO: Looking for File Transfer controller in C:/Program Files/Thinkbox/S3BackedCache/bin/task.py…
2018-08-02 10:08:40: 2: INFO: Could not find AWS Portal File Transfer.
2018-08-02 10:08:40: 2: INFO: AWS Portal File Transfer is not installed on the system.
2018-08-02 10:08:40: 2: INFO: Start Job called - starting up Cinema 4D Batch plugin
2018-08-02 10:08:40: 2: INFO: Not enforcing a build of Cinema 4D
2018-08-02 10:08:40: 2: INFO: [C4D_PLUGINS_DIR] set to: C:\Users\Rendernode01\AppData\Local\Thinkbox\Deadline10\slave\rendernode1\plugins\5b62b86547069424203a160d
2018-08-02 10:08:40: 2: INFO: Cinema 4D socket connection port: 50802
2018-08-02 10:08:40: 2: INFO: Parameters: -nogui -redshift-gpu 2 “-DeadlineConnect 50802 365170725758”
2018-08-02 10:08:40: 2: INFO: Starting monitored managed process Cinema4DProcess
2018-08-02 10:08:40: 2: INFO: Stdout Redirection Enabled: True
2018-08-02 10:08:40: 2: INFO: Stdout Handling Enabled: True
2018-08-02 10:08:40: 2: INFO: Popup Handling Enabled: True
2018-08-02 10:08:40: 2: INFO: QT Popup Handling Enabled: False
2018-08-02 10:08:40: 2: INFO: WindowsForms10.Window.8.app.* Popup Handling Enabled: False
2018-08-02 10:08:40: 2: INFO: Using Process Tree: True
2018-08-02 10:08:40: 2: INFO: Hiding DOS Window: True
2018-08-02 10:08:40: 2: INFO: Creating New Console: False
2018-08-02 10:08:40: 2: INFO: Running as user: Rendernode01
2018-08-02 10:08:40: 2: INFO: Executable: “C:\Program Files\MAXON\CINEMA 4D R18\Commandline.exe”
2018-08-02 10:08:40: 2: INFO: Argument: -nogui -redshift-gpu 2 “-DeadlineConnect 50802 365170725758”
2018-08-02 10:08:40: 2: INFO: Full Command: “C:\Program Files\MAXON\CINEMA 4D R18\Commandline.exe” -nogui -redshift-gpu 2 “-DeadlineConnect 50802 365170725758”
2018-08-02 10:08:40: 2: INFO: Startup Directory: “C:\Program Files\MAXON\CINEMA 4D R18”
2018-08-02 10:08:40: 2: INFO: Process Priority: BelowNormal
2018-08-02 10:08:40: 2: INFO: Process Affinity: default
2018-08-02 10:08:40: 2: INFO: Process is now running
2018-08-02 10:08:40: 2: STDOUT: Application start : 08/02/18 at 10:08:37
2018-08-02 10:08:40: 2: STDOUT: Executable : 64 Bit
2018-08-02 10:08:40: 2: STDOUT: Version / Build : 18.057 / RB203954
2018-08-02 10:08:40: 2: STDOUT: Debugger : not available
2018-08-02 10:08:40: 2: STDOUT: Memory model : release
2018-08-02 10:08:40: 2: STDOUT: Startup path : file:///C:/Program Files/MAXON/CINEMA 4D R18
2018-08-02 10:08:40: 2: STDOUT: Application path : file:///C:/Program Files/MAXON/CINEMA 4D R18/Commandline.exe
2018-08-02 10:08:40: 2: STDOUT: Application executable : file:///C:/Program Files/MAXON/CINEMA 4D R18/Commandline.exe
2018-08-02 10:08:40: 2: STDOUT: Resource path : file:///C:/Program Files/MAXON/CINEMA 4D R18/resource
2018-08-02 10:08:40: 2: STDOUT: Module path(s) : file:///C:/Program Files/MAXON/CINEMA 4D R18/modules
2018-08-02 10:08:40: 2: STDOUT: Temporary path : file:///C:/Users/RE~1/AppData/Local/Temp
2018-08-02 10:08:40: 2: STDOUT: Prefs path : file:///C:/Users/Rendernode01/AppData/Roaming/MAXON/CINEMA 4D R18_62A5E681
2018-08-02 10:08:40: 2: STDOUT: Global Prefs path : file:///C:/Users/Rendernode01/AppData/Roaming/MAXON
2018-08-02 10:08:40: 2: STDOUT: OS version : Windows 10, 64 Bit, Professional Edition (build 17134)
2018-08-02 10:08:40: 2: STDOUT: Processor : 8(16)x AMD Ryzen Threadripper 1900X 8-Core Processor
2018-08-02 10:08:40: 2: STDOUT: Computer name : RENDERNODE1
2018-08-02 10:08:40: 2: STDOUT: Thread Count : 16
2018-08-02 10:08:40: 2: STDOUT: Cpu Speed (MHz) : 3800.000
2018-08-02 10:08:40: 2: STDOUT: Application Type : Modular
2018-08-02 10:08:40: 2: STDOUT: Command line arguments : “-nogui” “-redshift-gpu” “2” “-DeadlineConnect 50802 365170725758”
2018-08-02 10:08:40: 2: STDOUT: Loading file:///C:/Program Files/MAXON/CINEMA 4D R18/modules/c4dplugin.xdl64 with module(s) net.maxon.c4dplugin net.maxon.c4d.c4dplugin
2018-08-02 10:08:40: 2: STDOUT: Loading file:///C:/Program Files/MAXON/CINEMA 4D R18/modules/crashhandler.module.xdl64 with module(s) net.maxon.crashhandler
2018-08-02 10:08:40: 2: STDOUT: Loading file:///C:/Program Files/MAXON/CINEMA 4D R18/modules/crypt.module.xdl64 with module(s) net.maxon.crypt
2018-08-02 10:08:40: 2: STDOUT: Loading file:///C:/Program Files/MAXON/CINEMA 4D R18/modules/drawport_general.module.xdl64 with module(s) net.maxon.drawport_general
2018-08-02 10:08:40: 2: STDOUT: Loading file:///C:/Program Files/MAXON/CINEMA 4D R18/modules/drawport_opengl.module.xdl64 with module(s) net.maxon.drawport_opengl
2018-08-02 10:08:40: 2: STDOUT: Loading file:///C:/Program Files/MAXON/CINEMA 4D R18/modules/drawport_selector.module.xdl64 with module(s) net.maxon.drawport_selector
2018-08-02 10:08:40: 2: STDOUT: Loading file:///C:/Program Files/MAXON/CINEMA 4D R18/modules/gui.module.xdl64 with module(s) net.maxon.gui
2018-08-02 10:08:40: 2: STDOUT: Loading file:///C:/Program Files/MAXON/CINEMA 4D R18/modules/image.module.xdl64 with module(s) net.maxon.image
2018-08-02 10:08:40: 2: STDOUT: Loading file:///C:/Program Files/MAXON/CINEMA 4D R18/modules/math.module.xdl64 with module(s) net.maxon.math
2018-08-02 10:08:40: 2: STDOUT: Loading file:///C:/Program Files/MAXON/CINEMA 4D R18/modules/mesh.module.xdl64 with module(s) net.maxon.mesh
2018-08-02 10:08:40: 2: STDOUT: Loading file:///C:/Program Files/MAXON/CINEMA 4D R18/modules/misc.module.xdl64 with module(s) net.maxon.misc
2018-08-02 10:08:40: 2: STDOUT: Loading file:///C:/Program Files/MAXON/CINEMA 4D R18/modules/network.module.xdl64 with module(s) net.maxon.network
2018-08-02 10:08:40: 2: STDOUT: Loading file:///C:/Program Files/MAXON/CINEMA 4D R18/modules/opencl.module.xdl64 with module(s) net.maxon.opencl
2018-08-02 10:08:40: 2: STDOUT: Loading file:///C:/Program Files/MAXON/CINEMA 4D R18/modules/opensubdiv.module.xdl64 with module(s) net.maxon.opensubdiv
2018-08-02 10:08:40: 2: STDOUT: Loading file:///C:/Program Files/MAXON/CINEMA 4D R18/modules/render.module.xdl64 with module(s) net.maxon.render
2018-08-02 10:08:40: 2: STDOUT: Loading file:///C:/Program Files/MAXON/CINEMA 4D R18/modules/shaderbase.module.xdl64 with module(s) net.maxon.shaderbase
2018-08-02 10:08:40: 2: STDOUT: Loading file:///C:/Program Files/MAXON/CINEMA 4D R18/modules/triangulation.module.xdl64 with module(s) net.maxon.triangulation
2018-08-02 10:08:40: 2: STDOUT: Could not initialize OpenGL root context: UnsupportedOperationError [ogl_context_win.cpp(1204)]
2018-08-02 10:08:40: 2: STDOUT: OpenGL root context initialized
2018-08-02 10:08:40: 2: STDOUT: Vendor : VMware, Inc. (VMWARE)
2018-08-02 10:08:40: 2: STDOUT: Renderer : Gallium 0.4 on llvmpipe (LLVM 4.0, 128 bits)
2018-08-02 10:08:40: 2: STDOUT: OpenGL version: 3.3 (Core Profile) Mesa 17.0.1 (git-)
2018-08-02 10:08:40: 2: STDOUT: Driver version: 17.0.1 (git-)
2018-08-02 10:08:42: 2: STDOUT: loading plugin directory: C:\Users\Rendernode01\AppData\Local\Thinkbox\Deadline10\slave\rendernode1\plugins\5b62b86547069424203a160d
2018-08-02 10:08:42: 2: STDOUT: X-Particles running on Command Line Render.
2018-08-02 10:08:42: 2: STDOUT:
2018-08-02 10:08:42: 2: STDOUT: ----------------------------------------
2018-08-02 10:08:42: 2: STDOUT: X-Particles particle system successfully loaded
2018-08-02 10:08:42: 2: STDOUT: X-Particles 3 Build 3.0.0328 Release
2018-08-02 10:08:42: 2: STDOUT: Wed May 13 15:17:25 2015
2018-08-02 10:08:42: 2: STDOUT: Copyright © INSYDIUM LTD
2018-08-02 10:08:42: 2: STDOUT: Registered To :
2018-08-02 10:08:42: 2: STDOUT: ----------------------------------------
2018-08-02 10:08:42: 2: STDOUT:
2018-08-02 10:08:42: 2: STDOUT: =================================================
2018-08-02 10:08:42: 2: STDOUT: --== Forester For Cinema 4D version 1.1.0 ==–
2018-08-02 10:08:42: 2: STDOUT: --== Forester is © 3DQUAKERS.com 2018 ==–
2018-08-02 10:08:42: 2: STDOUT: --== Forester Loaded Successfully! ==–
2018-08-02 10:08:42: 2: STDOUT: =================================================
2018-08-02 10:08:42: 2: STDOUT:
2018-08-02 10:08:42: 2: STDOUT: ===========================
2018-08-02 10:08:42: 2: STDOUT: – HDRLightStudio5C4D v2016.1124 © 2016
2018-08-02 10:08:42: 2: STDOUT: ===========================
2018-08-02 10:08:42: 2: STDOUT:
2018-08-02 10:08:42: 2: STDOUT:
2018-08-02 10:08:42: 2: STDOUT: --------- Microbion Software ---------
2018-08-02 10:08:42: 2: STDOUT: sIBL Loader successfully loaded.
2018-08-02 10:08:42: 2: STDOUT: sIBL Bitmap Transform shader loaded.
2018-08-02 10:08:42: 2: STDOUT:
2018-08-02 10:08:42: 2: STDOUT: [VB NOTE:] hash 0aa1892
2018-08-02 10:08:42: 2: STDOUT: Wrong VrayBridge.key - Vray not loaded!
2018-08-02 10:08:42: 2: STDOUT: Serial Number: 14804016606
2018-08-02 10:08:44: 2: STDOUT: Appending “//workstation/C/Program Files/Thinkbox/DeadlineRepository/submission/Cinema4D/Main” to system path to import SubmitC4DToDeadline module
2018-08-02 10:08:44: 2: STDOUT: FS_preview_accelerator 1.0
2018-08-02 10:08:44: 2: STDOUT:
2018-08-02 10:08:44: 2: STDOUT: True
2018-08-02 10:08:44: 2: STDOUT: D
2018-08-02 10:08:44: 2: STDOUT: == NextLimit RealFlow plug-in v2.4.6 ==
2018-08-02 10:08:44: 2: STDOUT: == NextLimit RealFlow RenderKit plug-in v1.4.2 (for SDK v5.0.1.0008) ==
2018-08-02 10:08:44: 2: STDOUT: C:\Users\Rendernode01\AppData\Roaming\MAXON\CINEMA 4D R18_62A5E681\VrayBridgeLog
2018-08-02 10:08:44: 2: INFO: Received Token: 365170725758
2018-08-02 10:08:44: 2: INFO: Connected to Cinema 4D
2018-08-02 10:08:44: 2: INFO: Set Verbose to True
2018-08-02 10:08:44: 2: STDOUT: Loading Scene: Z:\deadline_test.c4d
2018-08-02 10:08:44: 2: INFO: Loaded Scene
2018-08-02 10:08:44: 2: Done executing plugin command of type ‘Start Job’
2018-08-02 10:08:44: 2: Plugin rendering frame(s): 2
2018-08-02 10:08:45: 2: Executing plugin command of type ‘Render Task’
2018-08-02 10:08:45: 2: INFO: Render Tasks called
2018-08-02 10:08:45: 2: INFO: Pre Build Script
2018-08-02 10:08:45: 2: INFO: Validating the path: ‘Z:\render’
2018-08-02 10:08:45: 2: INFO: Validating the path: ‘C:\Users\Rendernode01\AppData\Local\Thinkbox\Deadline10\slave\rendernode1\jobsData\5b62b86547069424203a160d\c4dOutput_tempGkJWK0’
2018-08-02 10:08:45: 2: INFO: Rendering main output to local drive, will copy files and folders to final location after render is complete
2018-08-02 10:08:45: 2: INFO:
2018-08-02 10:08:45: 2: STDOUT: Running Script: C:\Users\Rendernode01\AppData\Local\Thinkbox\Deadline10\slave\rendernode1\jobsData\5b62b86547069424203a160d\thread2_tempH8hIl0\c4d_Batch_Script.py
2018-08-02 10:08:48: 2: STDOUT: Rendering frame 2 at <Thu Aug 02 10:08:46 2018>
2018-08-02 10:09:49: 2: INFO: Script Ran Successfully
2018-08-02 10:09:49: 2: INFO: Moving main output files and folders from C:\Users\Rendernode01\AppData\Local\Thinkbox\Deadline10\slave\rendernode1\jobsData\5b62b86547069424203a160d\c4dOutput_tempGkJWK0 to Z:\render
2018-08-02 10:09:49: 2: INFO: Finished Cinema 4D Task
2018-08-02 10:09:49: 2: Done executing plugin command of type ‘Render Task’

=======================================================
Details

Date: 08/02/2018 10:09:49
Frames: 2
Job Submit Date: 08/02/2018 09:53:09
Job User: alex
Average RAM Usage: 1100620288 (4%)
Peak RAM Usage: 1577984000 (5%)
Average CPU Usage: 8%
Peak CPU Usage: 18%
Used CPU Clocks (x10^6 cycles): 300897
Total CPU Clocks (x10^6 cycles): 3761210

=======================================================
Slave Information

Slave Name: Rendernode1
Version: v10.0.17.7 Release (b00c030fe)
Operating System: Windows 10 Pro
Running As Service: No
Machine User: Rendernode01
IP Address: 2a02:908:171:9920:4861:f175:cd7a:b693
MAC Address: 30:9C:23:5F:2D:4E
CPU Architecture: x64
CPUs: 16
CPU Usage: 33%
Memory Usage: 9.6 GB / 31.9 GB (30%)
Free Disk Space: 302.249 GB (38.069 GB on C:, 264.180 GB on Y:)
Video Card: NVIDIA GeForce GTX 1080 Ti

[/code]

it didn’t work for me, still running all GPUs even I did select 1 concurrent task 1 gpu and turned off use all GPUs in octane settings in C4D
so it doesn’t work with concurrent task and use number of GPUs when submitting but is it maybe intended to affect only GPU affinity in slaves?
I haven’t tested that yet but if that work that would be progress too.

Glad to hear blenderme.

Unfortunately, to get the logging from redshift we had to do some hackery (they have to be added on the command-line). If you take a look at the plugin settings for Cinema4D Batch, we’ve added an option to specify the different allowable verbosity’s for Redshift logging. It might take some fiddling to get the verbosity that best suits you.

It shouldn’t be dependent on GPU overrides, it takes all of those into account all of those factors when deciding which GPUs to use. I do recall you had this issue with the Octane Renderer and gpu affinity. Are you still using Octane, or are you testing with Redshift? This matters because each renderer has to choose to support gpu affinity (unlike cpu affinity) and I’m currently still waiting on the Octane for C4D developer to provide me the fix for gpu affinity there.

Cheers

aaaaaargh sorry my bad I mistaken this thread for the other one :slight_smile:
I thought it was octane fix. But I didn’t notice that I have issue with redshift on c4d at all… gave me something to thing about and test

No worries! :smiley:

Like I said, we’re still waiting on a response from the octane for c4d devs, hopefully not much longer now… :frowning:

Cheers

Privacy | Site terms | Cookie preferences