Return-Path: owner-postman
Received: from localhost.Berkeley.EDU (localhost.Berkeley.EDU [127.0.0.1]) by nobozo.CS.Berkeley.EDU (8.6.9/8.6.3) with SMTP id QAA01080 for postgres-redist; Thu, 12 Jan 1995 16:55:46 -0800
Resent-From: POSTGRES mailing list <postman@postgres.Berkeley.EDU>
Resent-Message-Id: <199501130055.QAA01080@nobozo.CS.Berkeley.EDU>
X-Authentication-Warning: nobozo.CS.Berkeley.EDU: Host localhost.Berkeley.EDU didn't use HELO protocol
Sender: owner-postman@postgres.Berkeley.EDU
X-Return-Path: owner-postman
Received: from mailgzrz.TU-Berlin.DE (mailgzrz.TU-Berlin.DE [130.149.4.10]) by nobozo.CS.Berkeley.EDU (8.6.9/8.6.3) with ESMTP id QAA01070 for <postgres@nobozo.CS.Berkeley.EDU>; Thu, 12 Jan 1995 16:55:43 -0800
Received: from marie.physik.tu-berlin.de by mailgzrz.TU-Berlin.DE 
          with SMTP (PP); Fri, 13 Jan 1995 01:40:59 +0100
Received: by marie.physik.tu-berlin.de (5.0/SMI-SVR4) id AA07751;
          Fri, 13 Jan 1995 01:40:54 --100
From: wpp@marie.physik.tu-berlin.de (Kai Petzke)
Message-Id: <9501130040.AA07751@marie.physik.tu-berlin.de>
Subject: Re: POSTGRES Append Performance
To: smith_w@mcnc.org (William T. Smith)
Date: Fri, 13 Jan 1995 01:42:19 +0100 (MET)
Cc: postgres@postgres.Berkeley.EDU
In-Reply-To: <199501121907.OAA07712@robin.mcnc.org.mcnc.org> from "William T. Smith" at Jan 12, 95 02:07:47 pm
X-Mailer: ELM [version 2.4 PL23]
Content-Type: text
Content-Length: 931
Resent-To: postgres-redist@postgres.Berkeley.EDU
Resent-Date: Thu, 12 Jan 95 16:55:46 -0800
Resent-XMts: smtp

> 
> Hello,
> 
> 	I am evaluating version 4.2 of POSTGRES as a database tool to
> provide persistent storage of directed graphs.  The test program adds
> one node which requires 17 append operations against an empty database.
> Each instance has less than 100 bytes.  The program takes 10 seconds
> elapsed time to execute.  Adding ten nodes takes 20 seconds.  Is this
> "normal" performance for POSTGRES?  Does anyone have any suggestions to
> improve performance? Is anyone using POSTGRES to support interactive
> applications.

Postgres has the overhead of all RDBMS systems: it has to parse the
queries, then optimize then, then do the actual work.  While doing
the first steps, tons of tuples are accessed from the pg_* files
of your database.

If you want better update performance for multiple tuples, use the 
"copy in" function.  Here, the parsing is done only once for the
complete set, not once for every datum.




Kai


==============================================================================
   To add/remove yourself to/from the POSTGRES mailing list: send mail with 
   the subject line ADD or DEL to "postgres-request@postgres.Berkeley.EDU".
   If this fails, send mail to "post_questions@postgres.Berkeley.EDU" and
   a human will deal with it.  DO NOT post to the "postgres" mailing list.
==============================================================================
              URL: http://s2k-ftp.CS.Berkeley.EDU:8000/postgres/
