All of lore.kernel.org
 help / color / mirror / Atom feed
From: Alireza Haghdoost <alireza@cs.umn.edu>
To: Kurt_Dorsey@dell.com
Cc: jeff.furlong@hgst.com, "fio@vger.kernel.org" <fio@vger.kernel.org>
Subject: Re: Monitor IO while fio is running
Date: Mon, 14 Mar 2016 13:36:31 -0500	[thread overview]
Message-ID: <CAB-428nKSCiuYQphBf7Ti0saWM8WkjL7kdr6wYw7ePxgKjHWXw@mail.gmail.com> (raw)
In-Reply-To: <c0aff70ec5314c33a41556b828fb7bd1@AUSX13MPC107.AMER.DELL.COM>

You should be able to redirect it to a file. Would you mind share with
us how you set the redirection?

On Mon, Mar 14, 2016 at 1:03 PM,  <Kurt_Dorsey@dell.com> wrote:
> Thank you Jeff for the reply.
>
> I have been playing around with this but unfortunately I cannot get the output to be outputted anywhere other than the screen / terminal.  I  have tried redirecting it to a txt file and parsing with with a python script but nothing ever gets output. (It only outputs to the screen)
>
> I haven't done C programming in years but I am trying to figure out from the code why this is.  I see in the eta.c file
>
> void display_thread_status(struct jobs_eta *je)
> {
> ...
>        printf("%s", output);
>
>         if (!eta_new_line_init) {
>                 fio_gettime(&disp_eta_new_line, NULL);
>                 eta_new_line_init = 1;
>         } else if (eta_new_line && mtime_since_now(&disp_eta_new_line) > eta_new_line) {
>                 fio_gettime(&disp_eta_new_line, NULL);
>                 eta_new_line_pending = 1;
>         }
>
>         fflush(stdout);
>
>
> It prints everything to the screen but I cannot redirect it at all
>
> Thoughts?
> Thank you,
> Kurt
>
>
> -----Original Message-----
> From: Jeff Furlong [mailto:jeff.furlong@hgst.com]
> Sent: Monday, March 14, 2016 12:56 PM
> To: Dorsey, Kurt ; fio@vger.kernel.org
> Subject: RE: Monitor IO while fio is running
>
> You might add --eta=always and --eta-newline=1 to get the current IOPs rate every 1s, printed to stdout. You can parse that current IOPs rate via a script and do something. I believe the IOPs rate is recalculated every 1s, not the average from beginning of test.
>
> Not sure why --eta and --eta-newline is not in the latest HOWTO notes.
>
> Regards,
> Jeff
>
> -----Original Message-----
> From: fio-owner@vger.kernel.org [mailto:fio-owner@vger.kernel.org] On Behalf Of Kurt_Dorsey@Dell.com
> Sent: Saturday, March 12, 2016 2:20 PM
> To: fio@vger.kernel.org
> Subject: Monitor IO while fio is running
>
> I may just not know how to do this
> I know about the ability to touch /tmp/fio-dump-status which will dump the output of fio to a file or stdout while the test is running. What I am looking for is to be able to dump the write_iops_log while fio is running so that I can see the point in time average IOps for a given interval For example if I have log_avg_msec=60000 it will write an iops.log file with 60second intervals, unfortunately this file doesn't get created until fio exits. Is there a way to get this to dump on a regular basis (or by touching a file in /tmp) so that I can tail the output?
>
> I am looking for a way to get point in time status via a script and the output from tmp-dump-status only gives me averages from the start of time rather than the last interval
>
> Thank you,
> Kurt
> --
> To unsubscribe from this list: send the line "unsubscribe fio" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
> Western Digital Corporation (and its subsidiaries) E-mail Confidentiality Notice & Disclaimer:
>
> This e-mail and any files transmitted with it may contain confidential or legally privileged information of WDC and/or its affiliates, and are intended solely for the use of the individual or entity to which they are addressed. If you are not the intended recipient, any disclosure, copying, distribution or any action taken or omitted to be taken in reliance on it, is prohibited. If you have received this e-mail in error, please notify the sender immediately and delete the e-mail in its entirety from your system.
> --
> To unsubscribe from this list: send the line "unsubscribe fio" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html

  parent reply	other threads:[~2016-03-14 18:39 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-03-12 22:20 Monitor IO while fio is running Kurt_Dorsey
2016-03-14 17:55 ` Jeff Furlong
2016-03-14 18:03   ` Kurt_Dorsey
2016-03-14 18:19     ` Jeff Furlong
2016-03-14 18:36     ` Alireza Haghdoost [this message]
2016-03-14 19:26       ` Kurt_Dorsey
2016-03-14 20:40         ` Wolford, Jeff (HPE Servers - Web Scale performance)
2016-03-15 13:59           ` Kurt_Dorsey
2016-03-14 18:07   ` Kudryavtsev, Andrey O

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=CAB-428nKSCiuYQphBf7Ti0saWM8WkjL7kdr6wYw7ePxgKjHWXw@mail.gmail.com \
    --to=alireza@cs.umn.edu \
    --cc=Kurt_Dorsey@dell.com \
    --cc=fio@vger.kernel.org \
    --cc=jeff.furlong@hgst.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.