Hi Pascal, I had the same pb on my "production" copy of dt (~50K photos) I've solved this with manually adding some index to the db. I've added index on tagged_images(tagid) tags(id) film_rolls(folder) images(film_id) I don't think all this index are needed, but I was too lazy to test them one by one :(
But be carrefull, I'm a noob in sql, so I don't now if adding index can have weird effect elsewhere or not ! AlicVB Le 15/09/2013 09:13, Pascal Obry a écrit : > James, > >> The snark in me suggests that if you were running the Solaris version >> of darktable, you could use DTrace to find out the function(s) which >> is/are taking the longest amount of time. ;-) > But I'm on GNU/Linux :) > >> I still think it's worthwhile looking at the SQL that's being run >> when you mouseover. Even if the queries are returning null for tags, >> they might still be being constructed inefficiently. >> >> I'd start by running darktable with -d sql and dumping that output >> to a file (it'll be *large*), and then seeing if you can narrow down >> the UI experience to a particular query. > Ok, will try that. > >> There's also gprof, which might go some way towards helping the >> investigation as well. > I would like to avoid gprof if possible. > >> Are you seeing this with a release version,or git master? > Yes on git master. I've not tested with latest release. > > Pascal. > ------------------------------------------------------------------------------ LIMITED TIME SALE - Full Year of Microsoft Training For Just $49.99! 1,500+ hours of tutorials including VisualStudio 2012, Windows 8, SharePoint 2013, SQL 2012, MVC 4, more. BEST VALUE: New Multi-Library Power Pack includes Mobile, Cloud, Java, and UX Design. Lowest price ever! Ends 9/22/13. http://pubads.g.doubleclick.net/gampad/clk?id=64545871&iu=/4140/ostg.clktrk _______________________________________________ darktable-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/darktable-devel
