Open Stack

Using RamDisk to simulate spindles

+Hugo Kuo+
hugo at swiftstack.com
tonytkdk at gmail.com
+886 935004793


2013/9/3 Jonathan Lu <jojokururu at gmail.com>

> Hi, pangj
>     While putting small objects, the bottleneck will not be the network
> bandwidth, and the server's cpu/mem will be low. It will be a matter of
> inode and cache. You can check the iowait of your storage node server and
> it may be a "filesystem" problem. As a estimate of the performance of your
> swift, take a look at this:
> http://www.zmanda.com/blogs/?**p=894 <http://www.zmanda.com/blogs/?p=894>
>
>     Robert van Leeuwen once post a report of their experience in the mail
> list and I think it's such a good sharing.
> http://engineering.spilgames.**com/openstack-swift-lots-**small-files/<http://engineering.spilgames.com/openstack-swift-lots-small-files/>
>
>     Hope it helpful.
>
> Jonathan Lu
>
>
> On 2013/9/3 13:53, pangj wrote:
>
>> For each test file the size is 4KB.
>> Network connection is 1Gb.
>> But the bandwidth never got full, it's about only 70 - 80 Mb at peak.
>> And all servers' cpu/mem usage are low.
>> Thanks.
>>
>> On 2013-9-3 13:32, Jonathan Lu wrote:
>>
>>> Hi,
>>>      What is the average size of the objects? And your network
>>> condition? Maybe the bottleneck of performance is not Swift, but the
>>> network or other things.
>>>
>>> Best Regards
>>> Jonathan Lu
>>>
>>> On 2013/9/2 19:51, pangj 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>
>>>>
>>>
>>>
>>>
>>
>
> ______________________________**_________________
> 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/249d9c5f/attachment.html>