Abstract
The comparative study published in this journal by Fernandez and Hill benchmarked some constraint programming systems on a set of well-known puzzles. The current article examines the positive and negative aspects of this kind of benchmarking. The article analyses some pitfalls in benchmarking, recalling previous published results from benchmarking different kinds of software, and explores some issues in comparative benchmarking of CLP systems. A benchmarking exercise should cover a broad set of representative problems and a broad set of programming constructs. This can be achieved using two kinds of benchmarking: Applications Benchmarking and Unit Testing. The article reports the authors' experiences with these two kinds of benchmarking in the context of the CHIC-2 Esprit project. The benchmarks were used to unit test different features of the CLP system ECLiPSe and to compare application development with different high-level constraint platforms. The conclusion is that, in deciding which system to use on a new application, it is less useful to compare standard features of CLP systems, than to compare their relevant functionalities.
Original language | English |
---|---|
Pages (from-to) | 5-34 |
Number of pages | 30 |
Journal | Constraints |
Volume | 9 |
Issue number | 1 |
DOIs | |
Publication status | Published - 1 Jan 2004 |
Keywords
- Benchmarking
- CLP
- Constraint logic programming
- ECLiPSe
- Finite Domain
- Solver performance
- Unit Testing