Use PrecompileTools for precompilation
Not sure this is a clear win. Some notes: This uses the simulation from the unit tests as a representative workload. This workload might be suboptimal in some ways: - Quite slow, 55 seconds for precompilation on my laptop. - Uses ficticious Wolpertinger species instead of Skylark, this might not be optimal for the real simulation. - There might be unnecessary data stored in the precompile file, this could be reduced with `@setup_workload` from PrecompileTools. Other notes: - Need to set up a representative benchmark, measuring changes in package load time and TTFX. - After running precompilation from the Pkg REPL, and then running tests, precompilation runs again (taking 55 seconds again). Why?
Showing
- Manifest.toml 122 additions, 571 deletionsManifest.toml
- Project.toml 2 additions, 0 deletionsProject.toml
- precompile/almass_crop_growth_curves.csv 650 additions, 0 deletionsprecompile/almass_crop_growth_curves.csv
- precompile/crop_data_general.csv 21 additions, 0 deletionsprecompile/crop_data_general.csv
- precompile/fields_jena.tif 0 additions, 0 deletionsprecompile/fields_jena.tif
- precompile/landcover_jena.tif 0 additions, 0 deletionsprecompile/landcover_jena.tif
- precompile/parameters.toml 43 additions, 0 deletionsprecompile/parameters.toml
- precompile/weather_jena.csv 8402 additions, 0 deletionsprecompile/weather_jena.csv
- src/Persefone.jl 6 additions, 3 deletionssrc/Persefone.jl
Loading
Please register or sign in to comment