Selective Loading of Custom Nodes Using INCLUDED_CUSTOM_NODES Environment Variable #6717
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
In production environments, multiple instances of ComfyUI may share a single volume. In such cases, some instances might only need specific custom nodes to function, while others might require a different set of nodes.
Currently, all custom nodes are loaded indiscriminately, which can lead to increased startup times and unnecessary resource usage.
Feature Overview
This PR introduces the INCLUDED_CUSTOM_NODES environment variable, allowing users to specify which custom nodes should be loaded at startup. This significantly reduces loading times and improves performance in environments where only a subset of nodes is required.
Usage Example
export INCLUDED_CUSTOM_NODES="node1, node2, node3"
Benefits
✅ Faster startup times by skipping unnecessary nodes
✅ Optimized resource usage for multi-instance environments
✅ More control over which custom nodes are loaded per instance
Looking forward to your feedback!
Thanks and best regards. 😊🚀