From: | Joseph Shraibman <jks(at)selectacast(dot)net> |
---|---|
To: | mike(at)mwcs(dot)mb(dot)ca |
Cc: | pgsql-jdbc(at)postgresql(dot)org |
Subject: | Re: JDBC Performance |
Date: | 2001-08-10 00:00:43 |
Message-ID: | 3B73242B.7000500@selectacast.net |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-jdbc |
This is typical. Until you do a vacuum the old versions of a row are
still in the db, so an update has to do an index query on an index to
get to the row that needs indexing, which returns a lot of pointers to
old entries, that then have to be tranversed until the valid one in
found. Then the update makes one more invalid row.
mike(at)mwcs(dot)mb(dot)ca wrote:
> I am having some performance problems with postgresql and JDBC when it
> comes to updates. If I try and update a record it seems to be taking 1.7
> seconds for 100 records or 14 seconds for 500 records. An insert is only
> taking between 3-5 ms/record. Performance on the updates continue to
> decrease until I vacuum analyze the database again. Is this normal?
>
> Mike
>
>
>
>
--
Joseph Shraibman
jks(at)selectacast(dot)net
Increase signal to noise ratio. http://www.targabot.com
From | Date | Subject | |
---|---|---|---|
Next Message | Joseph Shraibman | 2001-08-10 01:26:53 | NullPointerException on next() |
Previous Message | Barry Lind | 2001-08-09 17:37:11 | Re: Re: JDBC 2.0 conformance, documentation and todo list |