From owner-freebsd-hackers@freebsd.org Fri Feb 22 09:06:27 2019 Return-Path: Delivered-To: freebsd-hackers@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 0203B14E1CC6 for ; Fri, 22 Feb 2019 09:06:27 +0000 (UTC) (envelope-from yaneurabeya@gmail.com) Received: from mail-pg1-x529.google.com (mail-pg1-x529.google.com [IPv6:2607:f8b0:4864:20::529]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id EFFA88AD96 for ; Fri, 22 Feb 2019 09:06:25 +0000 (UTC) (envelope-from yaneurabeya@gmail.com) Received: by mail-pg1-x529.google.com with SMTP id 196so818274pgf.13 for ; Fri, 22 Feb 2019 01:06:25 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=lc7SrsI/WfcZ8yl6URh8E1yTTakyx/p3M49DT1DefAQ=; b=Tgk8Nh+zvqsWBsVgVPn5EsmTOmha0Rx+kuEcltnW3EySmtk275I8e6QV0DqwYRa7Pb kyuc7I6suFGY3egW8jjXQpYUdl76bKHCeaBlet/81yKNoDU0JN7WMvyju2bo/TyUAgGc AvGAV8YiW2pFPXZQJpC1HhdCUbmFk1zB3Ul2ctY0Uhlhho/EnPdkv53QzuO3bf/5eZsS UQqLoH0VTFyA65INOyTIQXbfoJ3+QLavwYsTKX/Yvkc4R1usx3AFp2+d5bYsUyN3NHOd sAJw4ZQ/7bwcxbuhh5ZtYOKG5Z6ow7iT7tL9asbSBpJP9/mgi9FHs722+/x7HET98KQe ypMw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=lc7SrsI/WfcZ8yl6URh8E1yTTakyx/p3M49DT1DefAQ=; b=g/1h3+MTS9jZdZFg3s6mzUcTx61avMnq5Syt4+D3SNfNKc4mC16eFAtFcEwZleFMME H9f3HiM0vlcFKZ351Y6XOnI6l5d3jsIjSOPnQiho7Wymgk75OgXAVM+sorI1Yc/X/I2C nSgj2NR8wifXiV+OnPEHhRg/u9yWIFXgweQGf1DfmE8JevM6bq+/3nHs/Tvfy5ahIikY dl50xgHljJbvHvjx7vEdpPrqAy2Qqbg/UYE1hrSyRlyEfIhzjvRrhLQIwUrIgpTdcGhV q20d+dn6tKEM15Mi/x4LXQmQWXnPiheuvXLCO/LgDkg5UfxPW0KBRZPMIVAgFgYQMlei fQZg== X-Gm-Message-State: AHQUAuYpJpCv+cfWnG3jUdD6kSlOJnw80rRTHFTQT3g5QCEMvchktih/ YOmA7kzk94f4e1o+fsxJ/sH1H7ME X-Google-Smtp-Source: AHgI3IaSIljDBqytiQthkaDUDDYsO6/2UVLfR3LHNBcIHACBXyGOONIolxWRegO7DoQHVV+l+b224A== X-Received: by 2002:a62:57dd:: with SMTP id i90mr3183010pfj.154.1550826384670; Fri, 22 Feb 2019 01:06:24 -0800 (PST) Received: from [10.61.32.242] (50-255-30-162-static.hfc.comcastbusiness.net. [50.255.30.162]) by smtp.gmail.com with ESMTPSA id g136sm3244359pfb.154.2019.02.22.01.06.23 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Fri, 22 Feb 2019 01:06:23 -0800 (PST) Content-Type: text/plain; charset=us-ascii Mime-Version: 1.0 (Mac OS X Mail 12.2 \(3445.102.3\)) Subject: Re: Any ideal way to run FIO benchmarking for NVMEe devices in FreeBSD From: Enji Cooper In-Reply-To: Date: Fri, 22 Feb 2019 01:06:22 -0800 Cc: FreeBSD Hackers Content-Transfer-Encoding: quoted-printable Message-Id: <0E136DED-C1AD-481C-B243-C943D4F8D9C5@gmail.com> References: To: Rajesh Kumar X-Mailer: Apple Mail (2.3445.102.3) X-Rspamd-Queue-Id: EFFA88AD96 X-Spamd-Bar: ------ Authentication-Results: mx1.freebsd.org; dkim=pass header.d=gmail.com header.s=20161025 header.b=Tgk8Nh+z; dmarc=pass (policy=none) header.from=gmail.com; spf=pass (mx1.freebsd.org: domain of yaneurabeya@gmail.com designates 2607:f8b0:4864:20::529 as permitted sender) smtp.mailfrom=yaneurabeya@gmail.com X-Spamd-Result: default: False [-6.34 / 15.00]; RCVD_VIA_SMTP_AUTH(0.00)[]; FREEMAIL_FROM(0.00)[gmail.com]; R_SPF_ALLOW(-0.20)[+ip6:2607:f8b0:4000::/36]; MV_CASE(0.50)[]; RCVD_COUNT_THREE(0.00)[3]; TO_DN_ALL(0.00)[]; DKIM_TRACE(0.00)[gmail.com:+]; RCPT_COUNT_TWO(0.00)[2]; DMARC_POLICY_ALLOW(-0.50)[gmail.com,none]; MX_GOOD(-0.01)[cached: alt3.gmail-smtp-in.l.google.com]; FREEMAIL_TO(0.00)[gmail.com]; FROM_EQ_ENVFROM(0.00)[]; RCVD_TLS_LAST(0.00)[]; MIME_TRACE(0.00)[0:+]; FREEMAIL_ENVFROM(0.00)[gmail.com]; ASN(0.00)[asn:15169, ipnet:2607:f8b0::/32, country:US]; MID_RHS_MATCH_FROM(0.00)[]; DWL_DNSWL_NONE(0.00)[gmail.com.dwl.dnswl.org : 127.0.5.0]; ARC_NA(0.00)[]; NEURAL_HAM_MEDIUM(-1.00)[-1.000,0]; R_DKIM_ALLOW(-0.20)[gmail.com:s=20161025]; FROM_HAS_DN(0.00)[]; NEURAL_HAM_SHORT(-0.98)[-0.978,0]; NEURAL_HAM_LONG(-1.00)[-1.000,0]; MIME_GOOD(-0.10)[text/plain]; PREVIOUSLY_DELIVERED(0.00)[freebsd-hackers@freebsd.org]; TO_MATCH_ENVRCPT_SOME(0.00)[]; RCVD_IN_DNSWL_NONE(0.00)[9.2.5.0.0.0.0.0.0.0.0.0.0.0.0.0.0.2.0.0.4.6.8.4.0.b.8.f.7.0.6.2.list.dnswl.org : 127.0.5.0]; IP_SCORE(-2.85)[ip: (-9.59), ipnet: 2607:f8b0::/32(-2.61), asn: 15169(-1.99), country: US(-0.07)] X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 22 Feb 2019 09:06:27 -0000 > On Feb 22, 2019, at 12:51 AM, Rajesh Kumar wrote: >=20 > Hi, >=20 > I am trying to run FIO benchmark test with NVMe devices and see how = FreeBSD > performs. There are lot of variables and combination. So, can anyone > suggest a Ideal way to do FIO benchmarking in FreeBSD? My intent is to > check what is the maximum throughput and IOPS the device delivers in > FreeBSD. >=20 > Few questions regarding the same, >=20 > 1. Should we use "posixaio" as the ioengine (or) something else? > 2. Should we use single thread (or) multiple threads for test? If > multiple threads, how can we decide on the optimal thread count? > 3. Should we use "raw device files" (Eg: nvme namespace file - > /dev/nvme0ns1) without filesystem (or) use a mounted filesystem with = a > regular file (Eg: /mnt/nvme/test1). Looks like raw device files give = better > numbers. > 4. Should we use a shared file (or) one file per thread? > 5. I believe 1Job should be fine for benchmarking. (or) should we = try > multiple jobs? >=20 > Please let me know your suggestions. Also, please suggest performance > tuning methods for NVMe and storage devices in general. Hi Rajesh, Is there a data sheet for the NVMe device? Cheers, -Enji=