Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtp (Exim 4.72) (envelope-from ) id 1UFnxQ-0001M8-BC for pgsql-performance@arkaria.postgresql.org; Wed, 13 Mar 2013 15:51:12 +0000 Received: from localhost ([127.0.0.1] helo=postgresql.org) by malur.postgresql.org with smtp (Exim 4.72) (envelope-from ) id 1UFnxP-0008C3-PJ for pgsql-performance@arkaria.postgresql.org; Wed, 13 Mar 2013 15:51:11 +0000 Received: from magus.postgresql.org ([2a02:c0:301:0:ffff::29]) by malur.postgresql.org with esmtp (Exim 4.72) (envelope-from ) id 1UFnxO-0008Bw-TU for pgsql-performance@postgresql.org; Wed, 13 Mar 2013 15:51:11 +0000 Received: from mail-ea0-x232.google.com ([2a00:1450:4013:c01::232]) by magus.postgresql.org with esmtp (Exim 4.72) (envelope-from ) id 1UFnxM-00026U-Ho for pgsql-performance@postgresql.org; Wed, 13 Mar 2013 15:51:10 +0000 Received: by mail-ea0-f178.google.com with SMTP id g14so518348eak.37 for ; Wed, 13 Mar 2013 08:51:06 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=x-received:references:mime-version:in-reply-to:content-type :content-transfer-encoding:message-id:cc:x-mailer:from:subject:date :to; bh=N8dpUIms/rMasoFdaQiygdZD/H4/ajZVyAurz06pX/s=; b=O0icB2PjoazbWn5Il712iNdIb29n+OBVYcDjPOfk9J56SA++0lyJVWBk/+mvkjSVZy LjMlOELn/ILQ/Ml4pG9PIl37ErS58Krkr7F1NowHyrxtKGKd6vjkCoBgDuzwMW/ca55H z+s5J5mMJ6Ilh26FO06Qy6l+mHrCrkctWWC6SEebo0TnTqxsQQu08lBxJPCx0xMOD6jt IODw/LVbYGRynXLMr+DKUJ5YL4rogFXE8ZJMr/11kZngOpbZj2DKTvI42HuGYxhB9916 GLArZm7nd3BZqV/Vb5UkLw4EmkoWsfpLpmClffyhdUOwJ3h62cMA/g9uPwZixiv7glh+ pMeA== X-Received: by 10.15.67.134 with SMTP id u6mr8638973eex.6.1363189866835; Wed, 13 Mar 2013 08:51:06 -0700 (PDT) Received: from [192.168.251.88] (outbound.latens.co.uk. [81.134.2.201]) by mx.google.com with ESMTPS id u44sm36760067eel.7.2013.03.13.08.51.05 (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Wed, 13 Mar 2013 08:51:05 -0700 (PDT) References: <4D6D1410-2208-4DAA-BD64-69BE1FD94E55@autouncle.com> <513CADB7.4030803@2ndQuadrant.com> <51409C51.1070601@kickstone.com> Mime-Version: 1.0 (1.0) In-Reply-To: <51409C51.1070601@kickstone.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: quoted-printable Message-Id: <38D48FB0-92A8-433B-8D34-4C63738B45BA@gmail.com> Cc: postgres performance list X-Mailer: iPad Mail (10B146) From: Greg Jaskiewicz Subject: Re: New server setup Date: Wed, 13 Mar 2013 15:50:51 +0000 To: John Lister X-Pg-Spam-Score: -2.0 (--) List-Archive: List-Help: List-ID: List-Owner: List-Post: List-Subscribe: List-Unsubscribe: X-Mailing-List: pgsql-performance Precedence: bulk Sender: pgsql-performance-owner@postgresql.org On 13 Mar 2013, at 15:33, John Lister wrote: > On 12/03/2013 21:41, Gregg Jaskiewicz wrote: >>=20 >> Whilst on the hardware subject, someone mentioned throwing ssd into the = mix. I.e. combining spinning HDs with SSD, apparently some raid cards can u= se small-ish (80GB+) SSDs as external caches. Any experiences with that ? >>=20 > The new LSI/Dell cards do this (eg H710 as mentioned in an earlier post).= It is easy to set up and supported it seems on all versions of dells cards= even if the docs say it isn't. Works well with the limited testing I did, = switched to pretty much all SSDs drives in my current setup >=20 > These cards also supposedly support enhanced performance with just SSDs (= CTIO) by playing with the cache settings, but to be honest I haven't notice= d any difference and I'm not entirely sure it is enabled as there is no ind= ication that CTIO is actually enabled and working. >=20 SSDs have much shorter life then spinning drives, so what do you do when on= e inevitably fails in your system ? --=20 Sent via pgsql-performance mailing list (pgsql-performance@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-performance