t the
output from EXPLAIN and EXPLAIN QUERY PLAN to get an idea of the work involved.
-Ursprüngliche Nachricht-
Von: Simon Slavin [mailto:slav...@bigfraud.org]
Gesendet: Montag, 15. Dezember 2014 10:12
An: General Discussion of SQLite Database
Betreff: [sqlite] '.timer on' in the
Hi, Simon.
> 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 ?
>
System time may be much greater if it involves a
On Mon, Dec 15, 2014 at 10:24 AM, Simon Slavin wrote:
>
> On 15 Dec 2014, at 9:20am, Donald Shepherd
> wrote:
> > - 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
On 15 Dec 2014, at 9:20am, Donald Shepherd wrote:
> - 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 t
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 "
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
6 matches
Mail list logo
