Ulrich, try designing an experiment which removes SQLITE and measures
the performance of the other software layers. That might resolve your
dilemma.
JS
Ulrich Schöbel wrote:
Hi Richard,
thanks for trying to reproduce my 'problem'.
I'm using Linux 2.6.12 (Ubuntu Breezy Badger, a debian distro),
Tcl/Tk 8.4.12, sqlite 3.3.4, all pretty recent versions.
I made the same tests today with the same results.
Nevertheless, sqlite is by far faster than mySQL, so I'm going
to switch to it, anyway. But I'm still curious, where this effect
is coming from.
Thanks
Ulrich
On Wednesday 22 February 2006 14:27, [EMAIL PROTECTED] wrote:
Ulrich =?iso-8859-1?q?Sch=F6bel?= <[EMAIL PROTECTED]> wrote:
% time {db eval {select * from cust_persons where first_name='Ulrich'}}
1000 75.498 microseconds per iteration
% time {db eval {select * from cust_persons where first_name='Ulrich'}}
10000 51.6179 microseconds per iteration
% time {db eval {select * from cust_persons where first_name='Ulrich'}}
100 309.95 microseconds per iteration
% time {db eval {select * from cust_persons where first_name='Ulrich'}}
10 66.8 microseconds per iteration
Where do those 309.95 microseconds come from? What's the
difference between running a query 100 times or 10000 times?
Should I avoid running a select exactly 100 times for some
obscure reason?
FWIW, I am unable to reproduce your problem) I get
a smooth transition from 10 iterations (84 uS/iteration) to
10000 (58 uS/iteration).
What OS are you using? And what version of Tcl/Tk?
--
D. Richard Hipp <[EMAIL PROTECTED]>
