Hi all,
The main problem is that the F-Spot import feature loads the whole
F-Spot database in memory and performs a single large batch import. So
even if it was tuned, there would always be a possibility that a very
large database would make it run out of memory. So the only way to fix
this is to completely overhaul the code.
The good news is that this code overhaul is happening right now. I've
made good progress during the Christmas break on bug 3614
(http://redmine.yorba.org/issues/3614) to move the code to the SPIT
architecture. As part of that work, I've changed the behaviour to avoid
importing everything in one go. There are still a few rough edges but I
should have a first patch for review in the next couple of weeks. At
that point, it would be very useful to test the functionality on large
databases to see if it actually fixes the problem.
Cheers,
Bruno
On 16/12/11 19:45, Adam Dingle wrote:
Josep,
thanks for the additional information - I've appended it to the ticket
for this bug (http://redmine.yorba.org/issues/4498). The best way to
continue discussion about this is by adding comments to that ticket.
That way, people who are interested in this issue can easily follow
the discussion. Thanks!
adam
On 12/16/2011 11:39 AM, Josep Cols wrote:
Thanks, Adam.
For your information:
The lasts 2 imports (when 3.1 Gb of virtual memory is used) imported
only 1.200 photos every import.
I think the quatity of photos imported and/or the mount the memory
used is due to the tags.
I've about 10.000 tags at the last level and about 13.000 tags in
total on the database. The low level tags has 3-5 levels.
Every photo as a minimum of 6 tags and an average of 8-10 tags (and a
maximum of 20 tags).
Also, the photos are jpg from 10 OR 15 Mpixels camera (between 4 and
8 Mbytes each).
If you need more information, I can run tests for you and/or install
specific software for test pourposes, etc.
Regards
Al 16/12/11 18:40, En/na Adam Dingle ha escrit:
Josep,
thanks for reporting this crash. As Lucas mentioned, we're already
aware of a potential crash that can result from F-Spot database
inconsistencies. But the other crash you described, where Shotwell
is using an enormous amount of memory, is new. I've created a
ticket for this here:
http://redmine.yorba.org/issues/4498
We should investigate this for the upcoming 0.12 release.
adam
_______________________________________________
Shotwell mailing list
[email protected]
http://lists.yorba.org/cgi-bin/mailman/listinfo/shotwell
_______________________________________________
Shotwell mailing list
[email protected]
http://lists.yorba.org/cgi-bin/mailman/listinfo/shotwell
