On 4 Aug 2016, at 4:00am, Kevin O'Gorman <kevinogorm...@gmail.com> wrote:
> I've got a problem set of about 1 billion game positions and 187GB to work > on (no, I won't have to solve them all) that took about 4 hours for a > generator program just to write. I wrote code to turn them into something > SQLite could import. Actually, it's import, build a non-primary index, and > alter table to add a column, all in sqlite3. Hmm. The closest I have to that is a 43 Gigabyte sqlite database which works fine. In that case almost all the space is taken up by one thin table which has a ridiculous number of rows. > The database was growing for about 1-1/2 days. Then its journal > disappeared, the file size dropped to zero, but sqlite3 is still running I assume that those are what 'ls' is showing you. Have you tried using 'lsof' or 'strace' ? Or monitoring the amount of free space on the disk to see if it's shrinking ? Simon. _______________________________________________ sqlite-users mailing list sqlite-users@mailinglists.sqlite.org http://mailinglists.sqlite.org/cgi-bin/mailman/listinfo/sqlite-users
