Clemens Ladisch writes:
> Sarge Borsch wrote:
>> time xzdec something.sql.xz | sqlite3 something.db
>
> This measures only xzdec; it does not catch anything that sqlite3 does
> after xzdec has finished and closed the pipe.
Nitpick:
In bash or zsh, `time` is handled by shell,
An: SQLite mailing list <sqlite-users@mailinglists.sqlite.org>
Betreff: Re: [sqlite] Importing from single-insert-statement SQL dump is 61
times slower than importing from SQL dump with one statement per row
On Tuesday, 30 May, 2017 10:33, R Smith <rsm...@rsweb.co.za> said:
> Keith,
On Tuesday, 30 May, 2017 10:33, R Smith said:
> Keith, I think the OP meant he inserted the values using one single
> statement, not one single transaction, as in he did one ginormous INSERT
> INTO t(v1, v2...) VALUES (1, 2),(2,3),(..),,(1,
> 297829872); -
Keith, I think the OP meant he inserted the values using one single
statement, not one single transaction, as in he did one ginormous INSERT
INTO t(v1, v2...) VALUES (1, 2),(2,3),(..),,(1,
297829872); - 180MB or so worth... Probably lots of data in few rows,
because he is not
On 2017/05/30 2:01 PM, Hick Gunter wrote:
If you stuff all 18MB of your data into a single INSERT, then SQlite will need
to generate a single program that contains all 18MB of your data (plus code to
build rows aout of that). This will put a heavy strain on memory requirements
and offset any
m: sqlite-users [mailto:sqlite-users-boun...@mailinglists.sqlite.org]
> On Behalf Of Sarge Borsch
> Sent: Sunday, 28 May, 2017 04:58
> To: sqlite-users@mailinglists.sqlite.org
> Subject: [sqlite] Importing from single-insert-statement SQL dump is 61
> times slower than importing from SQL d
@mailinglists.sqlite.org
Betreff: [sqlite] Importing from single-insert-statement SQL dump is 61 times
slower than importing from SQL dump with one statement per row
I compared speed of importing (into an empty SQLite DB) from 2 kinds of SQL
dumps. Data is exactly the same in both cases, and xz-compressed size of SQL
Sarge Borsch wrote:
> time xzdec something.sql.xz | sqlite3 something.db
This measures only xzdec; it does not catch anything that sqlite3 does
after xzdec has finished and closed the pipe.
> IMO sqlite needs some optimisation for this case when there’s a huge
> INSERT statement, because the
I compared speed of importing (into an empty SQLite DB) from 2 kinds of SQL
dumps. Data is exactly the same in both cases, and xz-compressed size of SQL
dump is near 18MB in both cases.
First SQL dump has single big INSERT statement in single transaction.
Second SQL dump has one INSERT statement
9 matches
Mail list logo