A case for simple SAT solvers

Jinbo Huang*

*Corresponding author for this work

Research output: Chapter in Book/Report/Conference proceedingConference contributionpeer-review

23 Citations (Scopus)

Abstract

As SAT becomes more popular due to its ability to handle large real-world problems, progress in efficiency appears to have slowed down over the past few years. On the other hand, we now have access to many sophisticated implementations of SAT solvers, sometimes boasting large amounts of code. Although low-level optimizations can help, we argue that the SAT algorithm itself offers opportunities for more significant improvements. Specifically, we start with a no-frills solver implemented in less than 550 lines of code, and show that by focusing on the central aspects of the solver, higher performance can be achieved over some best existing solvers on a large set of benchmarks. This provides motivation for further research into these more important aspects of SAT algorithms, which we hope will lead to future significant advances in SAT.

Original languageEnglish
Title of host publicationPrinciples and Practice of Constraint Programming - CP 2007 - 13th International Conference, CP 2007, Proceedings
PublisherSpringer Verlag
Pages839-846
Number of pages8
ISBN (Print)3540749691, 9783540749691
DOIs
Publication statusPublished - 2007
Externally publishedYes
Event13th International Conference on Principles and Practice of Constraint Programming, CP 2007 - Providence, RI, United States
Duration: 23 Sept 200727 Sept 2007

Publication series

NameLecture Notes in Computer Science (including subseries Lecture Notes in Artificial Intelligence and Lecture Notes in Bioinformatics)
Volume4741 LNCS
ISSN (Print)0302-9743
ISSN (Electronic)1611-3349

Conference

Conference13th International Conference on Principles and Practice of Constraint Programming, CP 2007
Country/TerritoryUnited States
CityProvidence, RI
Period23/09/0727/09/07

Fingerprint

Dive into the research topics of 'A case for simple SAT solvers'. Together they form a unique fingerprint.

Cite this