I'd like to optimize performance for batch insert operations, for example when a database is restored from JSON dump (say 1000 INSERT statements are run).

I'm using OPFSCoopSyncVFS + sync build in a worker.

I have the following questions:

1. With wa-sqlite (without using experimental WAL modes, etc.) is it better for performance to wrap the INSERT statements with BEGIN/COMMIT or SAVEPOINT/RELEASE?
2. Is SAVEPOINT also helping with performance, or only BEGIN?
3. What happens when I do the following?
   BEGIN
   SAVEPOINT
   ... 1k INSERT
   RELEASE
   COMMIT

Is there anything else I'm missing for optimizing batch inserts?

Python has a special commandexecutemany(), but I haven't seen an analogue of this in either node's better-sqlite3 nor in wa-sqlite.

I guess, outside of a special C-level batch insert function, our best bet is wrapping it in a transaction or savepoint?