Comfy-Org
Manager: V3.30.3, how to disable auto FETCH ComfyRegistry Data on every startup?
Updated to Manager: V3.30.3, I noticed that on each startup, it auto fetch ComfyRegistry Data, previously there is an option checkbox (skip update check) to disable it, with a manual 'fetch' button in the Manager UI, I don't see this anymore in this version.
Possible to bring back this manual fetching and option to disable auto fetching (skip update check), for those who restarts ComfyUI a lot to test stuff. Thanks.
The "skip update check" option is completely unrelated to this functionality.
FETCH DATA is performed in the background to keep the data up to date, whereas "skip update check" is an option that determines whether to skip checking for updates on nodes installed via git clone when displaying the list.
Currently, selecting "update" as the filter in the list performs the same function as unchecking "skip update check", so it was removed as it is no longer needed.
To disable FETCH DATA, you can change network_mode to private or offline.
https://github.com/ltdrdata/ComfyUI-Manager?tab=readme-ov-file#config
The "skip update check" option is completely unrelated to this functionality.
FETCH DATA is performed in the background to keep the data up to date,
Was this done as well for all the previous releases, just that it wasn't printed to the console before?
whereas "skip update check" is an option that determines whether to skip checking for updates on nodes installed via
git clonewhen displaying the list. Currently, selecting "update" as the filter in the list performs the same function as unchecking "skip update check", so it was removed as it is no longer needed.
I tried selecting "update" as the filter, it starts to go through all installed custom nodes one by one in the console, and got stuck at "teacache" custom node for very long while. I closed the console window and relaunched it, upon startup, it seems to be running a startup script that run installation of every custom nodes's requirements.txt, is that how it is supposed to work if the update filter scan process wasn't completed properly?
To disable FETCH DATA, you can change
network_modetoprivateoroffline. https://github.com/ltdrdata/ComfyUI-Manager?tab=readme-ov-file#config
Thanks for pointing this out, I totally missed this piece of information.
-
The "Skip update check" option determines whether to check the update availability of the items displayed in the list. The update check process can take a long time, especially if there are many older custom nodes installed using the Git clone method. In environments like Colab, this process was extremely time-consuming, which is why this option was introduced. Normally, it would have been used with this option always enabled. In this case, the update status of custom nodes would be uncertain, so instead of an "Update" button, a "Try Update" button would be displayed.
-
The issue of getting stuck can occur when a custom node has been deleted or its URL has been modified, making it inaccessible through the previous URL. This was not taken into account, but I will make the necessary fixes.
Why is the data downloaded every time? I think it should avoid downloading the same data over and over. Like a browser does with webpages: first check if the file is newer or expired, then download
Why is the data downloaded every time? I think it should avoid downloading the same data over and over. Like a browser does with webpages: first check if the file is newer or expired, then download
The current ComfyUI-Manager fetches the entire node list and stores it in a cache for use. Since some information becomes outdated quickly, the cached data needs to be updated continuously.
This structure is currently being changed, and soon it will no longer rely on caching. Instead, it will fetch only the necessary data directly from the registry as needed.
This structure is currently being changed, and soon it will no longer rely on caching. Instead, it will fetch only the necessary data directly from the registry as needed.
This is good news.
But the current behavior is unconditional download. I tried now: start server, wait until the data is downloaded, stop server, start again ... data downloaded again!
I pulled the last code from the main repo and the Manager and tried again, same behavior, registry data downloaded on each start. And I'm waiting for:
[ComfyUI-Manager] default cache updated: https://api.comfy.org/nodes
FETCH DATA from: https://raw.githubusercontent.com/ltdrdata/ComfyUI-Manager/main/custom-node-list.json [DONE]
[ComfyUI-Manager] All startup tasks have been completed.
The current ComfyUI-Manager fetches the entire node list and stores it in a cache for use. Since some information becomes outdated quickly, the cached data needs to be updated continuously.
Is it possible to add a feature to specify network_mode as a cmd parameter or as an env variable?
Editing "config.ini" for automated scripts that run ComfyUI on some service like RunPod.io is not so easy, as to pass param/env option to override it.
Local situation: I restart Comfy at least 20+ times a day and every time I got those downloads, and during last month the data it downloads from ComfyRegistry become bigger.
I needed those caches only when I need to updates Nodes or ComfyUI and that happens not so often. Edit every time the config.ini file is not very convinient(in local or remote environment).
Another variant will be to introduce some option to update those data only after period of time: once a day/once a week in addition to ability to easy ovveride network_mode to offline.
Once we have our ComfyUI environment configured correctly for our workflows (ie. we already have all the custom nodes we are going to use and are happy with how everything is performing), the need to have an up-to-date list of available custom nodes is completely superfluous. The bandwith expenditure for this task multiplied across all Comfy users is probably extremely high. It's irresponsible not to have a way to disable this behavior. Bury it somewhere deep so people can't accidentally disable it if you must.
The structure of ComfyUI-Manager is currently undergoing changes. In a future update, it will become cacheless, meaning the backend will no longer preload and compute cache in advance.
@ltdrdata looking forward to this! let me know if you need any testers 🙏
Updating the local registry cache should be manually triggered. It's like performing an apt-get update before apt-get install, or brew update before brew install.
can't this at least have a cache that checks only once a day or at least once an hour? This is annoying and pollutes console when rebooting comfyui to test other nodes.
