I'm guessing the tags are getting written to the photo's xmp files. Open one up and you can see the hierarchicalSubject and subject tags. These both contain tags I use.
Some file systems aren't very efficient writing a small amount of data to lots of files though I will admit this seems excessive. Full disclosure, I'm not a developer. Just a lurker/user on the mailing list. On 29 July 2017 at 21:14, August Schwerdfeger <aug...@schwerdfeger.name> wrote: > Darktable 1.4.2, 1.6.9, 2.0.7, and 2.2.4, on Fedora, CentOS, and OS X. > > There is something seriously wrong with Darktable's tagging module. > > As I have used successive versions of Darktable with databases containing > an increasing number of tags, the tagging module has gradually become so > slow in its operation as to be essentially unusable. > > For example, recently, on a database containing ~2500 tags, I attempted to > attach a single tag to ~250 images. This operation took approximately three > minutes, during which time Darktable was unresponsive and consistently used > about 100% of two cores. > > By way of comparison, I accessed a copy of the database file directly and > used an INSERT INTO command to apply the same tag to the same images. This > took about 20ms. > > Since actually attaching the tag is clearly not taking six minutes of > processor time, what else is the tagging module doing that could possibly > be causing these delays (and, what is more to the point, how do I work > around it so I can actually use the thing again)? > > -- > August Schwerdfeger > aug...@schwerdfeger.name > > ___________________________________________________________________________ > darktable developer mailing list to unsubscribe send a mail to > darktable-dev+unsubscr...@lists.darktable.org > -- Joel Brunetti c: 403.808.6208 joelbrune...@gmail.com ___________________________________________________________________________ darktable developer mailing list to unsubscribe send a mail to darktable-dev+unsubscr...@lists.darktable.org
