pg.ddx.io  pgsql-performance@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Alan Stange <stange@rentec.com>
To: PC Drew <drewpc@ibsncentral.com>
Cc: Leeuw van der, Tim <tim.leeuwvander@nl.unisys.com>
Cc: pgsql-performance@postgresql.org
Subject: Re: Insert Times
Date: Tue, 27 Jan 2004 10:58:29 -0500
Message-ID: <40168AA5.6040702@rentec.com> (raw)
In-Reply-To: <82CEDAA6A559DB48A373FC3090F2560F356689@mail.ibsncentral.com>
References: <82CEDAA6A559DB48A373FC3090F2560F356689@mail.ibsncentral.com>

PC Drew wrote:

>I tested this out and saw no improvement:
>  
>
I'd still suspect some class loading issues and HotSpot compilation 
issues are polluting your numbers.    Try using a PreparedStatement to 
another table first in order to make sure that classes bytecode has been 
loaded.   There are some command line options to the JVM to have it 
print out some status info when it is loading classes and compiling 
methods; you might want to turn on those options as well.

-- Alan

>EXPLAIN ANALYZE SELECT * FROM one;
>Seq Scan on one  (cost=0.00..20.00 rows=1000 width=404) (actual time=0.04..0.50 rows=51 loops=1)
>Total runtime: 0.75 msec
>EXPLAIN ANALYZE SELECT * FROM one;
>Seq Scan on one  (cost=0.00..20.00 rows=1000 width=404) (actual time=0.06..0.50 rows=51 loops=1)
>Total runtime: 0.64 msec
>EXPLAIN ANALYZE SELECT * FROM one;
>Seq Scan on one  (cost=0.00..20.00 rows=1000 width=404) (actual time=0.04..0.40 rows=51 loops=1)
>Total runtime: 0.54 msec
>EXPLAIN ANALYZE SELECT * FROM one;
>Seq Scan on one  (cost=0.00..20.00 rows=1000 width=404) (actual time=0.04..0.41 rows=51 loops=1)
>Total runtime: 0.54 msec
>EXPLAIN ANALYZE SELECT * FROM one;
>Seq Scan on one  (cost=0.00..20.00 rows=1000 width=404) (actual time=0.04..0.41 rows=51 loops=1)
>Total runtime: 0.53 msec
>EXPLAIN ANALYZE INSERT INTO one (id, msg) VALUES (1, 'blah');
>Result  (cost=0.00..0.01 rows=1 width=0) (actual time=0.01..0.02 rows=1 loops=1)
>Total runtime: 0.85 msec
>EXPLAIN ANALYZE INSERT INTO one (id, msg) VALUES (1, 'blah');
>Result  (cost=0.00..0.01 rows=1 width=0) (actual time=0.02..0.02 rows=1 loops=1)
>Total runtime: 0.15 msec
>EXPLAIN ANALYZE INSERT INTO one (id, msg) VALUES (1, 'blah');
>Result  (cost=0.00..0.01 rows=1 width=0) (actual time=0.02..0.02 rows=1 loops=1)
>Total runtime: 0.14 msec
>EXPLAIN ANALYZE INSERT INTO one (id, msg) VALUES (1, 'blah');
>Result  (cost=0.00..0.01 rows=1 width=0) (actual time=0.02..0.02 rows=1 loops=1)
>Total runtime: 0.12 msec
>EXPLAIN ANALYZE INSERT INTO one (id, msg) VALUES (1, 'blah');
>Result  (cost=0.00..0.01 rows=1 width=0) (actual time=0.01..0.02 rows=1 loops=1)
>Total runtime: 0.12 msec
>
>
>
>-----Original Message-----
>From:	Leeuw van der, Tim [mailto:tim.leeuwvander@nl.unisys.com]
>Sent:	Tue 1/27/2004 12:38 AM
>To:	PC Drew; pgsql-performance@postgresql.org
>Cc:	
>Subject:	RE: [PERFORM] Insert Times
>
>Hi,
>
>My personal feeling on this is, that the long time taken for the first query
>is for loading all sorts of libraries, JVM startup overhead etc.
>
>What if you first do some SELECT (whatever), on a different table, to warm
>up the JVM and the database?
>
>regards,
>
>--Tim
>
>THIS COMMUNICATION MAY CONTAIN CONFIDENTIAL AND/OR OTHERWISE PROPRIETARY
>MATERIAL and is thus for use only by the intended recipient. If you received
>this in error, please contact the sender and delete the e-mail and its
>attachments from all computers. 
>
>
>
>
>---------------------------(end of broadcast)---------------------------
>TIP 8: explain analyze is your friend
>  
>




view thread (5+ messages)

Message-ID: <40168AA5.6040702@rentec.com>
Permalink:  ../40168AA5.6040702@rentec.com/
Also on:    postgresql.org/message-id/40168AA5.6040702@rentec.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 using the --to and --cc options:
  reply via email

  To: pgsql-performance@postgresql.org
  Cc: stange@rentec.com, drewpc@ibsncentral.com, tim.leeuwvander@nl.unisys.com
  Subject: Re: Insert Times
  In-Reply-To: <40168AA5.6040702@rentec.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