openstack team mailing list archive

[Vishvananda Ishaya <vishvananda@xxxxxxxxx>]

In addition to the rate limiting changes, you can also run multiple copies of nova-api on different ports and put a load balancer (like ha-proxy) in front. You may have to set up your proxy to add an X-Forwarded-For header and specify the
--use_forwarded_for
flag to get things like metadata to work.

Vish

On Dec 21, 2011, at 4:38 PM, Huang Zhiteng wrote:

> I have a relevant question about API throughput.  I'm using Diablo release version and I found out that there's only one process of nova-api to handle all API requests from even different users.  That results very low (<10) API throughput (definition: API requests handled per second).  Similar symptom was observed back in Cactus release.  
> 
> Is there anyway to configure API service to run in multi-threaded mode so that it can utilize multi-core hardware?  I'd really appreciate if anyone can also shed some light on why Nova API was designed to work in this way.  Thank you in advance.
> 
> On Tue, Dec 20, 2011 at 3:28 AM, Day, Phil <philip.day@xxxxxx> wrote:
> Hi Folks,
> 
>  
> 
> Is there a file that can be used to configure the API rate limits for the OS API on a per user basis ?
> 
>  
> 
> I can see where the default values are set in the code, but it looks as if there should be a less brutal configuration mechanism to go along with this ?
> 
>  
> 
> Thanks
> 
> Phil
> 
> 
> _______________________________________________
> Mailing list: https://launchpad.net/~openstack
> Post to     : openstack@xxxxxxxxxxxxxxxxxxx
> Unsubscribe : https://launchpad.net/~openstack
> More help   : https://help.launchpad.net/ListHelp
> 
> 
> 
> 
> -- 
> Regards
> Huang Zhiteng
> _______________________________________________
> Mailing list: https://launchpad.net/~openstack
> Post to     : openstack@xxxxxxxxxxxxxxxxxxx
> Unsubscribe : https://launchpad.net/~openstack
> More help   : https://help.launchpad.net/ListHelp