at all the changes hit the disk together instead of separately.
-Ursprüngliche Nachricht-
Von: sqlite-users [mailto:sqlite-users-boun...@mailinglists.sqlite.org] Im
Auftrag von Kevin O'Gorman
Gesendet: Dienstag, 21. Februar 2017 19:22
An: sqlite-users
Betreff: [sqlite] Linux top co
Original message From: Roger Binns
Date: 21/02/2017 20:48 (GMT+00:00) To: SQLite mailing list
Subject: Re: [sqlite] Linux top command
and sqlite
On 21/02/17 10:22, Kevin O'Gorman wrote:
> Some of my stuff takes a while to run, and I like to keep tabs on it.
>
On 21/02/17 10:22, Kevin O'Gorman wrote:
> Some of my stuff takes a while to run, and I like to keep tabs on it.
> Right now, I'm running one of those, and the Linux top command shows
> extremely small CPU usage, and a status ("S" column) of "D" which the man
> page defines as "uninterruptable slee
I'll try the synchronous=off the next time I run it. As it happens, this
one
finished in 57 minutes, which is not bad, considering.
But, I wonder, could i not tell if it's doing lots of commits by looking at
the size of the ?.db-journal file? It gets pretty large.
On Tue, Feb 21, 2017 at 10:38
On 2/21/17, Kevin O'Gorman wrote:
> I'm not at all sure this is the right place to ask, but as it only comes up
> when I'm running one of
> my sqlite jobs, I thought I'd start here. I'm running Python 3.5 scripts
> in Linux 16.04.1 using the sqlite3 package. Machine is Core i5, 32GB RAM.
>
> Som
I'm not at all sure this is the right place to ask, but as it only comes up
when I'm running one of
my sqlite jobs, I thought I'd start here. I'm running Python 3.5 scripts
in Linux 16.04.1 using the sqlite3 package. Machine is Core i5, 32GB RAM.
Some of my stuff takes a while to run, and I like
6 matches
Mail list logo
