On Fri, Jan 13, 2012 at 3:19 PM, Normand Mongeau <[email protected]>wrote:
> not really, no. This is a server that receives files, and the transaction > below means a file has arrived. > Does your server have a really, really slow disk drive? Transaction commit normally takes milliseconds. I'm not sure why you are having problems. Might another process be soaking up all the disk I/O bandwidth and making your process have to wait for an available slot? > > Normand > > > > On 2012-01-13 15:16, Simon Slavin wrote: > >> On 13 Jan 2012, at 7:57pm, Normand Mongeau wrote: >> >> begin immediate transaction >>> insert 1 record in tableA >>> insert 1 record in tableB >>> insert 1 record in tableC >>> commit transaction >>> >>> Inserting 534 records takes about 75 seconds. Most of the time (about 71 >>> seconds) is spent on the commit transaction instruction. >>> >> Can you put one transaction around the whole lot rather than 178 separate >> transactions ? >> >> Simon. >> ______________________________**_________________ >> sqlite-users mailing list >> [email protected] >> http://sqlite.org:8080/cgi-**bin/mailman/listinfo/sqlite-**users<http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users> >> >> > ______________________________**_________________ > sqlite-users mailing list > [email protected] > http://sqlite.org:8080/cgi-**bin/mailman/listinfo/sqlite-**users<http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users> > -- D. Richard Hipp [email protected] _______________________________________________ sqlite-users mailing list [email protected] http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
