Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA1:256) (Exim 4.89) (envelope-from ) id 1go9R2-0000HL-6v for pgsql-performance@arkaria.postgresql.org; Mon, 28 Jan 2019 16:06:56 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.89) (envelope-from ) id 1go9R1-0001F6-1T for pgsql-performance@arkaria.postgresql.org; Mon, 28 Jan 2019 16:06:55 +0000 Received: from makus.postgresql.org ([2001:4800:3e1:1::229]) by malur.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA1:256) (Exim 4.89) (envelope-from ) id 1go9R0-0001Ez-NJ for pgsql-performance@lists.postgresql.org; Mon, 28 Jan 2019 16:06:54 +0000 Received: from nrm-vir-mail-01.normation.com ([212.129.19.75]) by makus.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA1:256) (Exim 4.89) (envelope-from ) id 1go9Qt-0007dF-HI for pgsql-performance@lists.postgresql.org; Mon, 28 Jan 2019 16:06:53 +0000 Received: from [192.168.90.10] (republique-1.normation.com [78.249.200.184]) by nrm-vir-mail-01.normation.com (Postfix) with ESMTPSA id C5F282238F0; Mon, 28 Jan 2019 17:06:14 +0100 (CET) Subject: Re: Benchmarking: How to identify bottleneck (limiting factor) and achieve "linear scalability"? To: Saurabh Nanda Cc: Jeff Janes , pgsql-performance@lists.postgresql.org References: <71a5e04d-8f2f-385a-2789-c78bf780a622@normation.com> From: Nicolas Charles Message-ID: <56533b5c-3244-efc6-a869-b9114595cea7@normation.com> Date: Mon, 28 Jan 2019 17:06:14 +0100 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:60.0) Gecko/20100101 Thunderbird/60.2.1 MIME-Version: 1.0 In-Reply-To: Content-Type: multipart/alternative; boundary="------------067876133A53EE450A47A0C3" Content-Language: fr List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Precedence: bulk This is a multi-part message in MIME format. --------------067876133A53EE450A47A0C3 Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 8bit Le 28/01/2019 à 16:55, Saurabh Nanda a écrit : > > You should probably include the detailed hardware you are working > on - > especially for the SSD, the model can have a big impact, as well > as its > wear. > > > What's the best tool to get meaningful information for SSD drives? > smartctl is a good start Nicolas --------------067876133A53EE450A47A0C3 Content-Type: text/html; charset=utf-8 Content-Transfer-Encoding: 8bit Le 28/01/2019 à 16:55, Saurabh Nanda a écrit :
You should probably include the detailed hardware you are working on -
especially for the SSD, the model can have a big impact, as well as its
wear.

What's the best tool to get meaningful information for SSD drives?

smartctl is a good start

Nicolas

--------------067876133A53EE450A47A0C3--