Let's see if I remember my notes from work ok at home: - Units are seconds. - IIRC user time is time spent in SQLite code, sys time is time spent in system (OS) calls. Both can vary from run to run and (at least in my testing) sys time tends to vary based off system usage.
If you want the best "real" time results, a later version of the command line also includes a "real" time that represents actual time elapsed but it also has updated query planning IIRC. On Mon Dec 15 2014 at 8:12:27 PM Simon Slavin <slav...@bigfraud.org> wrote: > Okay. I used '.timer on' in the shell tool. SQLite 3.7.13, if it > matters. Here are two sample lines I got in response to different INSERT > ... SELECT commands: > > CPU Time: user 880.710398 sys 353.260288 > > CPU Time: user 5073.001124 sys 11609.266484 > > The two commands were issued one after another on a computer which was > otherwise idle. > > Question 1: What are the units ? > > Question 2: I would have expected consistency in that user time was always > greater than system time. Or perhaps the other way around. Why is a > different one greater for the two examples ? > > Simon. > _______________________________________________ > sqlite-users mailing list > sqlite-users@sqlite.org > http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users > _______________________________________________ sqlite-users mailing list sqlite-users@sqlite.org http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
