On Mon, Jan 16, 2012 at 4:37 AM, Max Vlasov <max.vla...@gmail.com> wrote:
> On Sun, Jan 15, 2012 at 3:35 AM, John Elrick <john.elr...@fenestra.com > >wrote: > > > On Fri, Jan 13, 2012 at 5:13 PM, Max Vlasov <max.vla...@gmail.com> > wrote: > > > > 5,008 calls to > > > > UPDATE RESPONSES SET > > RESPONSE_NAME = :RESPONSE_NAME, > > prelisted_value = :prelisted_value > > WHERE RESPONSE_OID = :RESPONSE_OID > > > > 3.6.17: 382 ms > > 3.7.9: 5,924 ms > > > > > > John, I did a test reproducing your job with 80000 inserts > insert into responses default values > > and making 5000 calls in transaction > > UPDATE RESPONSES SET RESPONSE_NAME = '12345', prelisted_value='12345' > WHERE RESPONSE_OID = abs(random() % 80000) > > is this test ok for you (still showing bad performance)? > > On my side it's about 800 ms for 3.7.9 static and about 6000 memory calls > during the query. For 3.6.20 the number of calls ~ 7000, the time is > similar. > > Your test was hard coded. Mine uses bindings. However, I'm not arguing that something odd is going on. I'm just trying to understand what. _______________________________________________ sqlite-users mailing list sqlite-users@sqlite.org http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
