On 26 January 2018 at 15:04, Florence ROUGER JUNG < florence.rouger-jung@st.com> wrote:
See following attachments which contains some results of 4 commands executed in same Lava job or without Lava
Each test takes around 3/4 minutes. Is it some periodically action from LAVA to check if DUT is always available (ping/ssh ... ) which can explain these differences of results ?
There is no periodic action from LAVA during execution of a test shell. LAVA sends nothing to the DUT once the device starts execution of the test shell.
Please explain *what* the differences are. The numbers in the files you attached are essentially meaningless as we're not familiar with what IOZone is meant to produce. It looks just like random divergence as would happen by chance, to me.
Florence
-----Original Message----- From: Steve McIntyre [mailto:steve.mcintyre@linaro.org] Sent: vendredi 26 janvier 2018 15:14 To: Florence ROUGER JUNG florence.rouger-jung@st.com Cc: Remi Duraffort remi.duraffort@linaro.org; Neil Williams < neil.williams@linaro.org>; lava-users@lists.linaro.org Subject: Re: [Lava-users] IOZone test to measure performance of DUT
On Fri, Jan 26, 2018 at 02:04:52PM +0000, Florence ROUGER JUNG wrote:
That's right, at first I used following command and there was some
output to the terminal
iozone $OPT -f /mnt_emmc/tmp/iozone.tmp | tee result.logBut now I redirect output iozone $OPT -f /mnt_emmc/tmp/iozone.tmp > iozone.log 2>&1
performance
are better but remain not homogeneous with Lava
OK, that does surprise me. I could imagine that running a test with lots of output to the serial port could slow things down, but if you're redirecting everything then it should be making no difference at all. What kind of variance are you seeing?
Cheers,
Steve McIntyre steve.mcintyre@linaro.org http://www.linaro.org/ Linaro.org | Open source software for ARM SoCs