To use this package, you must use our modified version of Julia compiler.
Due to some technical limitations, Julia fails to build system image in our modified compiler. So we need to first build the system image in an unmodified Julia, then apply our patch.
Firstly download our fork of Julia https://github.com/ChenNingCong/julia.git
, then checkout to commit 55808a56e0fcd147b10e35d64721a1849c841196
. Build Julia normally following official documents. Then switch to master
and run make julia-noimage-release
. This will build julia without running system image build process. After this you can run make binary-dist
to get a packed julia distribution (not necessary).
Firstly ensure that you install this package BuildSytem
in the same directory where you install you julia executable. For example, if you unpack your julia installation (or build) at path /home/username/julia
, then you also need to install the package with path /home/username/BuildSystem
.
To run the demo, follow these steps:
- At root path of
BuildSystem
, runsource test/help.sh
in shell. This script creates two shortcutsju18
andjbuild
.ju18
is used to start julia in the image-codegen mode, andjbuild
drives the makefile system for julia. - At root path of
BuildSystem
, runjbuild test/json_ninja.jl
. This will build a compiled cache ofJSON
package. You need to wait a couple of time because we need to firstly compileBuildSystem
,Test
andPkg
, on which the build system depends. You need to compile them only once because the results are cached and can be reused. The actual time spend on compiling JSON is small. - If you encounter no error at step 1 and 2, you can check the directory of
test/binary
, where you can find a bundle of compiled binary files.
Now you have the compiled binary generated from test files, it's time to use these binaries!
- At root path of
BuildSystem
, runju18
. This command will start a new Julia (version 1.8.0-DEV). Pkg.activate("test")
to activate the environment attest
folder. RunPkg.instantiate()
to install dependencies. This may take some time, forPkg.instantiate
is not compiled due to some technical limitation.- Now excecute
@use JSON
, to import both the package and the binary. - Run
x = JSON.parse("123")
, you can notice that the latency is completely gone. - Run
s = "{\"a_number\" : 5.0, \"an_array\" : [\"string\", 9]}" JSON.parse(s)
- You may notice that step 5 still have latency. This is largely due to the compilation of
display
in the REPL, which is generally not touched in test file. To conquer this problem, runsaveWork([:JSON])
. This will magically save all the compiled code in JSON generated in this REPL session. - To use the REPL cache, the next time you open REPL, after you load JSON library (after step 3, this is very important), run
loadREPL()
to bring in the binary cache you save, repeat step 5,6 and now you can see that the latency is completely gone!!!