Synology Drive

[native warren]

This might be an unusual setup, but I keep all my models and outputs on Synology Drive (but I suspect this could be the same for any 'cloud' or local cloud service) to keep the local storage at a minimum.

When I need a model, I'll make it local. But there's an issue with images - whenever Swarm is trying to gather information to make the thumbnail history, it needs to download every single image to gather the metadata. Obviously I don't want it to download every output - I also know there's a swarm_metadata.ldb that I don't exactly know what that does but might help. Is there a setting I can turn on to modify this behavior? The error I receive is thus:

   at System.IO.File.ReadAllBytes(String path)
   at SwarmUI.Utils.OutputMetadataTracker.GetMetadataFor(String file, String root, Boolean starNoFolders) in /SwarmUI/src/Utils/OutputMetadataTracker.cs:line 382

[sharp harbor]

I used to load models over a network. It works but on 1Gbit networking it is pretty slow.
Never did that with the output folder. That folder gets too messy for my taste anyway. I drag drop or "save as" the best images into my own folders with better organisation, then just nuke all the many many seed reools in the output folder if it gets too big.

Remember you can drag drop in an image into Swarm from anywhere on disk and it will still extract all the generation metadata

[tight mortar]

the metadata cache file makes it so swarm doesn't need to read every image. However it has to read each at least once to fill the cache, and you'll getting timeouts on just the basic initial read.

So, (1) I'll agree with berni, probably have your outputs on local drive and nuke or move folders if it starts getting big.

(2) Swarm works pretty well on a NAS, even at a distance. I've tested remote access between the US and Japan with large model&output folders. Swarm loaded in seconds (Comfy took several minutes though lol). The error you're having is not a simple byproduct of being a NAS. I suspect it's one of
(a) configuration issue with the nas software, look around specifically for anything that mentions timeouts, max read time, anything like that
(b) network hardware issue (eg you're connected via unstable wifi)
(c) drive hardware issue (is the nas able to actually reliably handle moving large amounts of data on and off without error?)

Relevant server settings here are ImageDataValidationChance you'll want to set to 0, ImageMetadataPerFolder you'll want off (unchecked), also user setting MaxImagesScannedInHistory you'll want relatively low