Re: [psycopg] speed concerns with executemany() - Mailing list psycopg

From Adrian Klaver
Subject Re: [psycopg] speed concerns with executemany()
Date
Msg-id ed4aa432-1805-965f-99ee-993dd68f27b9@aklaver.com
Whole thread Raw
In response to Re: [psycopg] speed concerns with executemany()  (Christophe Pettus <xof@thebuild.com>)
List psycopg
On 01/02/2017 08:27 AM, Karsten Hilbert wrote:
>> On 01/02/2017 08:07 AM, Daniele Varrazzo wrote:
>>> On Mon, Jan 2, 2017 at 4:35 PM, Adrian Klaver <adrian.klaver@aklaver.com> wrote:
>>>>
>>>> With NRECS=10000 and page size=100:
>>>>
>>>> aklaver@tito:~> python psycopg_executemany.py -p 100
>>>> classic: 427.618795156 sec
>>>> joined: 7.55754685402 sec
>>>
>>> Ugh! :D
>
> While 7 as such may be a lot, a decrease from 427 to 7 is
> simply brilliant.

Also the server I am running this against is a stock install running on
a VM that just backs an issue tracker. No optimizations. Also on the
client end we are experiencing a Winter storm that is making things sort
of flaky. So I would take this as a relative comparison not a absolute
truth.

>
> Karsten
>


--
Adrian Klaver
adrian.klaver@aklaver.com


psycopg by date:

Previous
From: Karsten Hilbert
Date:
Subject: Re: [psycopg] speed concerns with executemany()
Next
From: Adrian Klaver
Date:
Subject: Re: [psycopg] Solving the SQL composition problem