RE: Proper way to shut down FIO in Linux

[Matt Freel <matt.freel@broadcom.com>]

I'm using it to generate IO -- not necessarily as a benchmark.  I'm running
IO, taking some other measurements, then killing it to kick off a different
workload.  The time it needs to run is not constant -- it depends on a bunch
of different things.

-----Original Message-----
From: Erwan Velu <evelu@redhat.com>
Sent: Wednesday, March 14, 2018 12:47 AM
To: Matt Freel <matt.freel@broadcom.com>
Cc: fio@vger.kernel.org
Subject: Re: Proper way to shut down FIO in Linux

Hey,

Why do you want to kill fio ? That sounds weird to me.

If you need to run your benchmark on constant time then use time_based &
runtime instructions.

----- Mail original -----
De: "Matt Freel" <matt.freel@broadcom.com>
À: fio@vger.kernel.org
Envoyé: Mardi 13 Mars 2018 19:56:10
Objet: Proper way to shut down FIO in Linux

I'm using FIO to run IOs to a number of block devices.  I'm looking for the
proper way to shut down all the threads that are spawned.

I'm doing the following:

/usr/bin/pkill --signal INT fio

Most of the time this works fine, but I do have cases where some of the FIO
processes remain open.  Eventually I get a 300s timeout and then they're
killed.

A couple questions:

1.	When these threads have to be ungracefully killed, do the results
still get counted in the output file?
a.	I'm using JSON output file
2.	Is there a better way I should be killing all the threads?
--
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