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 E0DC2533E6 for ; Wed, 6 Apr 2005 19:18:35 +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 48321-03 for ; Wed, 6 Apr 2005 18:18:25 +0000 (GMT) Received: from wproxy.gmail.com (wproxy.gmail.com [64.233.184.205]) by svr1.postgresql.org (Postfix) with ESMTP id A72CA53364 for ; Wed, 6 Apr 2005 19:18:22 +0100 (BST) Received: by wproxy.gmail.com with SMTP id 68so335225wri for ; Wed, 06 Apr 2005 11:18:23 -0700 (PDT) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:reply-to:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:references; b=PhKLjkKXC6KArg0W+MzvEXEKarXw8td8U5lzND09Gd3JDPjvzybvXMDp9ngtZ+MMYmTEdvXdboz6tZAGMW27Vc1rAuTQm1DVntQfd52tzlcIuIXY8HFLfzDbCT7z/uiVii1nPK4CUF2hxhbUXli09/MajdREEL2kdXvY/B7pnFM= Received: by 10.54.32.67 with SMTP id f67mr233939wrf; Wed, 06 Apr 2005 11:18:21 -0700 (PDT) Received: by 10.54.86.16 with HTTP; Wed, 6 Apr 2005 11:18:21 -0700 (PDT) Message-ID: <33c6269f050406111849766b3@mail.gmail.com> Date: Wed, 6 Apr 2005 14:18:21 -0400 From: Alex Turner Reply-To: Alex Turner To: "Mohan, Ross" Subject: Re: RE : RE: Postgresql vs SQLserver for thisapplication ? Cc: pgsql-performance@postgresql.org In-Reply-To: Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit References: X-Virus-Scanned: by amavisd-new at hub.org X-Spam-Status: No, hits=0.253 tagged_above=0 required=5 tests=AWL, DNS_FROM_RFC_ABUSE, RCVD_BY_IP X-Spam-Level: X-Archive-Number: 200504/114 X-Sequence-Number: 11511 I guess I was thinking more in the range of 5000 transaction/sec, less so 5000 rows on bulk import... Alex On Apr 6, 2005 12:47 PM, Mohan, Ross wrote: > > > 31Million tuples were loaded in approx 279 seconds, or approx 112k rows per second. > > > I'd love to see PG get into this range..i am a big fan of PG (just a > > rank newbie) but I gotta think the underlying code to do this has to > > be not-too-complex..... > > I'd say we're there. > > || Yes! PG is there, assuredly! So VERY cool! I made a newbie > error of conflating COPY with INSERT. I don't know if I could get > oracle to do much more than about 500-1500 rows/sec...PG is quite impressive. > > Makes one wonder why corporations positively insist on giving oracle > $$$$ yearly. > > -----Original Message----- > From: Rod Taylor [mailto:pg@rbt.ca] > Sent: Wednesday, April 06, 2005 12:41 PM > To: Mohan, Ross > Cc: pgsql-performance@postgresql.org > Subject: Re: RE : RE: [PERFORM] Postgresql vs SQLserver for thisapplication ? > > On Wed, 2005-04-06 at 16:12 +0000, Mohan, Ross wrote: > > I wish I had a Dell system and run case to show you Alex, but I > > don't... however...using Oracle's "direct path" feature, it's pretty > > straightforward. > > > > We've done 110,000 rows per second into index-less tables on a big > > system (IBM Power5 chips, Hitachi SAN). ( Yes, I am sure: over 100K a > > second. Sustained for almost 9 minutes. ) > > Just for kicks I did a local test on a desktop machine (single CPU, single IDE drive) using COPY from STDIN for a set of integers in via a single transaction, no indexes. > > 1572864 tuples were loaded in 13715.613ms, which is approx 115k rows per second. > > Okay, no checkpoints and I didn't cross an index boundary, but I also haven't tuned the config file beyond bumping up the buffers. > > Lets try again with more data this time. > > 31Million tuples were loaded in approx 279 seconds, or approx 112k rows per second. > > > I'd love to see PG get into this range..i am a big fan of PG (just a > > rank newbie) but I gotta think the underlying code to do this has to > > be not-too-complex..... > > I'd say we're there. > > > -----Original Message----- > > From: Alex Turner [mailto:armtuk@gmail.com] > > Sent: Wednesday, April 06, 2005 11:38 AM > > To: bsimon@loxane.com > > Cc: pgsql-performance@postgresql.org; Mohan, Ross > > Subject: Re: RE : RE: [PERFORM] Postgresql vs SQLserver for this application ? > > > > > > I think everyone was scared off by the 5000 inserts per second number. > > > > I've never seen even Oracle do this on a top end Dell system with > > copious SCSI attached storage. > > > > Alex Turner > > netEconomist > > > > On Apr 6, 2005 3:17 AM, bsimon@loxane.com wrote: > > > > > > Unfortunately. > > > > > > But we are in the the process to choose Postgresql with pgcluster. > > > I'm > > > currently running some tests (performance, stability...) Save the > > > money on the license fees, you get it for your hardware ;-) > > > > > > I still welcome any advices or comments and I'll let you know how > > > the > > > project is going on. > > > > > > Benjamin. > > > > > > > > > > > > "Mohan, Ross" > > > > > > 05/04/2005 20:48 > > > > > > Pour : > > > cc : > > > Objet : RE: [PERFORM] Postgresql vs SQLserver for this > > > application ? > > > > > > > > > You never got answers on this? Apologies, I don't have one, but'd be > > > curious to hear about any you did get.... > > > > > > thx > > > > > > Ross > > > > > > -----Original Message----- > > > From: pgsql-performance-owner@postgresql.org > > > [mailto:pgsql-performance-owner@postgresql.org] On Behalf Of > > > bsimon@loxane.com > > > Sent: Monday, April 04, 2005 4:02 AM > > > To: pgsql-performance@postgresql.org > > > Subject: [PERFORM] Postgresql vs SQLserver for this application ? > > > > > > > > > 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. > > > > > > > > > > > > > ---------------------------(end of > > broadcast)--------------------------- > > TIP 2: you can get off all lists at once with the unregister command > > (send "unregister YourEmailAddressHere" to majordomo@postgresql.org) > > > -- > > ---------------------------(end of broadcast)--------------------------- > TIP 7: don't forget to increase your free space map settings >