pg.ddx.io  pgsql-performance@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Seth Robertson <pgsql-performance@sysd.com>
To: pgsql-performance@postgresql.org
Subject: Re: Postgres 7.3.1 poor insert/update/search performance
Date: Wed, 22 Jan 2003 12:45:24 -0500
Message-ID: <200301221745.h0MHjOs14488@winwood.sysdetect.com> (raw)
References: <200301212120.h0LLKn820463>
	<20030121134242.Q84028-100000@megazone23.bigpanda.com>
	<200301212207.h0LM7Dt21080@winwood.sysdetect.com>
	<13165.1043188295@sss.pgh.pa.us>


Seth Robertson writes:

    
    However, it looks like my hope to use arrays is
    doomed though, I'm not sure I can handle the performance penalty.

Just in case I get the person who implemented arrays annoyed or
worried, I did not properly modify the "array" test and was vacuum'ing
the wrong table every 10000 vectors during the test.  I realized that
this morning and the new array results are listed below.  I also
experimented with batching read operations, and I was surprised to find
that this helps a great deal as well.

----------------------------------------------------------------------
"normal" C libpq                        256 t/s
"normal" Perl DBI                       251 t/s
"DBI Prepared Statement" Perl DBI       254 t/s
"Batching" Perl DBI                     1149 t/s
"arrays" Perl DBI                       250 t/s  (*)
"arrays with batching" Perl DBI         1020 t/s (*)
"server-side function" Perl DBI         84 t/s
"server-side trigger" Perl DBI          84 t/s
"normal" Perl DBI read                  1960 t/s
"batched" Perl DBI read			3076 t/s (*)
"array" Perl DBI read                   1754 t/s (*)
"batched array" Perl DBI read           2702 t/s (*)
"normal" Perl DBI for Oracle            314 t/s
"normal" Perl DBI read for Oracle       395 t/s
----------------------------------------------------------------------
(*) New/updated from this morning

This brings array code to within 11% of the performance of batched
non-arrays, and close enough to be an option.  I may well be doing
something wrong with the server-side functions, but I don't see
anything quite so obviously wrong.

                                        -Seth Robertson



view thread (16+ messages)  latest in thread

Message-ID: <200301221745.h0MHjOs14488@winwood.sysdetect.com>
Permalink:  ../200301221745.h0MHjOs14488@winwood.sysdetect.com/
Also on:    postgresql.org/message-id/200301221745.h0MHjOs14488@winwood.sysdetect.com

 · 

reply

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients from your mail client; the link fills in
  the headers below: reply via email
  Some clients, webmail especially, drop In-Reply-To and References from
  a link, and the reply then starts a new thread: use the mbox below.

  To: pgsql-performance@postgresql.org
  Cc: pgsql-performance@sysd.com
  Subject: Re: Postgres 7.3.1 poor insert/update/search performance
  In-Reply-To: <200301221745.h0MHjOs14488@winwood.sysdetect.com>
  References: <200301212120.h0LLKn820463> <20030121134242.Q84028-100000@megazone23.bigpanda.com> <200301212207.h0LM7Dt21080@winwood.sysdetect.com> <13165.1043188295@sss.pgh.pa.us> <200301221745.h0MHjOs14488@winwood.sysdetect.com>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox