X-Original-To: pgsql-performance-postgresql.org@localhost.postgresql.org Received: from localhost (neptune.hub.org [200.46.204.2]) by svr1.postgresql.org (Postfix) with ESMTP id 1674DD1B50A for ; Mon, 24 Nov 2003 17:21:42 +0000 (GMT) Received: from svr1.postgresql.org ([200.46.204.71]) by localhost (neptune.hub.org [200.46.204.2]) (amavisd-new, port 10024) with ESMTP id 74973-10 for ; Mon, 24 Nov 2003 13:21:10 -0400 (AST) Received: from news.hub.org (news.hub.org [200.46.204.72]) by svr1.postgresql.org (Postfix) with ESMTP id 678ECD1C914 for ; Mon, 24 Nov 2003 13:21:10 -0400 (AST) Received: from news.hub.org (news.hub.org [200.46.204.72]) by news.hub.org (8.12.9/8.12.9) with ESMTP id hAOHLANu001635 for ; Mon, 24 Nov 2003 17:21:10 GMT (envelope-from news@news.hub.org) Received: (from news@localhost) by news.hub.org (8.12.9/8.12.9/Submit) id hAOHJLOD001134 for pgsql-performance@postgresql.org; Mon, 24 Nov 2003 17:19:21 GMT From: William Yu X-Newsgroups: comp.databases.postgresql.performance Subject: Re: Maximum Possible Insert Performance? Date: Mon, 24 Nov 2003 09:19:20 -0800 Organization: Hub.Org Networking Services Lines: 16 Message-ID: References: <3FC19C2C.4050704@myrealbox.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-Complaints-To: usenet@news.hub.org User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.5) Gecko/20031007 X-Accept-Language: en-us, en In-Reply-To: <3FC19C2C.4050704@myrealbox.com> To: pgsql-performance@postgresql.org X-Virus-Scanned: by amavisd-new at postgresql.org X-Archive-Number: 200311/209 X-Sequence-Number: 4769 This is an intriguing thought which leads me to think about a similar solution for even a production server and that's a solid state drive for just the WAL. What's the max disk space the WAL would ever take up? There's quite a few 512MB/1GB/2GB solid state drives available now in the ~$200-$500 range and if you never hit those limits... When my current job batch is done, I'll save a copy of the dir and give the WAL on ramdrive a test. And perhaps even buy a Sandisk at the local store and run that through the hooper. Shridhar Daithankar wrote: > > Mount WAL on RAM disk. WAL is most often hit area for heavy > updates/inserts. If you spped that up, things should be pretty faster.