Open Stack

Hi Pangj,

First, make sure you have an updated version of swift-bench.  There was a
bug where it was relying on python-swiftclient to setup eventlet, but when
eventlet was removed from swiftclient, that caused swift-bench to not run
requests concurrently.

There are quite a few things that should be checked after that:

1.  Check the logs to make sure there are no major errors.  Swift is
designed to work around failures, but failures will add some latency to
requests.  This can be anything from configuration issues, ring issues,
connectivity issues, etc.

2.  Once you have validated that the system is running correctly, observe
the system while under load.  I would start with the proxies and watch the
CPU usage of the proxy processes to see if they are maxing out the CPU.
 Increase the workers if they are, or add more proxies if you are running
out of total CPU.  Do the same for the other services if needed.

3.  I noticed that you have one server for accounts/containers.  IO for
container services can be a bit of a bottleneck for PUTs, since every
object PUT is going to send an update to the container listing.  If you
start seeing timeouts in the object-server logs trying to do container
updates, then some tweaking here might need to be done.

Those are some good starting points, and hope that helps you get further
along.

--
Chuck


On Mon, Sep 2, 2013 at 6:51 AM, pangj <pangj at laposte.net> wrote:

> Hi,
>
> We have benched the swift, the cluster is with one proxy server, one
> combined account/container server, five object servers. All are separated
> physical servers.
>
> We benched from 12 clients (each with 200 threads), got the results as
> below:
>
> | node   |   PUT |   GET | DELETE |
>    |--------+-------+-------+----**----|
>    | sb2 A  |  35.6 |  57.1 |     44 |
>    | sb2 B  |  35.6 |  56.1 |   43.4 |
>    | sb3 A  |  35.4 |  58.1 |   43.4 |
>    | sb3 B  |  35.6 |  56.1 |   43.4 |
>    | ad61 A |  35.5 |  57.2 |   43.8 |
>    | ad61 B |  35.5 |  55.2 |   43.5 |
>    | sb64 A |  35.4 |  53.4 |   43.7 |
>    | sb64 B |  35.5 |  54.9 |   43.5 |
>    | sb65 A |  35.7 |  53.3 |   43.6 |
>    | sb65 B |  35.6 |  52.5 |   44.1 |
>    | sb27 A |  35.4 |  49.4 |   44.1 |
>    | sb27 B |  35.4 |  51.1 |   43.9 |
>    |--------+-------+-------+----**----|
>    | total  | 426.2 | 654.4 |  524.4 |
>
>
> The total IOPS for PUT is 426, means 426 PUT requests per second.
> But our application design requires 3000 PUT requests per second.
> So how to improve swift's performance to match the requirement?
>
> Thanks.
>
> ______________________________**_________________
> Mailing list: http://lists.openstack.org/**cgi-bin/mailman/listinfo/**
> openstack <http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack>
> Post to     : openstack at lists.openstack.org
> Unsubscribe : http://lists.openstack.org/**cgi-bin/mailman/listinfo/**
> openstack <http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack/attachments/20130903/8c1bdb20/attachment.html>