This is something we're working on (I work with the author of the patch you referenced) but the refactoring of the backup code in this cycle has made progress challenging. If you have a patch that works, please submit it, even if it needs some cleaning up, we'd be happy to work with you on and testing, cleaning up and improvements.
The basic problem is that backup is CPU bound (compression, ssl) so the existing parallelisation techniques used in cinder don't help. Running many cinder-backup processes can give you good aggregate throughput if you're running many backups at once, but this appears not to be a common case, even in a large public cloud. On 1 April 2015 at 11:41, Jae Sang Lee <hyan...@gmail.com> wrote: > Hi, > > I tested Swift backup driver in Cinder-backup and that performance isn't > high. > In our test environment, The average time for backup 50G volume is 20min. > > > I found a patch for this that add multi thread for swift backup driver( > https://review.openstack.org/#/c/111314) but It's also too slow. It looks > like that patch doesn't implement thread properly. > > Is there any improvement way about this? I'd appreciate other's thoughts > on these issues. > > Thanks. > > __________________________________________________________________________ > OpenStack Development Mailing List (not for usage questions) > Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev > > -- Duncan Thomas
__________________________________________________________________________ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
