Open Stack

Top shows the CPUs pegged at ~100%. Writes are done by a tool built
in-house which is similar in functionality to other object store
benchmarking tools. As I mentioned, there are 256 parallel object
writes (PUTS), each of 256K bytes.

On Thu, Apr 2, 2015 at 9:21 PM, Yogesh Girikumar <yogeshg1987 at gmail.com> wrote:
> Also how are you doing the object writes to benchmark it? Are you using dd?
>
> On 3 April 2015 at 09:50, Yogesh Girikumar <yogeshg1987 at gmail.com> wrote:
>>
>> What does top say?
>>
>> On 3 April 2015 at 02:34, Shrinand Javadekar <shrinand at maginatics.com>
>> wrote:
>>>
>>> Hi,
>>>
>>> I have a single node Swift instance. It has 16 cpus, 8 disks and 64GB
>>> memory. As part of testing, I am doing 256 object writes in parallel
>>> for ~10 mins. Each object is also 256K bytes in size.
>>>
>>> While my experiment is running, I see that the CPU utilization of the
>>> box is always ~100%. I am trying to understand what is causing this
>>> high CPU utilization. Some of this could be attributed to:
>>>
>>> 1. MD5 checksum calculation done to verify every PUT.
>>> 2. MD5 checksum calculation by the auditor (if it runs during this
>>> interval).
>>> 3. Hash calculation of the path to decide which partition the object goes
>>> to.
>>>
>>> Are there any other CPU intensive operations happening on the system
>>> that I should be aware of?
>>>
>>> I see that the proxy-server has a "PUT" queue. Is there some
>>> processing of the data in this queue? Would simply putting data in and
>>> out of the queue, streaming the data between the proxy and object
>>> server use considerable CPU?
>>>
>>> Thanks in advance.
>>> -Shri
>>>
>>> _______________________________________________
>>> Mailing list:
>>> 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
>>
>>
>