X-Original-To: pgsql-performance-postgresql.org@localhost.postgresql.org Received: from localhost (unknown [200.46.204.144]) by svr1.postgresql.org (Postfix) with ESMTP id 9AA95534B0 for ; Sat, 9 Apr 2005 14:19:15 +0100 (BST) Received: from svr1.postgresql.org ([200.46.204.71]) by localhost (av.hub.org [200.46.204.144]) (amavisd-new, port 10024) with ESMTP id 70704-09 for ; Sat, 9 Apr 2005 13:19:11 +0000 (GMT) Received: from floppy.pyrenet.fr (news.pyrenet.fr [194.116.145.2]) by svr1.postgresql.org (Postfix) with ESMTP id CC0C953431 for ; Sat, 9 Apr 2005 14:19:10 +0100 (BST) Received: by floppy.pyrenet.fr (Postfix, from userid 106) id 5F2F230952; Sat, 9 Apr 2005 15:18:43 +0200 (MET DST) Date: Sat, 09 Apr 2005 08:19:12 -0500 From: BarryS User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7.3) Gecko/20041202 Debian/1.7.3.x.1-39 X-Accept-Language: en MIME-Version: 1.0 X-Newsgroups: pgsql.performance Subject: Re: Postgresql vs SQLserver for this application ? References: In-Reply-To: Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Message-ID: <5-2dnWnNnuvSS8rfRVn-tA@giganews.com> Lines: 53 X-Complaints-To: abuse@giganews.com X-DMCA-Notifications: http://www.giganews.com/info/dmca.html X-Abuse-and-DMCA-Info: Please be sure to forward a copy of ALL headers X-Abuse-and-DMCA-Info: Otherwise we will be unable to process your complaint properly X-Postfilter: 1.3.32 To: pgsql-performance@postgresql.org X-Virus-Scanned: by amavisd-new at hub.org X-Spam-Status: No, hits=0 tagged_above=0 required=5 tests= X-Spam-Level: X-Archive-Number: 200504/200 X-Sequence-Number: 11597 Well, quite honestly, if you need this performance (5000 ins / sec) and features (clustering, replication) - you should be looking at DB2 or Oracle. That is not to say that PG can not do the job, or that its not a great database, but the reason that DB2 and Oracle are still in wide use is because they answer the exact question you asked. -Barry bsimon@loxane.com wrote: > > hi all. > > We are designing a quite big application that requires a > high-performance database backend. > The rates we need to obtain are at least 5000 inserts per second and 15 > selects per second for one connection. There should only be 3 or 4 > simultaneous connections. > I think our main concern is to deal with the constant flow of data > coming from the inserts that must be available for selection as fast as > possible. (kind of real time access ...) > > As a consequence, the database should rapidly increase up to more than > one hundred gigs. We still have to determine how and when we shoud > backup old data to prevent the application from a performance drop. We > intend to develop some kind of real-time partionning on our main table > keep the flows up. > > At first, we were planning to use SQL Server as it has features that in > my opinion could help us a lot : > - replication > - clustering > > Recently we started to study Postgresql as a solution for our project : > - it also has replication > - Postgis module can handle geographic datatypes (which would > facilitate our developments) > - We do have a strong knowledge on Postgresql administration (we > use it for production processes) > - it is free (!) and we could save money for hardware purchase. > > Is SQL server clustering a real asset ? How reliable are Postgresql > replication tools ? Should I trust Postgresql performance for this kind > of needs ? > > My question is a bit fuzzy but any advices are most welcome... > hardware,tuning or design tips as well :)) > > Thanks a lot. > > Benjamin. >