Open Stack

On 7/6/2018 9:33 AM, Alan Bishop wrote:
>
> On Fri, Jul 6, 2018 at 10:18 AM Amy Marrich <amy at demarco.com 
> <mailto:amy at demarco.com>> wrote:
>
>     Hey,
>
>     Forwarding to the Dev list as you may get a better response from
>     there.
>
>     Thanks,
>
>     Amy (spotz)
>
>     On Thu, Jul 5, 2018 at 11:30 PM, Keynes Lee/WHQ/Wistron
>     <Keynes_Lee at wistron.com <mailto:Keynes_Lee at 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 ?
>
>
> This has been addressed in [1], but it may not be in the release 
> you're using.
>
> [1] 
> https://github.com/openstack/cinder/commit/373b52404151d80e83004a37d543f825846edea1
>

In addition to the change above we also have 
https://review.openstack.org/#/c/537003/ which should also help with the 
stability issues.  That has been backported as far as Pike.

The change for multiple processes is only in master for the Rocky 
release right now.

Jay

> Alan
>
>         cid:image007.jpg at 01D1747D.DB260110
>
>         	
>
>         *Keynes  Lee **李****俊****賢*
>
>         Direct:
>
>         	
>
>         +886-2-6612-1025
>
>         Mobile:
>
>         	
>
>         +886-9-1882-3787
>
>         Fax:
>
>         	
>
>         +886-2-6612-1991
>
>         	
>
>         E-Mail:
>
>         	
>
>         keynes_lee at wistron.com <mailto:keynes_lee at 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
>         Community at lists.openstack.org
>         <mailto:Community at lists.openstack.org>
>         http://lists.openstack.org/cgi-bin/mailman/listinfo/community
>
>
>     __________________________________________________________________________
>     OpenStack Development Mailing List (not for usage questions)
>     Unsubscribe:
>     OpenStack-dev-request at lists.openstack.org?subject:unsubscribe
>     <http://OpenStack-dev-request@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-request at lists.openstack.org?subject:unsubscribe
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack-dev/attachments/20180706/5346d807/attachment.html>