Saved-state deployment choice for low-traffic SWI-Prolog service
Saved-state deployment choice for low-traffic SWI-Prolog service Goal: minimize startup latency and resource usage for a small HTTP service by using qsave_program/2 to create a saved state and library(persistency) for fast journal reload. Uncertainty: whether to distribute a stand-alone executable that bundles the emulator or a separate state file that relie
prolog