Trace number 230325

Some explanations

A solver is run under the control of another program named runsolver. runsolver is in charge of imposing the CPU time limit and the memory limit to the solver. It also monitors some information about the process. The trace of the execution of a solver is divided into four (or five) parts:
  1. SOLVER DATA
    This is the output of the solver (stdout and stderr).
    Note that some very long lines in this section may be truncated by your web browser ! In such a case, you may want to use the "Download as text" link to get the trace as a text file.

    When the --timestamp option is passed to the runsolver program, each line output by the solver is prepended with a timestamp which indicates at what time the line was output by the solver. Times are relative to the start of the program, given in seconds, and are wall clock time (not CPU time).

    As some 'v lines' may be very long (sometimes several megabytes), the 'v line' output by your solver may be split on several lines to help limit the size of the trace recorded in the database. In any case, the exact output of your solver is preserved in a trace file.
  2. VERIFIER DATA
    The output of the solver is piped to a verifier program which will search a value line "v " and, if found, will check that the given interpretation satisfies all constraints.
  3. CONVERSION SCRIPT DATA (Optionnal)
    When a conversion script is used, this section shows the messages that were output by the conversion script.
  4. WATCHER DATA
    This is the informations gathered by the runsolver program. It first prints the different limits. There's a first limit on CPU time set to X seconds (see the parameters in the trace). After this time has ellapsed, runsolver sends a SIGTERM and 2 seconds later a SIGKILL to the solver. For safety, there's also another limit set to X+30 seconds which will send a SIGXPU to the solver. The last limit is on the virtual memory used by the process (see the parameters in the trace).
    Every ten seconds, the runsolver process fetches the content of /proc/loadavg, /proc/pid/stat and /proc/pid/statm (see man proc) and prints it as raw data. This is only recorded in case we need to investigate the behaviour of a solver. The memory used by the solver (vsize) is also given every ten seconds.
    When the solver exits, runsolver prints some informations such as status and time. CPU usage is the ratio CPU Time/Real Time.
  5. LAUNCHER DATA
    These informations are related to the script which will launch the solver. The most important informations are the command line given to the solver, the md5sum of the different files and the dump of the /proc/cpuinfo and /proc/meminfo which provides some useful information on the computer.

Solver answer on this benchmark

Solver NameAnswerCPU timeWall clock time
Abscon 109 ESACSAT 0.91886 1.02369

DiagnosticValue
CHECKS123067
NODES93

General information on the benchmark

Namegeom/
geo50-20-d4-75-97_ext.xml
MD5SUM58b6187a22c96037a9bcdd1cf57e5322
Bench Category2-ARY-EXT (binary constraints in extension)
Best result obtained on this benchmarkSAT
Best CPU time to get the best result obtained on this benchmark0.140977
SatisfiableYES
(Un)Satisfiability was provedYES
Number of variables50
Number of constraints383
Maximum constraint arity2
Maximum domain size20
Number of constraints which are defined in extension383
Number of constraints which are defined in intension0
Global constraints used (with number of constraints)

Solver Data (download as text)

0.36	   
0.36	Abscon 109 (November, 2006)
0.36	   
0.36	   configuration
0.36	     name=esac.xml
0.40	   
0.40	   instance
0.40	     name=/tmp/evaluation/230325-1168316520/unknown.xml
0.43	   
0.43	   domains being loaded...
0.44	   
0.44	   variables being loaded...
0.47	     nbVariables=50  nbDomainTypes=1  minDomainSize=20  maxDomainSize=20
0.47	       =>  wckTime=0.1  cpuTime=0.08  mem=6M951
0.47	   
0.47	   relations being loaded...
0.59	   
0.59	   constraints being loaded...
0.70	     nbConstraints=383  nbRelationTypes=383  nbExtensionStructures=383  nbSharedExtensionStructures=0
0.70	     nbConflictsStructures=383  nbSharedConflictsStructures=0  nbSharedBinaryRepresentations=3395  maxDegree=26
0.70	     maxArity=2
0.70	       =>  wckTime=0.325  cpuTime=0.23  mem=13M827
0.74	   
0.74	   solver IterativeSystematicSolver being built... 
0.89	       =>  wckTime=0.518  cpuTime=0.36  mem=15M221
0.94	   
0.94	   preprocessing
0.94	     nbConstraintChecks=60468  nbPropagations=899  nbRevisions=6106  nbUselessRevisions=5001  nbSingletonTests=64
0.94	     nbEffectiveSingletonTests=0  nbESACBranches=6  nbRemovedValues=0  detectedInconsistency=no
0.94	       =>  wckTime=0.049  cpuTime=0.03  mem=15M221
0.96	   
0.96	   search
0.96	     run=0  nbConstraintChecks=30791  nbPropagations=1328  nbRevisions=10823  nbUselessRevisions=8804  nbAssignments=27
0.96	     nbFailedAssignments=10  nbBacktracks=11  nbVisitedNodes=44  nbRestartNogoods=0  mapSize=11  nbInferences=0
0.96	     nbTooLargeKeys=0
0.96	       =>  wckTime=0.072  cpuTime=0.05  mem=15M221
0.98	   
0.98	   search
0.98	     run=1  nbConstraintChecks=62599  nbPropagations=3180  nbRevisions=26040  nbUselessRevisions=21036  nbAssignments=93
0.98	     nbFailedAssignments=17  nbBacktracks=20  nbVisitedNodes=121  nbRestartNogoods=3  mapSize=18  nbInferences=0
0.98	     nbTooLargeKeys=0
0.98	       =>  wckTime=0.093  cpuTime=0.06  mem=15M221
0.99	   
0.99	   global
0.99	     nbConstraintChecks=123067  nbPropagations=4079  nbRevisions=32146  nbUselessRevisions=26037  nbRestartNogoods=3
0.99	     solvingWckTime=0.094  solvingCpuTime=0.06  expiredTime=no  totalExploration=no  nbFoundSolutions=1
0.99	     globalCpuTime=0.47
0.99	       =>  wckTime=0.614  cpuTime=0.42  mem=15M221
0.99	   
0.99	s SATISFIABLE
0.99	v 19 12 2 14 2 2 18 4 9 7 9 7 7 13 5 17 16 7 1 13 8 7 3 2 10 8 1 13 16 5 15 18 7 12 19 16 12 15 5 10 12 11 19 13 19 9 18 7 9 19 
0.99	d NODES 93
0.99	d CHECKS 123067
0.99	   
0.99	   totalWckTime=0.696  totalCpuTime=0.47

Verifier Data (download as text)

OK

Watcher Data (download as text)

runsolver version 3.1.3 (c) roussel@cril.univ-artois.fr

command line: runsolver --timestamp -w ROOT/results/node24/watcher-230325-1168316520 -o ROOT/results/node24/solver-230325-1168316520 -C 1800 -M 900 java -Xms756M -Xmx756M -XX:PermSize=10m -XX:MaxPermSize=10m -jar abscon109.jar esac.xml 1 XSax /tmp/evaluation/230325-1168316520/unknown.xml 

Enforcing CPUTime limit (soft limit, will send SIGTERM then SIGKILL): 1800 seconds
Enforcing CPUTime limit (hard limit, will send SIGXCPU): 1830 seconds
Enforcing VSIZE limit (soft limit, will send SIGTERM then SIGKILL): 921600 KiB
Enforcing VSIZE limit (hard limit, stack expansion will fail with SIGSEGV, brk() and mmap() will return ENOMEM): 972800 KiB
Current StackSize limit: 10240 KiB

/proc/loadavg: 1.80 1.94 2.02 5/86 17818
/proc/meminfo: memFree=467352/2055920 swapFree=4192812/4192956
[pid=17817] ppid=17815 vsize=18540 CPUtime=0
/proc/17817/stat : 17817 (runsolver) R 17815 17817 16999 0 -1 4194368 17 0 0 0 0 0 0 0 20 0 1 0 180047519 18984960 279 18446744073709551615 4194304 4267372 548682068960 18446744073709551615 237788261671 0 2147483391 4096 24578 0 0 0 17 0 0 0
/proc/17817/statm: 4635 279 244 17 0 2626 0

[startup+0.107569 s]
/proc/loadavg: 1.80 1.94 2.02 5/86 17818
/proc/meminfo: memFree=467352/2055920 swapFree=4192812/4192956
[pid=17817] ppid=17815 vsize=907676 CPUtime=0.05
/proc/17817/stat : 17817 (java) R 17815 17817 16999 0 -1 0 2317 0 14 0 3 2 0 0 20 0 4 0 180047519 929460224 2077 18446744073709551615 134512640 134570532 4294956480 18446744073709551615 4153552326 0 4 0 7368 18446744073709551615 0 0 17 0 0 0
/proc/17817/statm: 226919 2077 1166 14 0 214502 0
Current children cumulated CPU time (s) 0.05
Current children cumulated vsize (KiB) 907676

[startup+0.519613 s]
/proc/loadavg: 1.80 1.94 2.02 5/86 17818
/proc/meminfo: memFree=467352/2055920 swapFree=4192812/4192956
[pid=17817] ppid=17815 vsize=915328 CPUtime=0.44
/proc/17817/stat : 17817 (java) R 17815 17817 16999 0 -1 0 6329 0 20 0 38 6 0 0 24 0 8 0 180047519 937295872 6087 18446744073709551615 134512640 134570532 4294956480 18446744073709551615 4294960144 0 4 0 23759 18446744073709551615 0 0 17 0 0 0
/proc/17817/statm: 228832 6087 2137 14 0 215302 0
Current children cumulated CPU time (s) 0.44
Current children cumulated vsize (KiB) 915328

Child status: 0
Real time (s): 1.02369
CPU time (s): 0.91886
CPU user time (s): 0.827874
CPU system time (s): 0.090986
CPU usage (%): 89.7598
Max. virtual memory (cumulated for all children) (KiB): 915456

getrusage(RUSAGE_CHILDREN,...) data:
user time used= 0.827874
system time used= 0.090986
maximum resident set size= 0
integral shared memory size= 0
integral unshared data size= 0
integral unshared stack size= 0
page reclaims= 8782
page faults= 20
swaps= 0
block input operations= 0
block output operations= 0
messages sent= 0
messages received= 0
signals received= 0
voluntary context switches= 984
involuntary context switches= 1068

runsolver used 0.003999 s user time and 0.008998 s system time

The end

Launcher Data (download as text)

Begin job on node24 on Tue Jan  9 04:22:01 UTC 2007


IDJOB= 230325
IDBENCH= 6408
FILE ID= node24/230325-1168316520

PBS_JOBID= 3502471

Free space on /tmp= 66473 MiB

BENCH NAME= HOME/pub/bench/CPAI06/geom/geo50-20-d4-75-97_ext.xml
COMMAND LINE= java -Xms756M -Xmx756M -XX:PermSize=10m -XX:MaxPermSize=10m -jar abscon109.jar esac.xml 1 XSax /tmp/evaluation/230325-1168316520/unknown.xml
RUNSOLVER COMMAND LINE= runsolver  --timestamp  -w ROOT/results/node24/watcher-230325-1168316520 -o ROOT/results/node24/solver-230325-1168316520 -C 1800 -M 900  java -Xms756M -Xmx756M -XX:PermSize=10m -XX:MaxPermSize=10m -jar abscon109.jar esac.xml 1 XSax /tmp/evaluation/230325-1168316520/unknown.xml

META MD5SUM SOLVER= 9b91398c18c9fe54a6c4cfb50dadce08
MD5SUM BENCH=  58b6187a22c96037a9bcdd1cf57e5322

RANDOM SEED= 376350631

TIME LIMIT= 1800 seconds

MEMORY LIMIT= 900 MiB


/proc/cpuinfo:
processor	: 0
vendor_id	: GenuineIntel
cpu family	: 15
model		: 4
model name	:                   Intel(R) Xeon(TM) CPU 3.00GHz
stepping	: 3
cpu MHz		: 3000.234
cache size	: 2048 KB
fpu		: yes
fpu_exception	: yes
cpuid level	: 5
wp		: yes
flags		: fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm syscall nx lm pni monitor ds_cpl cid cx16 xtpr
bogomips	: 5914.62
clflush size	: 64
cache_alignment	: 128
address sizes	: 36 bits physical, 48 bits virtual
power management:

processor	: 1
vendor_id	: GenuineIntel
cpu family	: 15
model		: 4
model name	:                   Intel(R) Xeon(TM) CPU 3.00GHz
stepping	: 3
cpu MHz		: 3000.234
cache size	: 2048 KB
fpu		: yes
fpu_exception	: yes
cpuid level	: 5
wp		: yes
flags		: fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm syscall nx lm pni monitor ds_cpl cid cx16 xtpr
bogomips	: 5586.94
clflush size	: 64
cache_alignment	: 128
address sizes	: 36 bits physical, 48 bits virtual
power management:


/proc/meminfo:
MemTotal:      2055920 kB
MemFree:        468024 kB
Buffers:          5308 kB
Cached:        1469408 kB
SwapCached:          0 kB
Active:         904048 kB
Inactive:       630368 kB
HighTotal:           0 kB
HighFree:            0 kB
LowTotal:      2055920 kB
LowFree:        468024 kB
SwapTotal:     4192956 kB
SwapFree:      4192812 kB
Dirty:            2540 kB
Writeback:           0 kB
Mapped:          82128 kB
Slab:            38268 kB
Committed_AS:  3819524 kB
PageTables:       2320 kB
VmallocTotal: 536870911 kB
VmallocUsed:    264952 kB
VmallocChunk: 536605679 kB
HugePages_Total:     0
HugePages_Free:      0
Hugepagesize:     2048 kB

Free space on /tmp at the end= 66473 MiB



End job on node24 on Tue Jan  9 04:22:04 UTC 2007