Re: [PERFORM] tsearch2/GIST performance factors?

2005-10-17 Thread Oleg Bartunov
Craig, could you prepare excerption from your db (if possible), so I could play myself ? Oleg On Mon, 17 Oct 2005, Craig A. James wrote: Oleg wrote: Did you consider *decreasing* SIGLENINT ? Size of index will diminish and performance could be increased. I use in current project SIGLE

Re: [PERFORM] tsearch2/GIST performance factors?

2005-10-17 Thread Craig A. James
Oleg wrote: Did you consider *decreasing* SIGLENINT ? Size of index will diminish and performance could be increased. I use in current project SIGLENINT=15 The default value for SIGLENINT actually didn't work at all. It was only by increasing it that I got any performance at all. An examinat

Re: [PERFORM] Bytea poor performance

2005-10-17 Thread Mark Kirkwood
NSO wrote: Well, no. Delphi isn't better, same time just for downloading data... But as I told before, if for ex. pgAdminIII is running on server machine it is a lot faster, I do not know why, I was monitoring network connection between client and server and it is using only up to 2% of full spe

Re: [PERFORM] Sequential scan on FK join

2005-10-17 Thread Martin Nickel
When I turn of seqscan it does use the index - and it runs 20 to 30% longer. Based on that, the planner is correctly choosing a sequential scan - but that's just hard for me to comprehend. I'm joining on an int4 key, 2048 per index page - I guess that's a lot of reads - then the data -page reads.

Re: [PERFORM] tsearch2/GIST performance factors?

2005-10-17 Thread Oleg Bartunov
On Sat, 15 Oct 2005, Craig A. James wrote: We are indexing about 5 million small documents using tsearch2/GIST. Each "document" contains 2 to 50 words. This is a "write once, read many" situation. Write performance is unimportant, and the database contents are static. (We build it offline.

Re: [PERFORM] Sequential scan on FK join

2005-10-17 Thread Richard Huxton
Martin Nickel wrote: Subject: Re: Sequential scan on FK join From: Martin Nickel <[EMAIL PROTECTED]> Newsgroups: pgsql.performance Date: Wed, 12 Oct 2005 15:53:35 -0500 Richard, here's the EXPLAIN ANALYZE. I see your point re: the 2.7M expected vs the 2 actual, but I've r

[PERFORM] tsearch2/GIST performance factors?

2005-10-17 Thread Craig A. James
We are indexing about 5 million small documents using tsearch2/GIST. Each "document" contains 2 to 50 words. This is a "write once, read many" situation. Write performance is unimportant, and the database contents are static. (We build it offline.) We're having problems with inconsistent pe

Re: [PERFORM] Sequential scan on FK join

2005-10-17 Thread Martin Nickel
Subject: Re: Sequential scan on FK join From: Martin Nickel <[EMAIL PROTECTED]> Newsgroups: pgsql.performance Date: Wed, 12 Oct 2005 15:53:35 -0500 Richard, here's the EXPLAIN ANALYZE. I see your point re: the 2.7M expected vs the 2 actual, but I've run ANALYZE on the lead

[PERFORM] tsearch2/GIST performance factors?

2005-10-17 Thread Craig A. James
We are indexing about 5 million small documents using tsearch2/GIST. Each "document" contains 2 to 50 words. This is a "write once, read many" situation. Write performance is unimportant, and the database contents are static. (We build it offline.) We're having problems with inconsistent pe

Re: [PERFORM] Bytea poor performance

2005-10-17 Thread Andreas Pflug
NSO wrote: Well, no. Delphi isn't better, same time just for downloading data... But as I told before, if for ex. pgAdminIII is running on server machine it is a lot faster, I do not know why, I was monitoring network connection between client and server and it is using only up to 2% of full spe

Re: [PERFORM] Sequential scan on FK join

2005-10-17 Thread Richard Huxton
Martin Nickel wrote: EXPLAIN SELECT m.mailcode, l.lead_id FROM mailing m INNER JOIN lead l ON m.mailing_id = l.mailing_id WHERE (m.maildate >= '2005-7-01'::date AND m.maildate < '2005-8-01'::date) Hash Join (cost=62.13..2001702.55 rows=2711552 width=20) Hash Cond: ("outer".m