drh
8a056d486f
cover the recent optimizations involving updates to large JSON strings that indexed. FossilOrigin-Name: f9213289d09adfb0461d9644e80c7e889f4bae51563ae2e575a2c95336052bcb
The files in this subdirectory are used to help measure the performance of the SQLite JSON parser.
1.0 Prerequisites
-
Valgrind
-
Fossil
2.0 Setup
-
Run: "
tclsh json-generator.tcl | sqlite3 json100mb.db" to create the 100 megabyte test database. Do this so that the "json100mb.db" file lands in the directory from which you will run tests, not in the test/json subdirectory of the source tree. -
Build the baseline sqlite3.c file. ("
make sqlite3.c") -
Run "
sh json-speed-check.sh trunk". This creates the baseline profile in "jout-trunk.txt".
3.0 Testing
-
Build the sqlite3.c to be tested.
-
Run "
sh json-speed-check.sh x1". The profile output will appear in jout-x1.txt. Substitute any label you want in place of "x1". -
Run the script shown below in the CLI. Divide 2500 by the real elapse time from this test to get an estimate for number of MB/s that the JSON parser is able to process.
.open json100mb.db .timer on WITH RECURSIVE c(n) AS (VALUES(1) UNION ALL SELECT n+1 FROM c WHERE n<25) SELECT sum(json_valid(x)) FROM c, data1;