Re: [psycopg] speed concerns with executemany()
От | Adrian Klaver |
---|---|
Тема | Re: [psycopg] speed concerns with executemany() |
Дата | |
Msg-id | bb29821c-0063-b584-91f1-ea6f0218ef6f@aklaver.com обсуждение исходный текст |
Ответ на | Re: [psycopg] speed concerns with executemany() (Daniele Varrazzo <daniele.varrazzo@gmail.com>) |
Ответы |
Re: [psycopg] speed concerns with executemany()
Re: [psycopg] speed concerns with executemany() Re: [psycopg] speed concerns with executemany() |
Список | 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. With NRECS=10000 and page size=100: aklaver@tito:~> python psycopg_executemany.py -p 100 classic: 427.618795156 sec joined: 7.55754685402 sec > > -- Daniele > -- Adrian Klaver adrian.klaver@aklaver.com
В списке psycopg по дате отправления: