Re: FIO - Client and Server - Suggestion

[Jens Axboe <axboe@kernel.dk>]

On 2014-10-13 08:37, Jens Axboe wrote:
> On 2014-10-13 07:37, Neto, Antonio Jose Rodrigues wrote:
>>
>>
>> On 10/12/14, 8:27 PM, "Jens Axboe" <axboe@kernel.dk> wrote:
>>
>>> On 2014-10-12 14:28, Neto, Antonio Jose Rodrigues wrote:
>>>>
>>>>
>>>>
>>>>
>>>>> On Oct 12, 2014, at 3:26 PM, Jens Axboe <axboe@kernel.dk> wrote:
>>>>>
>>>>>> On 2014-10-12 13:12, Jens Axboe wrote:
>>>>>>> On 2014-10-12 09:26, Neto, Antonio Jose Rodrigues wrote:
>>>>>>> Just applied the patch and it's perfect.
>>>>>>>
>>>>>>> Please see below:
>>>>>>>
>>>>>>> Nossa Senhora:fiop neto$ ./fio --client 10.61.109.151
>>>>>>> --remote-config
>>>>>>> /root/fiop/iotest --client 10.61.109.152 --remote-config
>>>>>>> /root/fio/iotest
>>>>>>> hostname=s2, be=0, 64-bit, os=Linux, arch=x86-64,
>>>>>>> fio=fio-2.1.13-59-gaa7bc, flags=1
>>>>>>> hostname=s1, be=0, 64-bit, os=Linux, arch=x86-64,
>>>>>>> fio=fio-2.1.13-59-gaa7bc, flags=1
>>>>>>> <s2> fio: unable to open '/root/fio/iotest' job file
>>>>>>> <s1> workload: (g=0): rw=write, bs=32K-32K/32K-32K/32K-32K,
>>>>>>> ioengine=libaio, iodepth=4
>>>>>>> <s1> ...
>>>>>>> <s1> Starting 64 threads
>>>>>>> Jobs: 64 (f=1024): [W(64)] [43.3% done] [882.5M/0K/0K /s] [27.6K/0/0
>>>>>>> iops]
>>>>>>> [eta 00m:34s]
>>>>>>
>>>>>> Great, at least that took care of that issue. As to missing output
>>>>>> from
>>>>>> one client, I've seen that here before, I will look into that. It's a
>>>>>> separate issue.
>>>>>
>>>>> For the above one, s2 never started since it could not find the config
>>>>> file you gave it. Have you seen missing final output for cases where
>>>>> the jobs did all start? This particular one does not look valid.
>>>>>
>>>>> --
>>>>> Jens Axboe
>>>>>
>>>>
>>>>
>>>> Yes. I did.
>>>>
>>>> I ran using both servers but the output was showing the latest client -
>>>> s2
>>>
>>> Odd. Can you reproduce and send the output of such a run?
>>>
>>> --
>>> Jens Axboe
>>
>>
>> Hi Jens,
>>
>> This is neto from Brazil
>>
>> How are you?
>>
>> I believe the issue could be formatting....
>>
>> Also, when running from both clients, seem to me unified_rw_reporting is
>> not working... I do not have the total for all clients....
>
> unified_rw_reporting groups reads, writes, and discards into the same
> reporting bucket. I'm assuming you mean that group_reporting doesn't
> work for multiple connections? That's the option that groups multiple
> jobs together for reporting. And yes, that's not supported right now for
> multiple connections. But it could be, it's not that different from the
> ETA which is grouped as it would be on a local run.

Try newest -git. It now outputs an "All clients" summed section, if you 
have more than 1 client.

-- 
Jens Axboe