Re: [HACKERS] Profile of current backend

From: "Thomas G(dot) Lockhart" <lockhart(at)alumni(dot)caltech(dot)edu>
To: Michael Meskes <meskes(at)topsystem(dot)de>
Cc: Bruce Momjian <maillist(at)candle(dot)pha(dot)pa(dot)us>, PostgreSQL Hacker <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: [HACKERS] Profile of current backend
Date: 1998-02-06 15:09:53
Message-ID: 34DB27C1.F220369A@alumni.caltech.edu
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

> Not exactly. But to get my application running we have to do something to
> speed it up. This morning I started my program on a database with 15165
> records in one table and something like 100 in a second plus 2 in a third.
> Then my software tries to add records to the first table and for each record
> added it updates a record in the other two. This doesn't count the select
> etc.
>
> Anyway, the data isn't processed fast enough. I tried adding about 600
> records which should be done (the time in which the data was send) in 5
> minutes, but our system needed almost 8 minutes to insert the data. And this
> doesn't cause Oracle too much trouble.
>
> So I guess there's need for some speed-up. :-)

I (and others) had done some benchmarking on simple inserts (6 months ago?) and
had concluded that the speed was similar to other commercial systems (I was
comparing against Ingres). I recall getting ~50TPS.

This was all before Bruce did his work on startup and runtime speeds. You
really think your performance is that far off? You are doing selects on the big
table before inserting? Do you have indices set up?? Our results were for
inserts on a heap table, which has the least overhead...

- Tom

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message The Hermit Hacker 1998-02-06 15:20:38 Re: [HACKERS] Profile of current backend
Previous Message Hannu Krosing 1998-02-06 15:09:15 06.02.98 snapshot core dump