On 06/07, Amy Marrich wrote: > Hey, > > Forwarding to the Dev list as you may get a better response from there. > > Thanks, > > Amy (spotz) >
Hi, I included a good number of improvements regarding bottlenecks on the backup service in recent releases, some of them are automatic, and others need configuration tweaks. But even in older releases there are a couple of things that can be done to mitigate/fix this situation, depending on the release you are using. In general I recommend: - Using more than one process: Use the "backup_processes" option, if available, to run multiple subprocesses (like Alan suggested). If this option is not available run multiple backup services on the same machine (like Duncan suggests), but use a configuration overlay to change the host configuration option. That way you won't have problems with one service messing up the others' resources at start time. - Increase the native thread pool size: This is even more critical if you are using RBD backend: Using the "backend_native_threads_pool_size" configuration option [1], if available, we can increase the default size. If your deployment doesn't have this option, you can still use environmental variable "EVENTLET_THREADPOOL_SIZE" to set it in any release. Cheers, Gorka. [1]: https://github.com/openstack/cinder/commit/e570436d1cca5cfa89388aec8b2daa63d01d0250 > On Thu, Jul 5, 2018 at 11:30 PM, Keynes Lee/WHQ/Wistron < > keynes_...@wistron.com> wrote: > > > Hi > > > > > > > > When making “cinder backup-create” > > > > We found the process “cinder-backup” use 100% util of 1 CPU core on an > > OpenStack Controller node. > > > > It not just causes a bad backup performance, also make the > > openstack-cinder-backup unstable. > > > > Especially when we make several backup at the same time. > > > > > > > > The Controller Node has 40 CPU cores. > > > > Can we assign more CPU resources to cinder-backup ? > > > > > > > > > > > > > > > > > > > > > > > > > > > > [image: cid:image007.jpg@01D1747D.DB260110] > > > > *Keynes Lee **李* *俊* *賢* > > > > Direct: > > > > +886-2-6612-1025 > > > > Mobile: > > > > +886-9-1882-3787 > > > > Fax: > > > > +886-2-6612-1991 > > > > > > > > E-Mail: > > > > keynes_...@wistron.com > > > > > > > > > > > > > > *---------------------------------------------------------------------------------------------------------------------------------------------------------------* > > > > *This email contains confidential or legally privileged information and is > > for the sole use of its intended recipient. * > > > > *Any unauthorized review, use, copying or distribution of this email or > > the content of this email is strictly prohibited.* > > > > *If you are not the intended recipient, you may reply to the sender and > > should delete this e-mail immediately.* > > > > > > *---------------------------------------------------------------------------------------------------------------------------------------------------------------* > > > > _______________________________________________ > > Community mailing list > > commun...@lists.openstack.org > > http://lists.openstack.org/cgi-bin/mailman/listinfo/community > > > > > __________________________________________________________________________ > 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 __________________________________________________________________________ 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