On Tue, Oct 2, 2018 at 6:56 PM dmp <[email protected]> wrote:
> >> On Sep 25, 2018, at 11:14 AM, dmp <[email protected]> > wrote: > The timing given takes place at the beginning of the transfer > process and stops when completed, threads join. > Why aren't you measuring the time spent only in the SQLite writing thread? That would eliminate the overhead from the read-thread(s) and the queue in the middle, measuring only work by SQLite, instead of including the *waiting* for work in the queue. I wrote a similarly "piped" ETL not too long ago, and I output overall "wall" time of course, but also time spent reading, time spent writing, but important times when reader/writer threads were "stalled", because the pipe is full/empty (respectively). --DD _______________________________________________ sqlite-users mailing list [email protected] http://mailinglists.sqlite.org/cgi-bin/mailman/listinfo/sqlite-users
