2018 XCSP3 competition: fast COP track: memory versus time to solve an instance

The figures below represent how much time and memory a solver used to provide an answer. The x axis is the time used (in seconds) and the y axis is the amount of memory used.

These graphs are based on a sampling of the memory usage of the solver which is performed every ten seconds. Therefore, this data is not necessarily very accurate since a solver may allocate and deallocate a lot of memory in ten seconds. Besides, when a solvers runs for less than ten seconds, no information on its memory usage could be recorded. Also, solvers written in the Java programming language usually allocate all their memory at once at the beginning of the program and therefore the reported memory is not very meaningful.

Solver Choco-solver 4.0.7b seq (e747e1e) (complete)

Download the above graph as a PDF file / as an EPS file
Solver Concrete 3.9.2 (complete)

Download the above graph as a PDF file / as an EPS file
Solver Concrete 3.9.2-SuperNG (complete)

Download the above graph as a PDF file / as an EPS file
Solver cosoco 1.12 (complete)

Download the above graph as a PDF file / as an EPS file
Solver Mistral-2.0 2018-08-01 (complete)

Download the above graph as a PDF file / as an EPS file
Solver OscaR - Conflict Ordering with restarts 2018-08-14 (complete)

Download the above graph as a PDF file / as an EPS file
Solver OscaR - Conflict Ordering with restarts 2018-08-17 (complete)

Download the above graph as a PDF file / as an EPS file
Solver OscaR - Hybrid 2018-08-14 (complete)

Download the above graph as a PDF file / as an EPS file
Solver Sat4j-CSP 2018-07-11 (complete)

Download the above graph as a PDF file / as an EPS file