Updating library on every start
Submitted by an unknown user
Link to original bug (#717549)
Description
---- Reported by shotwell-maint@gnome.bugs 2011-05-01 07:15:00 -0700 ----
Original Redmine bug id: 3568
Original URL: http://redmine.yorba.org/issues/3568
Searchable id: yorba-bug-3568
Original author: Norbert Preining
Original description:
Hi all,
maybe it is just my ignorance, but it looks strange that shotwell on every start goes into "Updating Library" (in the side bar).
Is this intended? It does indeed some disk access as far as I can see, so I am not sure if that makes sense, esp. when libraries are getting big.
(as usual git from yesterday or so)
Thanks a lot and all the best
Norbert
Related issues: duplicates shotwell - Feature #3130 (closed): Disable runtime monitoring (don't scan library directory ... (Open)
---- Additional Comments From shotwell-maint@gnome.bugs 2013-05-01 11:47:00 -0700 ----
History
Comment 1
Updated by Adam Dingle over 2 years ago
When you start Shotwell, it looks at the date of all photo files on disk to see if any of them have changed. If they have, it reads them to look for new metadata and/or image data. The “Updating library†message appears during this process. On my machine, even with a library of 10,000 photos it appears only for a moment, which seems fine.
- How many photos are in your library?
- I'm not sure what you dislike about how this works now. Do you think that Shotwell should not perform this startup scan? Or do you think that the message “Updating library†is confusing?
Comment 2
Updated by Norbert Preining over 2 years ago
Hi Adam,
I have about 20000+ photos and it takes 4sec when the disk cache is filled, and about 10sec when it is empty.
Concerning the behaviour: I am not sure if it should be done automatically, but the “Updating library†is probably the misguiding info. I always thought it is actually changing something. “Checking for changes†or something similar might be better.
And of course, a pref option to disable that for huge libraries and do it only on demand might be nice.
Thanks and all the best
Norbert
Comment 3
Updated by Mattias Põldaru over 2 years ago
- Description updated (diff)
I would be happier, if this happened less often, once a day or so.
Also it could be completely in the background, so that it stops when larger picture is being loaded and continues right after that. But this one is huge amount of work.
Comment 4
Updated by rv - almost 2 years ago
- Description updated (diff)
I would also be happier if there was some mechanism to limit the overload of IO on HDD. During the start-scan the computer's interface almost freezes due to that. A lesser IO-priority for those processes could be applied to prevent such behaviour.
Thanks
Comment 5
Updated by Jim Nelson 11 months ago
- Status changed from Open to 5
- Resolution set to duplicate
This is in spirit a duplicate of #3130 (closed), so closing.
Comment 6
Updated by Charles Lindsay 7 months ago
- Status changed from 5 to Duplicate
--- Bug imported by chaz@yorba.org 2013-11-25 21:52 UTC ---
This bug was previously known as bug 3568 at http://redmine.yorba.org/show_bug.cgi?id=3568
Unknown Component Using default product and component set in Parameters Unknown version " in product shotwell. Setting version to "!unspecified". Unknown milestone "unknown in product shotwell. Setting to default milestone for this product, "---". Setting qa contact to the default for this product. This bug either had no qa contact or an invalid one.
Resolution: RESOLVED DUPLICATE