I just checked the sqlite tables and I only have a couple dozen comments, the longest of which is about 200 characters.
Is there a way to get a better idea of what Shotwell is doing when I start it? While looking around in the db I do notice that I have a value in the TagTable.photo_id_list column that is almost 26000 characters long. On Sat, 2015-09-19 at 04:44 +0000, Brian Masney wrote: > Do you happen to have a large amount of data in your event or photo > comment fields? I have a library with 17K photos and Shotwell was > taking > several minutes to start. A few months ago, I found the cause of the > problem to be my large event comments. The attached patch disables > searching by event comment but it makes Shotwell start with my > library > in under 3 seconds. > > I planned to submit a bug report once I had a correct patch ready to > fix > the issue. > > Brian > > > > On Fri, Sep 18, 2015 at 07:52:51PM -0400, a.gnome wrote: > > I have about 23K photo files going back to 1999 under Shotwell's > > management. Even on an SSD, it takes about 90 seconds for > > Shotwell to > > become responsive after starting up, which sometimes makes it > > pretty > > painful to use. > > > > What strategies have you used to deal with large collections of > > photos, > > while ensuring that all metadata (tags etc) are preserved? > > > > I was thinking of maintaining a small "Current" library for photo > > imports, initial organization, tagging, etc; and an "Archive" > > library > > for older photos, but foresee problems moving photos from "Current" > > to > > "Archive" as time goes on, especially with the metadata. > > > > Are there plans to make Shotwell more capable when it comes to > > managing > > large photo libraries? > > _______________________________________________ > > shotwell-list mailing list > > [email protected] > > https://mail.gnome.org/mailman/listinfo/shotwell-list _______________________________________________ shotwell-list mailing list [email protected] https://mail.gnome.org/mailman/listinfo/shotwell-list
