Re: speed concerns with executemany()

From: Adrian Klaver <adrian(dot)klaver(at)aklaver(dot)com>
To: Daniele Varrazzo <daniele(dot)varrazzo(at)gmail(dot)com>
Cc: mike bayer <mike_mp(at)zzzcomputing(dot)com>, Christophe Pettus <xof(at)thebuild(dot)com>, "psycopg(at)postgresql(dot)org" <psycopg(at)postgresql(dot)org>
Subject: Re: speed concerns with executemany()
Date: 2017-01-02 16:15:54
Message-ID: aedadc82-c4c4-d65f-4f27-813a23b02d39@aklaver.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: psycopg

On 01/02/2017 08:07 AM, Daniele Varrazzo wrote:
> On Mon, Jan 2, 2017 at 4:35 PM, Adrian Klaver <adrian(dot)klaver(at)aklaver(dot)com> wrote:
>>
>> With NRECS=10000 and page size=100:
>>
>> aklaver(at)tito:~> python psycopg_executemany.py -p 100
>> classic: 427.618795156 sec
>> joined: 7.55754685402 sec
>
> Ugh! :D

Well it does show the benefit of the joined approach.

>
> -- Daniele
>

--
Adrian Klaver
adrian(dot)klaver(at)aklaver(dot)com

In response to

Responses

Browse psycopg by date

  From Date Subject
Next Message Karsten Hilbert 2017-01-02 16:16:12 Re: speed concerns with executemany()
Previous Message Daniele Varrazzo 2017-01-02 16:10:10 Re: speed concerns with executemany()