On Thu, Sep 8, 2011 at 11:17 AM, Joseph Bylund <[email protected]>wrote:
> I'm not quite sure what's going on on preparing for upload, but it can > really take quite a long time at least from a users standpoint. I looked at > top while this was going on and noted shotwell was only using one core. Is > there something that is being performed for each photo to be uploaded? If > so maybe the photos could be split into groups and each core could handle > some of the work? Specifically I'm uploading about 80 high res photos to > flickr. > Each time a photo gets uploaded, it has to be "exported" to the temporary folder. This can take some time for large images and/or cases where you've made changes to the image with Shotwell. The export process tends to be more I/O bound than CPU bound, so multi-threading this operation isn't likely to result in a performance increase. That said, I'd be really interested in how long the images took to upload, and how large they are. We're trying to make Shotwell scale better, and this is an area we hadn't considered. Also depending how large these images are, it might be helpful if you could send us one or more sample images for testing on our side. - Eric _______________________________________________ Shotwell mailing list [email protected] http://lists.yorba.org/cgi-bin/mailman/listinfo/shotwell
