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

From Adrian Klaver
Subject Re: [psycopg] speed concerns with executemany()
Date
Msg-id 3f0fb434-4bdb-f778-ddb4-14636454697a@aklaver.com
Whole thread Raw
In response to Re: [psycopg] speed concerns with executemany()  (Daniele Varrazzo <daniele.varrazzo@gmail.com>)
List psycopg
On 01/02/2017 05:05 AM, Daniele Varrazzo wrote:
> On Sun, Jan 1, 2017 at 9:33 PM, Adrian Klaver <adrian.klaver@aklaver.com> wrote:
>
>> Same code across network, client in Bellingham WA, server in Fremont CA:
>>
>> Without autocommit:
>>
>> In [51]: %timeit -n 10 cur.executemany(sql, l)
>> 10 loops, best of 3: 8.22 s per loop
>>
>>
>> With autocommit:
>>
>> In [56]: %timeit -n 10 cur.executemany(sql, l)
>> 10 loops, best of 3: 8.38 s per loop
>
> Adrian, have you got a benchmark "classic vs. joined" on remote
> network? Thank you.

Knew I was forgetting something, thanks for the reminder. Will set that
up and report back.

>
> -- Daniele
>


--
Adrian Klaver
adrian.klaver@aklaver.com


psycopg by date:

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