Tagspaces import tags11/10/2023 ![]() ![]() Any more and I just spend the entire day watching Tagspaces perform incredibly inefficient sequences of file operations… It’s horrible… At the moment i have to tag photos in a temporary folder in batches of 5 to 10 photos. But even 20 is too many if the files have a lot of tags. the performance is a bit better if I reduce the number of visible items per page in the settings. The UI shouldn’t block while mundane stuff like search index updating and thumbnail proofing are occurring. Reducing the number of visible items on each page helps, so it seems tied to some inefficiencies in how a file’s thumbnail and tags are being loaded, and a lack of asynchronous activity. Just clicking a folder with page size 100 files that have 5-10 tags each can be brutally slow taking up to a blocking minute and chew on. The app struggles with thumbnail gallery presentation when any significant number of tags are involved in the files themselves. But every small inefficiency in this process is being exacerbated by points 1 and 2 above. Managing a list of 400 values applied to a few thousand DB records, and maintaining a search index just is not a hard task these days for the kinds of powerful computers we all enjoy. The inefficiencies of having lots of tags and tag groups in the left Tag organizing area are real, there are clearly optimizations to be had. It of should be batching operations efficiently to avoid needless loops, resulting in roughly the same required time to tag one as for tagging 100 files. If you have a large folder and try to apply tags to a lot of files, the whole app can be frozen in deep concentration for minutes to hours. It’s clearly doing each update one by one, causing the delays from point 1 above to snowball / accumulate.
0 Comments
Leave a Reply.AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |