From: Joel Reymont <joelr1@gmail.com>
To: Kevin Grittner <Kevin.Grittner@wicourts.gov>
Cc: pgsql-performance@postgresql.org <pgsql-performance@postgresql.org>
Subject: Re: stored proc and inserting hundreds of thousands of rows
Date: Sat, 30 Apr 2011 18:58:50 +0100
Message-ID: <4881277622113933088@unknownmsgid> (raw)
In-Reply-To: <4DBC004C020000250003D099@gw.wicourts.gov>
References: <D5DE36B9-17CF-4A55-9119-CDC0BDC4E48D@gmail.com>
<4DBC004C020000250003D099@gw.wicourts.gov>
Calculating distance involves giving an array of 150 float8 to a pgsql
function, then calling a C function 2 million times (at the moment),
giving it two arrays of 150 float8.
Just calculating distance for 2 million rows and extracting the
distance takes less than a second. I think that includes sorting by
distance and sending 100 rows to the client.
Are you suggesting eliminating the physical linking and calculating
matching documents on the fly?
Is there a way to speed up my C function by giving it all the float
arrays, calling it once and having it return a set of matches? Would
this be faster than calling it from a select, once for each array?
Sent from my comfortable recliner
On 30/04/2011, at 18:28, Kevin Grittner <Kevin.Grittner@wicourts.gov> wrote:
> Joel Reymont <joelr1@gmail.com> wrote:
>
>> We have 2 million documents now and linking an ad to all of them
>> takes 5 minutes on my top-of-the-line SSD MacBook Pro.
>
> How long does it take to run just the SELECT part of the INSERT by
> itself?
>
> -Kevin
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: joelr1@gmail.com, Kevin.Grittner@wicourts.gov
Subject: Re: stored proc and inserting hundreds of thousands of rows
In-Reply-To: <4881277622113933088@unknownmsgid>
* 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