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

From Daniele Varrazzo
Subject Re: [psycopg] speed concerns with executemany()
Date
Msg-id CA+mi_8bipP557+7cJyw_wkqP1paeAJr-oewzEsqR0SkfnzgHiQ@mail.gmail.com
Whole thread Raw
In response to Re: [psycopg] speed concerns with executemany()  (Adrian Klaver <adrian.klaver@aklaver.com>)
Responses Re: [psycopg] speed concerns with executemany()  (Adrian Klaver <adrian.klaver@aklaver.com>)
Re: [psycopg] speed concerns with executemany()  (Adrian Klaver <adrian.klaver@aklaver.com>)
List psycopg
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.

-- Daniele


psycopg by date:

Previous
From: Daniele Varrazzo
Date:
Subject: Re: [psycopg] speed concerns with executemany()
Next
From: Jim Nasby
Date:
Subject: Re: [psycopg] Solving the SQL composition problem