mirror of
https://github.com/tursodatabase/libsql.git
synced 2024-12-16 19:31:15 +00:00
44 lines
1.3 KiB
Markdown
44 lines
1.3 KiB
Markdown
The files in this subdirectory are used to help measure the performance
|
|
of the SQLite JSON functions, especially in relation to handling large
|
|
JSON inputs.
|
|
|
|
# 1.0 Prerequisites
|
|
|
|
1. Valgrind
|
|
|
|
2. Fossil
|
|
|
|
3. tclsh
|
|
|
|
# 2.0 Setup
|
|
|
|
1. 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.
|
|
|
|
2. Build the baseline sqlite3.c file with sqlite3.h and shell.c.
|
|
("`CFLAGS='-Os -g' make -e clean sqlite3.c`")
|
|
|
|
3. Run "`sh json-speed-check.sh trunk`". This creates the baseline
|
|
profile in "jout-trunk.txt".
|
|
|
|
# 3.0 Testing
|
|
|
|
1. Build the sqlite3.c (with sqlite3.h and shell.c) to be tested.
|
|
|
|
2. 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".
|
|
|
|
3. 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;
|
|
~~~~
|