Bug 788716 - Write-perf reports useless results due to use of /dev/urandom
Summary: Write-perf reports useless results due to use of /dev/urandom
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: GlusterFS
Classification: Community
Component: glusterd
Version: mainline
Hardware: Unspecified
OS: Unspecified
unspecified
low
Target Milestone: ---
Assignee: Jeff Darcy
QA Contact: Anush Shetty
URL:
Whiteboard:
Depends On:
Blocks: 817967
TreeView+ depends on / blocked
 
Reported: 2012-02-08 21:35 UTC by Jeff Darcy
Modified: 2013-07-24 18:01 UTC (History)
2 users (show)

Fixed In Version: glusterfs-3.4.0
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2013-07-24 18:01:43 UTC
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Embargoed:


Attachments (Terms of Use)

Description Jeff Darcy 2012-02-08 21:35:43 UTC
Contrary to popular belief, urandom is not free.  In generic testing, a simple dd using /dev/urandom performs at about half the performance compared to /dev/zero for fully synchronous I/O, about 1/20 for buffered I/O (i.e. the difference on the input side is mostly masked when waiting for disks on the output side).  There's probably we can do about read-perf without platform-specific flushing of kernel buffers, but for write-perf we can at least get more accurate and useful numbers by using /dev/zero instead.

Comment 1 Anand Avati 2012-02-09 06:51:12 UTC
CHANGE: http://review.gluster.com/2728 (Use /dev/zero instead of /dev/urandom to get realistic numbers.) merged in master by Anand Avati (avati)


Note You need to log in before you can comment on or make changes to this bug.