From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from lists.gentoo.org (pigeon.gentoo.org [208.92.234.80]) by finch.gentoo.org (Postfix) with ESMTP id BA27613877A for ; Thu, 19 Jun 2014 08:40:25 +0000 (UTC) Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id 97EDAE085D; Thu, 19 Jun 2014 08:40:18 +0000 (UTC) Received: from mail-pa0-f47.google.com (mail-pa0-f47.google.com [209.85.220.47]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by pigeon.gentoo.org (Postfix) with ESMTPS id 7449EE07C5 for ; Thu, 19 Jun 2014 08:40:17 +0000 (UTC) Received: by mail-pa0-f47.google.com with SMTP id kq14so1684358pab.6 for ; Thu, 19 Jun 2014 01:40:16 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=from:date:to:subject:message-id:mail-followup-to:references :mime-version:content-type:content-disposition:in-reply-to :user-agent; bh=Yb3H6HlIWG5VwvC3MdtZ+blfUYCOGnIhuCVGeEBWWsM=; b=fnXE6+q7cxvMx+Kq9qbW0/LPZMesyl/rpelJvFjKspoPGcrLdEMczo2PSwl9pSw/SJ mbOfzbCIJLWXhDYBS3H3OUOas0VpF4WZpW4l3B+Uk3BXV7ZR8cm8rNNktBU2m4btCaoO M/nHvfkjWjEbYnQ47Zr7dMA4vRBC7ioJf6MPOp54h3Pc1TdOGWBfRi7zZ9DQC0CAsZP8 fy0ZxHNddKp5uiSXi94c/fBeorrp43+JoYEjloeFt1NP+FdQF1I4P2Zwn4XqhYzh00R2 jdBeAOhH8/2/C9O8lXnCZpNX7i3HoVkXQq67zkPv7wd19VS87ABEhQPiKD7fYue08hDP WH3Q== X-Received: by 10.68.137.193 with SMTP id qk1mr3682746pbb.155.1403167216476; Thu, 19 Jun 2014 01:40:16 -0700 (PDT) Received: from localhost ([58.61.202.95]) by mx.google.com with ESMTPSA id ao4sm7327069pbc.51.2014.06.19.01.40.13 for (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Thu, 19 Jun 2014 01:40:15 -0700 (PDT) From: Amankwah X-Google-Original-From: Amankwah Date: Thu, 19 Jun 2014 16:40:08 +0800 To: gentoo-user@lists.gentoo.org Subject: Re: [gentoo-user] [Gentoo-User] emerge --sync likely to kill SSD? Message-ID: <20140619084008.GA97639@NAS> Mail-Followup-To: gentoo-user@lists.gentoo.org References: Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-Id: Gentoo Linux mail X-BeenThere: gentoo-user@lists.gentoo.org Reply-to: gentoo-user@lists.gentoo.org MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.23 (2014-03-12) X-Archives-Salt: f2e937e1-4760-48e3-9a0f-23c1c63dc020 X-Archives-Hash: 26ff4f6160ce8f5b3c85204999bd6c10 On Thu, Jun 19, 2014 at 10:36:59AM +0800, microcai wrote: > rsync is doing bunch of 4k ramdon IO when updateing portage tree, > that will kill SSDs with much higher Write Amplification Factror. > > > I have a 2year old SSDs that have reported Write Amplification Factor > of 26. I think the only reason is that I put portage tree on this SSD > to speed it up. > > what is the suggest way to reduce Write Amplification of a portage sync ? > Maybe the only solution is that move the portage tree to HDD??