X-Original-To: pgsql-novice-postgresql.org@localhost.postgresql.org Received: from localhost (unknown [64.117.224.130]) by svr1.postgresql.org (Postfix) with ESMTP id 5C730D1B4E1; Thu, 2 Oct 2003 09:29:37 +0000 (GMT) Received: from svr1.postgresql.org ([64.117.224.193]) by localhost (neptune.hub.org [64.117.224.130]) (amavisd-new, port 10024) with ESMTP id 48682-07; Thu, 2 Oct 2003 06:28:49 -0300 (ADT) Received: from lakemtao01.cox.net (lakemtao01.cox.net [68.1.17.244]) by svr1.postgresql.org (Postfix) with ESMTP id 6A4EFD1B4F0; Thu, 2 Oct 2003 06:28:46 -0300 (ADT) Received: from lhosts ([68.11.66.83]) by lakemtao01.cox.net (InterMail vM.5.01.06.05 201-253-122-130-105-20030824) with ESMTP id <20031002092843.VSTZ23248.lakemtao01.cox.net@lhosts>; Thu, 2 Oct 2003 05:28:43 -0400 Subject: basket, eggs & NAS (was eggs Re: Ideal Hardware?) From: Ron Johnson To: PgSQL Performance ML , PgSQL Novice ML In-Reply-To: References: Content-Type: text/plain Message-Id: <1065086923.27013.15.camel@haggis> Mime-Version: 1.0 X-Mailer: Ximian Evolution 1.4.4 Date: Thu, 02 Oct 2003 04:28:43 -0500 Content-Transfer-Encoding: 7bit X-Virus-Scanned: by amavisd-new at postgresql.org X-Archive-Number: 200310/24 X-Sequence-Number: 8461 On Wed, 2003-10-01 at 10:13, Jason Hihn wrote: > We have an opportunity to purchase a new, top-notch database server. I am > wondering what kind of hardware is recommended? We're on Linux platforms and > kernels though. I remember a comment from Tom about how he was spending a > lot of time debugging problems which turned out to be hardware-related. I of > course would like to avoid that. > > In terms of numbers, we expect have an average of 100 active connections > (most of which are idle 9/10ths of the time), with about 85% reading > traffic. I expect the database with flow average 10-20kBps under moderate > load. I hope to have one server host about 1000-2000 active databases, with > the largest being about 60 meg (no blobs). Inactive databases will only be > for reading (archival) purposes, and will seldom be accessed. Whoever mentioned using multiple servers instead of one uber-server is very right. You're putting all your eggs in one basket that way, and unless that "basket" has hot-swap CPUs, memory boards, etc, etc, then if you have a hardware problem, your whole business goes down. Buy 3 or 4 smaller systems, and distribute any possible pain from down time. It seems like I'm going to contravene what I just said about eggs in a basket when I suggest that the disks could possibly be concen- trated into a NAS, so that you could get 1 big, honkin fast *hot- swappable* (dual-redundant U320 storage controllers w/ 512MB battery- backed cache each, for a total of 1GB cache are easily available) disk subsystem for however many smaller CPU-boxes you get. (They could be kept un-shared by making separate partitions, and each machine only mounts one partition.) -- ----------------------------------------------------------------- Ron Johnson, Jr. ron.l.johnson@cox.net Jefferson, LA USA "Adventure is a sign of incompetence" Stephanson, great polar explorer