ComfyUI Node: Queue on remote (single)

RemoteQueueSimple(Nux):

The RemoteQueueSimple(Nux) node is designed to facilitate the distribution of tasks to remote servers, allowing for efficient processing of AI-generated art tasks. This node is particularly beneficial for users who need to offload processing to remote systems, thereby freeing up local resources and potentially speeding up task completion. By managing the queuing of tasks and dispatching them to specified remote URLs, this node ensures that tasks are handled in an organized manner. It supports the configuration of multiple parameters that can be applied remotely, making it versatile for various use cases. The node's primary goal is to streamline the process of remote task execution, providing a seamless experience for users who wish to leverage distributed computing resources.

RemoteQueueSimple(Nux) Input Parameters:

remote_url

This parameter specifies the URL of the remote server where tasks will be dispatched. It is crucial for directing the task to the correct remote location. There are no specific minimum or maximum values, but it must be a valid URL.

batch_local

This parameter defines the number of tasks to be processed locally. It impacts how many tasks are retained for local execution versus being sent remotely. The default value is typically set to zero, indicating no local processing.

batch_remote

This parameter indicates the number of tasks to be processed remotely. It determines the workload that will be offloaded to the remote server. The default value is usually set to a positive integer, depending on the user's needs.

trigger

This parameter acts as a control mechanism to initiate the queuing process. It is often a boolean or a specific condition that, when met, starts the task dispatch process.

enabled

This parameter determines whether the node is active and whether tasks should be processed locally or remotely. It can take values like "false" for no processing, "remote" for remote processing, or other conditions as defined by the user.

seed

This parameter is used to initialize the random number generator for task processing, ensuring reproducibility of results. It is an integer value, with no specific minimum or maximum, but typically starts at zero or a user-defined value.

prompt

This parameter contains the instructions or data that will be sent to the remote server for processing. It is a string value and forms the core of what the remote task will execute.

remoteapply1 to remoteapply10

These parameters allow for the specification of additional remote parameters, each consisting of a nodetitle, parameter name, value, and value type. They enable customization of the remote task execution, allowing for up to ten additional configurations.

RemoteQueueSimple(Nux) Output Parameters:

seed

This output returns the seed value used for the task, which is crucial for reproducing the results of the task execution. It helps in verifying and validating the consistency of the output.

batch_local

This output indicates the number of tasks that were processed locally, providing insight into the distribution of workload between local and remote processing.

remote_info

This output is a dictionary containing information about the remote task execution, including the remote_url and job_id. It is essential for tracking and managing remote tasks, allowing users to monitor the status and results of their dispatched tasks.

RemoteQueueSimple(Nux) Usage Tips:

• Ensure that the remote_url is correctly configured to avoid dispatching tasks to incorrect or unreachable servers.
• Use the enabled parameter wisely to toggle between local and remote processing based on your current resource availability and task urgency.

RemoteQueueSimple(Nux) Common Errors and Solutions:

Invalid URL

• Explanation: The remote_url provided is not a valid URL or is unreachable.
• Solution: Double-check the URL for typos and ensure that the remote server is accessible and online.

Task Dispatch Failure

• Explanation: The node failed to dispatch tasks to the remote server due to network issues or incorrect parameters.
• Solution: Verify network connectivity and ensure all required parameters are correctly set and valid.

Parameter Mismatch

• Explanation: The remote parameters specified do not match the expected format or types.
• Solution: Review the remote parameters for correct naming, values, and types, ensuring they align with the remote server's requirements.