anchor.diff:  The benchmark configuration currently expects an `<inputSolutionFile>` element, so a separate file, for each dataset.
   There are 2 ways to deal with this if your dataset is in a relational database or another type of repository:
   
  -* Extract the datasets from the database and serialize them to a local file (for example as XML with `XStreamSolutionFileIO` if XML isn't too verbose). Then use those files an `<inputSolutionFile>` elements.
  -* For each dataset, create a txt file that holds the unique id of the dataset. Write <<customSolutionFileIO,a custom `SolutionFileIO`>> that reads that identifier, connects to the database and extract the problem identified by that id. Configure those txt files as `<inputSolutionFile>` elements.
  +* Extract the datasets from the database and serialize them to a local file (for example as XML with `XStreamSolutionFileIO` if XML isn't too verbose).
  +Then use those files an `<inputSolutionFile>` elements.
  +* For each dataset, create a txt file that holds the unique id of the dataset.
  +Write <<customSolutionFileIO,a custom `SolutionFileIO`>> that reads that identifier, connects to the database and extract the problem identified by that id. Configure those txt files as `<inputSolutionFile>` elements.
   
   
   [NOTE]
  
positive.code: ====
  
  
  If an `Exception` or `Error` occurs in a single benchmark, the entire Benchmarker will not fail-fast (unlike everything else in Planner). Instead, the Benchmarker will continue to run all other benchmarks, write the benchmark report and then fail (if there is at least 1 failing single benchmark). The failing benchmarks will be clearly marked as such in the benchmark report.
  
  
  [[inheritedSolverBenchmark]]
  
negative.code: ----
  
  
  Those input files need to have been written with a `XStreamSolutionFileIO` instance, not just any `XStream` instance,
  because the `XStreamSolutionFileIO` uses a customized `XStream` instance.
  Add XStream annotations (such as ``@XStreamAlias``) on your domain classes to use a less verbose XML format.
  
  [WARNING]
  ====
  XML is a very verbose format.
  Reading or writing large datasets in this format can cause an `OutOfMemoryError`, `StackOverflowError` or large performance degradation.
  ====
  
  
  