Comments on: Two by Two http://lewing.org/wordpress/2006/10/12/two-by-two/ Why go hungry when you can go free. Thu, 11 Mar 2010 23:51:47 +0000 http://wordpress.org/?v=2.0.4 by: AP http://lewing.org/wordpress/2006/10/12/two-by-two/#comment-24 Fri, 13 Oct 2006 14:55:59 +0000 http://lewing.org/wordpress/2006/10/12/two-by-two/#comment-24 Joe, my F-Spot catalog contains a little over 15 000 photos. While applying tags to many images takes some time, I'm still able to browse and view them pretty fast and filtering helps a lot. Joe, my F-Spot catalog contains a little over 15 000 photos. While applying tags to many images takes some time, I’m still able to browse and view them pretty fast and filtering helps a lot.

]]> by: lewing http://lewing.org/wordpress/2006/10/12/two-by-two/#comment-23 Fri, 13 Oct 2006 01:11:19 +0000 http://lewing.org/wordpress/2006/10/12/two-by-two/#comment-23 Absolutely give it another chance. Several thosand images should be no problem at all, in the tens of thousands you may begin to notice some of the filtering operations slowing down, but if it is anything more that a small lag please file a bug. One of the primary goals of f-spot is to deal with large collections. The specific problem you mention sounds like a very old bug in the import code where mono was extremely slow garbage collect image buffers because it isn't aware of the actual amount of memory they are using. It has been solved for a long time by being more more explicit and not relying too much on the garbage collector in places where we know there are issues. F-Spot is by no means flawless and it never will be. That said I'm sure you'll find it has improved a great deal since you last tried, and I hope you'll find using it a more pleasurable experience. Give it a try, let me know how it goes, and I'll continue to do my best to improve it. Absolutely give it another chance. Several thosand images should be no problem at all, in the tens of thousands you may begin to notice some of the filtering operations slowing down, but if it is anything more that a small lag please file a bug. One of the primary goals of f-spot is to deal with large collections.

The specific problem you mention sounds like a very old bug in the import code where mono was extremely slow garbage collect image buffers because it isn’t aware of the actual amount of memory they are using. It has been solved for a long time by being more more explicit and not relying too much on the garbage collector in places where we know there are issues.

F-Spot is by no means flawless and it never will be. That said I’m sure you’ll find it has improved a great deal since you last tried, and I hope you’ll find using it a more pleasurable experience. Give it a try, let me know how it goes, and I’ll continue to do my best to improve it.

]]> by: Joe Buck http://lewing.org/wordpress/2006/10/12/two-by-two/#comment-22 Thu, 12 Oct 2006 22:08:37 +0000 http://lewing.org/wordpress/2006/10/12/two-by-two/#comment-22 I tried f-spot about a year ago, asking it to import my digital photo collection: several thousand pictures, about 2Gb worth. My poor machine went into a swapping frenzy, as if f-spot were trying to have all the photos in memory at once. It also made a copy of each photo (up to the point where my computer ran out of gas and the OOM killer kicked in). I deleted the app from my system. Should I give it another chance? Does f-spot now deal sanely with large numbers of images? I tried f-spot about a year ago, asking it to import my digital photo collection: several thousand pictures, about 2Gb worth. My poor machine went into a swapping frenzy, as if f-spot were trying to have all the photos in memory at once. It also made a copy of each photo (up to the point where my computer ran out of gas and the OOM killer kicked in). I deleted the app from my system.

Should I give it another chance? Does f-spot now deal sanely with large numbers of images?

]]>