David Mitchell wrote: > bill lam wrote: >> David Mitchell wrote: >> > Test: table table1(fname varchar(250),fsize long,fts timestamp, >>> int1 long, int2 long, int3 long) >>> >>> insert data(nr=.100000): da=. (nr$<250$'abc'),. >>> (<"0 i.nr),.(nr$<'2006-07-28'),.(nr$<"0 ]4 5 6),. >>> (nr$<"0]7 8 9),.(nr$<"0]0 1 2) >>> >>> ODBC/MSAccess/ddins - 10.12 seconds >>> SQLite/apply - 39.70 seconds >>> SQLite/apply/pragma sync off - 35.35 seconds >>> SQLite/exec 1 big sql/sync off - 98.84 seconds >>> SQLite/exec 1 big sql/begin/commit/sync off - 6.66 seconds >>> SQLite/exec 1 big sql/no field names/sync off - 98.59 seconds >>> SQLite/exec 1 big sql/no field names/sync off/begin/com - 5.95 seconds >> >> What is the "1 big sql"? >> > > A single text vector with 100000 inserts. > > -- > David Mitchell > ---------------------------------------------------------------------- > For information about J forums see http://www.jsoftware.com/forums.htm > >
It seems that apply can be further optimised using "exec 1 big sql" :-) -- regards, bill ---------------------------------------------------------------------- For information about J forums see http://www.jsoftware.com/forums.htm
