Re: speed concerns with executemany()

On 02/01/17 17:07, 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

That's great. Just a minor point: I won't overload executemany() with
this feature but add a new method UNLESS the semantics are exactly the
same especially regarding session isolation. Also, right now psycopg
keeps track of the number of affected rows over executemany() calls: I'd
like to not lose that because it is a breaking change to the API.

federico

--
Federico Di Gregorio federico(dot)digregorio(at)dndg(dot)it
DNDG srl http://dndg.it
We should forget about small efficiencies, say about 97% of the
time: premature optimization is the root of all evil. -- D.E.Knuth