[Bug general/31729] New: the huge-file test is too sloooow

[Bug general/31729] New: the huge-file test is too sloooow

[fche at redhat dot com]

https://sourceware.org/bugzilla/show_bug.cgi?id=31729

            Bug ID: 31729
           Summary: the huge-file test is too sloooow
           Product: elfutils
           Version: unspecified
            Status: NEW
          Severity: normal
          Priority: P2
         Component: general
          Assignee: unassigned at sourceware dot org
          Reporter: fche at redhat dot com
                CC: elfutils-devel at sourceware dot org
  Target Milestone: ---

run-large-elf-file.sh does a little speed gating predicate before launching its
4GB I/O test, but it is IMO too optimistic.  On my box, where the source/build
trees are often NFS-mounted, the 100MB/s initial test passes, but the whole
test takes O(minutes).  It would be better if the the check plopped the test
files onto something like /var/tmp, which is apprx. guaranteed to be local
disk.

-- 
You are receiving this mail because:
You are on the CC list for the bug.

[Bug general/31729] the huge-file test is too sloooow

[mark at klomp dot org]

https://sourceware.org/bugzilla/show_bug.cgi?id=31729

Mark Wielaard <mark at klomp dot org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |mark at klomp dot org

--- Comment #1 from Mark Wielaard <mark at klomp dot org> ---
Maybe we should just up the test to try to get at least 200MB or 500MB? So
change the timeout from 10s to 5s or 2s ? Locally timeout -s9 2s dd conv=fsync
if=/dev/zero of=tempfile bs=1M count=1K works just fine.

But trying to find a different location/file system for the tests sound OK too.
Note that there are two tests to see if the location/disk can be used:

# These tests need lots of disk space since they test files > 4GB.
# Skip if there just isn't enough (2.5 * 4 = 10GB).
space_available=$[$(stat -f --format="%a*%S" .)/(1024 * 1024 * 1024)]
echo "space_available: $space_available"
if test $space_available -lt 10; then
  echo "Not enough disk space, need at least 10GB available"
  exit 77
fi

and

# Make sure the disk is reasonably fast, should be able to write 100MB/s
fast_disk=1
timeout -s9 10s dd conv=fsync if=/dev/zero of=tempfile bs=1M count=1K \
  || fast_disk=0; rm tempfile
if test $fast_disk -eq 0; then
  echo "File system not fast enough, need at least 100MB/s"
  exit 77
fi

They probably should be combined and then tried on some reasonable sounding
locations, "/var/tmp", "/tmp" and "." ? Then pick the one with the highest
speed?

-- 
You are receiving this mail because:
You are on the CC list for the bug.