X-Original-To: pgsql-admin-postgresql.org@localhost.postgresql.org Received: from localhost (mx1.hub.org [200.46.208.251]) by postgresql.org (Postfix) with ESMTP id 534BF11F68E4 for ; Thu, 27 Apr 2006 02:06:19 -0300 (ADT) Received: from postgresql.org ([200.46.204.71]) by localhost (mx1.hub.org [200.46.208.251]) (amavisd-new, port 10024) with ESMTP id 14325-02 for ; Thu, 27 Apr 2006 02:06:07 -0300 (ADT) X-Greylist: from auto-whitelisted by SQLgrey- Received: from noel.decibel.org (noel.decibel.org [67.100.216.10]) by postgresql.org (Postfix) with ESMTP id EC51911F60AE for ; Thu, 27 Apr 2006 02:06:06 -0300 (ADT) Received: by noel.decibel.org (Postfix, from userid 1001) id 4C17956408; Thu, 27 Apr 2006 00:06:06 -0500 (CDT) Received: (hashcash-sendmail, from uid 1001); Thu, 27 Apr 2006 00:06:05 -0500 Date: Thu, 27 Apr 2006 00:06:05 -0500 From: "Jim C. Nasby" To: Benjamin Krajmalnik Cc: pgsql-admin@postgresql.org Subject: Re: New system recommendations Message-ID: <20060427050605.GW97354@pervasive.com> References: <8511B4970E0D124898E973DF496F9B432515CF@stash.stackdump.local> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <8511B4970E0D124898E973DF496F9B432515CF@stash.stackdump.local> X-Operating-System: FreeBSD 6.0-RELEASE-p4 amd64 X-Distributed: Join the Effort! http://www.distributed.net User-Agent: Mutt/1.5.11 X-Hashcash: 1:20:060427:kraj@illumen.com::BQrfVB8oRjhUPuwe:06XAR X-Hashcash: 1:20:060427:pgsql-admin@postgresql.org::RazUdt/cN8DOjpk3:00000000000 0000000000000000000000001D9K X-Virus-Scanned: Maia Mailguard 1.0.1 X-Archive-Number: 200604/296 X-Sequence-Number: 21465 On Wed, Apr 26, 2006 at 07:30:49PM -0600, Benjamin Krajmalnik wrote: > I am about to take a system from testing into production. > > The system is a combination oltp/bi (network monitoring platform). > > We are currently inserting about 1 million rows per day, and will > increase to probably 5 million once it goes into full deployment. > > The current test production server is running Windows Server 2003, > PostgreSQL 8.1.3. > > Record insertion is done via an ODBC call to a stored procedure from a > Windows based host monitor. Make sure you're batching inserts with transactions. > It is currently running on a 3GHz Xeon HT, 2GB RAM, dual 72GB disks > running RAID 1. This server is a 1U without only 2 drive bays, so I > have a potential issue with drive space. > > As a result, I will be moving the db server to a Dell 1650 with 3 146GB > SCSI drives running RAID 0. System is a dual processor, 1.2GHz, with > 4GB RAM. 3 drive raid0 is likely to fail within 3-4 years, just so you know; unless it's not new hardware, in which case I'd expect something closer to 2 years (my general experience is that server HDs will last 4-6 years, so with 3 of them you're looking at a failure every ~2 years). You sure you want to trust a monitoring app to raid0? :) > Due to the amount of record insertions being performed, record insertion > speed is paramount - also because excessive execution time will have a > side effect of causing the monitoring agent to go stale. Some of the > users have mentioned that I will get better performance running under a > *nix OS. We are mostly a Microsoft OS house, but also run FreeBSD. I > am considering deploying with FreeBSD 6.0. I was wondering if anyone > has benchmarks showing speed of execution of PostgreSQL 8.1.3 under > Win2003 and FreeBSD 6.0. Also, are there any caveats or items I should > be aware of if running under FreeBSD? Any issues when running under a > multi-processor kernel? Anything in specific which I should include in > the kernel build to give me optimum performance for running PostgreSQL? > > Needless to say, I am a bit nervous of moving to FreeBSD since I have > not tested it in a production environment. Aside from some very large shops running FreeBSD (yahoo does I believe, and hotmail did for a long time, even after MS bought it), it's also a preferred OS by PostgreSQL developers. On the other hand we've only had Windows support for about 2 years and there's known windows-only issues. -- Jim C. Nasby, Sr. Engineering Consultant jnasby@pervasive.com Pervasive Software http://pervasive.com work: 512-231-6117 vcard: http://jim.nasby.net/pervasive.vcf cell: 512-569-9461