ComfyUI Node: Queue on remote (single)

Queue on remote (single):

The RemoteQueueSimple node is designed to facilitate the dispatching of tasks to a remote server for processing. This node simplifies the process by providing a streamlined interface without extra controls, making it easier for you to manage remote job queues. It allows you to specify various parameters such as the remote server URL, batch sizes for local and remote processing, and a trigger mechanism to control when the job should be dispatched. The primary goal of this node is to offload computational tasks to a remote server, thereby freeing up local resources and potentially speeding up the overall workflow.

Queue on remote (single) Input Parameters:

remote_url

This parameter specifies the URL of the remote server where the job will be dispatched. It is a string input and should be a valid URL. The default value is http://127.0.0.1:8288/. This URL is crucial as it directs where the job will be processed remotely.

batch_local

This parameter defines the number of tasks to be processed locally before dispatching to the remote server. It is an integer input with a default value of 1, and it can range from a minimum of 1 to a maximum of 8. Adjusting this value can help balance the load between local and remote processing.

batch_remote

This parameter sets the number of tasks to be processed on the remote server. Similar to batch_local, it is an integer input with a default value of 1, and it can range from a minimum of 1 to a maximum of 8. This helps in managing the workload on the remote server.

trigger

This parameter controls when the job should be dispatched to the remote server. It offers two options: on_change and always. Selecting on_change will dispatch the job only when there is a change, while always will dispatch the job every time.

enabled

This parameter determines whether the remote dispatch is enabled. It offers three options: true, false, and remote. The default value is true. If set to false, the job will not be dispatched. If set to remote, the job will be dispatched only to the remote server.

seed

This parameter is used to set the seed value for the job, which can be useful for reproducibility. It is an integer input with a default value of 0, and it can range from a minimum of 0 to a maximum of 0xffffffffffffffff. The seed value ensures that the same job produces the same results when re-run.

prompt

This is a hidden parameter that contains the prompt or instructions for the job to be processed. It is not visible in the input interface but is essential for the job's execution.

Queue on remote (single) Output Parameters:

seed

This output parameter returns the seed value used for the job. It helps in tracking and reproducing the job results.

batch

This output parameter returns the number of tasks processed locally. It provides insight into the local processing workload.

remote_info

This output parameter returns a dictionary containing information about the remote job, including the remote_url and job_id. This information is useful for tracking and managing the remote job.

Queue on remote (single) Usage Tips:

• Ensure that the remote_url is correctly set to avoid connection issues with the remote server.
• Adjust the batch_local and batch_remote parameters to balance the workload between local and remote processing effectively.
• Use the trigger parameter to control when jobs are dispatched, which can help in optimizing performance.
• Keep track of the seed value for reproducibility of job results.

Queue on remote (single) Common Errors and Solutions:

"ConnectionError: Failed to connect to remote server"

• Explanation: This error occurs when the specified remote_url is incorrect or the remote server is not reachable.
• Solution: Verify that the remote_url is correct and that the remote server is running and accessible.

"ValueError: Invalid batch size"

• Explanation: This error occurs when the batch_local or batch_remote values are set outside the allowed range (1-8).
• Solution: Ensure that the batch_local and batch_remote values are within the range of 1 to 8.

"RuntimeError: Remote dispatch is disabled"

• Explanation: This error occurs when the enabled parameter is set to false, preventing the job from being dispatched.
• Solution: Set the enabled parameter to true or remote to allow the job to be dispatched to the remote server.