Soufflé has an interpreter and a compiler for executing Datalog programs. Profile information can be generated and visualized with a profiling tool to understand the performance of a program. The Soufflé execution mode (compile, interpret etc.) is determined by the argument parameters of the souffle command.
Input / Output
The Soufflé permits facts to be sourced from tab-separated input files to separate Datalog programs from their data. In Datalog literature the tab-separated input files can be seen as the extensional database (EDB) of the program. The default location of the input files is specified by the parameter
-F <fact-dir>. If the flag is not specified, it is assumed that the fact files are stored in the current directory. The default filenames of the input files consists of the name of the input relations with an extension
.facts. For example, the declaration
.decl my_relation(a:number,b:number) .input my_relation
defines an input relation
my_relation with two number columns. Note that a relation becomes an input relation with the keyword
input at the end of a declaration. For the aforementioned example , souffle expects a tab-separated file
my_relation.facts in either the current directory (if no
-F flag was specified) or in the directory
<fact-dir> with the option
-F <fact-dir>. Note that there is an exception if a relation is an input relation and is declared in an instantiation of a component.
If more precise control over file location is needed, more options can be added to the input directive. For example
.decl my_relation(a:number,b:number) .input my_relation(filename="<path to input file>")
The output relations of a Datalog program are written to file in the current directory if no command line parameters, directives in the Datalog program, are given. The default output directory can be specified with the flag
-D <output-dir> Output is written to standard output with the parameter
-D-. For example, the relation
.decl result(a:number,b:number,c:number) .output result
has three number columns that are written either to the file
result.csv in the directory
<output-dir> using the flag
-D <output-dir> or to standard output using the flag
-D-. As with the input directive, more detailed output can be specified via the output directive.
.decl result(a:number,b:number,c:number) .output result(filename="<path to output file")
Both input and output file IO can also benefit from the
compress options, for example,
.decl result(a:number,b:number,c:number) .output result(filename="<path to output file", delimiter=",", compress=true)
This will output using “,” as a column delimiter and compress the output using gzip.
Multiple input and output directives may be given in order to read input from, or send output to, multiple locations.
If the directive
printsize is used, the size of the relation is printed to the standard output.
For example, the relation
.decl result(a:number,b:number,c:number) .printsize
is not printed to a file. Instead the number of tuples of relation
result are written to standard output.
The interpreter is the default option when invoking the
souffle as a command line tool. When souffle is invoked in interpreter mode, the parser translates the Datalog program to a RAM program, and executes the RAM program on-the-fly. For computationally intensive Datalog programs, the interpretation is slower than the compilation to C++. However, the interpreter has no costs for compiling a RAM program to C++ and invoking the C++ compiler, which is for larger programs expensive (in the order of minutes).
The compiler of souffle is enabled using the flag
-c, the flag
-o <exec>, or the flag
-g <class.cpp> (or the long versions, respectively,
--generate=<class.cpp>). The compiler translates a Datalog program to a C++ program that is compiled to an executable and executed. The performance of a compiled Datalog is superior to the interpreter, however, the compilation of the C++ program may take some time.
The difference between the flag
-o is whether the program is compiled and immediately executed with the former option or whether an executable is generated with the latter option. If compiled with option
-o <exec>, the executable is a standalone program whose options can be queried with flag
-h. The following message would be produced,
============================================================================ souffle -- A datalog engine. Usage: souffle [OPTION] FILE. ---------------------------------------------------------------------------- Options: -F, --fact-dir=<DIR> Specify directory for fact files. -I, --include-dir=<DIR> Specify directory for include files. -D, --output-dir=<DIR> Specify directory for output files. If <DIR> is `-` then stdout is used. -j, --jobs=<N> Run interpreter/compiler in parallel using N threads, N=auto for system default. -c, --compile Generate C++ source code, compile to a binary executable, then run this executable. -g, --generate=<FILE> Generate C++ source code for the given Datalog program and write it to <FILE>. If <FILE> is `-` then stdout is used. --inline-exclude=<RELATIONS> Prevent the given relations from being inlined. Overrides any `inline` qualifiers. -s, --swig=<LANG> Generate SWIG interface for given language. The values <LANG> accepts is java and python. -L, --library-dir=<DIR> Specify directory for library files. -l, --libraries=<FILE> Specify libraries. -w, --no-warn Disable warnings. -m, --magic-transform=<RELATIONS> Enable magic set transformation changes on the given relations, use '*' for all. --magic-transform-exclude=<RELATIONS> Disable magic set transformation changes on the given relations. Overrides `magic-transform`. Implies `inline-exclude` for the given relations. -M, --macro=<MACROS> Set macro definitions for the pre-processor -z, --disable-transformers=<TRANSFORMERS> Disable the given AST transformers. -o, --dl-program=<FILE> Generate C++ source code, written to <FILE>, and compile this to a binary executable (without executing it). --live-profile Enable live profiling. -p, --profile=<FILE> Enable profiling, and write profile data to <FILE>. -u, --profile-use=<FILE> Use profile log-file <FILE> for profile-guided optimization. --profile-frequency Enable the frequency counter in the profiler. -r, --debug-report=<FILE> Write HTML debug report to <FILE>. -P, --pragma=<OPTIONS> Set pragma options. -t, --provenance=<[ none | explain | explore ]> Enable provenance instrumentation and interaction. -v, --verbose Verbose output. --version Version. --show=<[ parse-errors | precedence-graph | scc-graph | transformed-datalog | transformed-ram | type-analysis ]> Print selected program information. --parse-errors Show parsing errors, if any, then exit. -h, --help Display this help message. --legacy Enable legacy support. ---------------------------------------------------------------------------- Version: XXXX ---------------------------------------------------------------------------- Copyright (c) 2016-21 The Souffle Developers. Copyright (c) 2013-16 Oracle and/or its affiliates. All rights reserved. ============================================================================
The defaults are taken from the compiler invocation, which may be overwritten with user defined parameters of the standalone executable.
Note that if the profiling option is enabled, the standalone executable has the additional option
-p (see below).
As a side-effect of execution, a profile log can be generated. The profile log can be visualized using the souffle-profiler. The option for enabling the profile log is
-p <log-file> that works for the interpreter as well as the compiler. The profiler is described in the profiler section.
Soufflé has various command line options to control the execution mode and parameterise the Soufflé input program.
Warnings produced by Soufflé can be disabled with the option
All execution modes of Soufflé provide parallel evaluation. The parallel evaluation is enabled with the option
Verbose message output
More verbose output can be produced by using the verbose flag
A debug report in HTML format is generated using the flag
--debug-report=<report.html>. Note that for the debug report, it is essential that graphviz is installed to render the dependency graphs.