Randy & Sakib & I took a look at using `flock` instead of `dd`
Initial results to see if it works:
the results are the following when tested with `stress --timeout 20'
stress: info: [44041] dispatching hogs: 800 cpu, 0 io, 800 vm, 800 hdd:
0.74 seconds to flock my home directory
at this load,
Hi Sakib,
On Mon, 2021-03-08 at 15:46 -0500, Sakib Sajal wrote:
> Randy and I could directly use autobuilders and make the necessary
> changes to run the tests/experiments, if you prefer to do it yourself,
> read on for more details.
I'm happy to have the help. I'm thinking that rather than
On 2021-03-08 12:33 p.m., Richard Purdie wrote:
[Please note: This e-mail is from an EXTERNAL e-mail address]
On Mon, 2021-03-08 at 09:50 -0500, Randy MacLeod wrote:
On 2021-03-07 3:58 p.m., Sakib Sajal wrote:
+timeout $1 dd if=/dev/zero of=/tmp/foo bs=1024 count=$2 >/dev/null 2>&1
+
+if [
On Mon, 2021-03-08 at 09:50 -0500, Randy MacLeod wrote:
> On 2021-03-07 3:58 p.m., Sakib Sajal wrote:
> > +timeout $1 dd if=/dev/zero of=/tmp/foo bs=1024 count=$2 >/dev/null 2>&1
> > +
> > +if [ $? -ne 0 ]
> > +then
> > +top -b -n 1
> > +else
> > +echo "success"
>
> Do we need
On 2021-03-07 3:58 p.m., Sakib Sajal wrote:
oe-timeout-dd-test tries to write number of
kilobytes to the filesystem within a specified
. The purporse of this script is to find
s/purporse/purpose/
which part of the build system puts stress on the
filesystem io and log all the processes.
To
oe-timeout-dd-test tries to write number of
kilobytes to the filesystem within a specified
. The purporse of this script is to find
which part of the build system puts stress on the
filesystem io and log all the processes.
To use and monitor a build, add to local.conf:
BB_HEARTBEAT_EVENT = ""
