Open Stack

Thanks Hugo, Clay and Pete. I asked this question based on some limited
knowledge I had about Swift and while trying to understand more based on
the source code. I'll try and run some more experiments and revert back
with questions if any. The general system tuning guidelines definitely seem
helpful.


On Mon, Jan 13, 2014 at 10:46 AM, Pete Zaitcev <zaitcev at redhat.com> wrote:

> On Fri, 10 Jan 2014 15:25:02 -0800
> Shrinand Javadekar <shrinand at maginatics.com> wrote:
>
> > I see that the proxy-server already has a "workers" config option.
> However,
> > looks like that is the # of threads in one proxy-server process.
>
> Not so. Workers are separate Linux processes. Look at os.fork() in
> run_sever(). Perhaps you're looking for the 'max_client' option,
> which restricts the green pool passed to eventlet in each of the workers.
>
> > It does not send the request and go back do accept more requests.
>
> The requests each gets a green thread inside the eventlet, by way
> of monkey-patching of some syscalls.
>
> Anyhow, please be more specific about the numbers you see on your
> proxies, e.g. how many IOPS, GHz, workers, and so on. Otherwise
> it's poinless to speculate about your bottleneck case and its causes.
>
> -- Pete
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack/attachments/20140113/5236cfed/attachment.html>