From: | Adrian Klaver <adrian(dot)klaver(at)aklaver(dot)com> |
---|---|
To: | psycopg(at)postgresql(dot)org |
Subject: | Re: speed concerns with executemany() |
Date: | 2017-01-02 16:35:08 |
Message-ID: | ed4aa432-1805-965f-99ee-993dd68f27b9@aklaver.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | 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(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
>
> 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(dot)klaver(at)aklaver(dot)com
From | Date | Subject | |
---|---|---|---|
Next Message | Adrian Klaver | 2017-01-02 17:03:23 | Re: Solving the SQL composition problem |
Previous Message | Karsten Hilbert | 2017-01-02 16:32:28 | Re: speed concerns with executemany() |