Trace number 203929

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.940856 0.96882

DiagnosticValue
CHECKS2465805
NODES0

General information on the benchmark

Namedomino/
domino-300-100.xml
MD5SUMeff2a61155581d1c1ba66ec540fd5989
Bench Category2-ARY-INT (binary constraints in intension)
Best result obtained on this benchmarkSAT
Best CPU time to get the best result obtained on this benchmark0.028995
SatisfiableYES
(Un)Satisfiability was provedYES
Number of variables300
Number of constraints300
Maximum constraint arity2
Maximum domain size100
Number of constraints which are defined in extension0
Number of constraints which are defined in intension300
Global constraints used (with number of constraints)

Solver Data (download as text)

0.29	   
0.29	Abscon 109 (November, 2006)
0.29	   
0.29	   configuration
0.29	     name=esac.xml
0.32	   
0.32	   instance
0.32	     name=/tmp/evaluation/203929-1168165033/unknown.xml
0.35	   
0.35	   domains being loaded...
0.36	   
0.36	   variables being loaded...
0.43	     nbVariables=300  nbDomainTypes=1  minDomainSize=100  maxDomainSize=100
0.43	       =>  wckTime=0.133  cpuTime=0.11  mem=8M903
0.43	   
0.43	   predicates being loaded...
0.43	   
0.43	   constraints being loaded...
0.59	     nbConstraints=300  nbConvertedConstraints=300  nbConvertConstraintsChecks=20000  nbExtensionStructures=2
0.59	     nbSharedExtensionStructures=298  nbConflictsStructures=2  nbSharedConflictsStructures=298
0.59	     nbSharedBinaryRepresentations=298  maxDegree=2  maxArity=2
0.59	       =>  wckTime=0.298  cpuTime=0.22  mem=9M911
0.63	   
0.63	   solver IterativeSystematicSolver being built... 
0.81	       =>  wckTime=0.515  cpuTime=0.36  mem=16M582
0.93	   
0.93	   preprocessing
0.93	     nbConstraintChecks=2465805  nbPropagations=30001  nbRevisions=30300  nbUselessRevisions=600  nbSingletonTests=300
0.93	     nbEffectiveSingletonTests=0  nbESACBranches=1  nbRemovedValues=29700  detectedInconsistency=no
0.93	       =>  wckTime=0.119  cpuTime=0.1  mem=16M582
0.94	   
0.94	   global
0.94	     nbConstraintChecks=2465805  nbPropagations=30001  nbRevisions=30300  nbUselessRevisions=600  nbRestartNogoods=0
0.94	     solvingWckTime=0.12  solvingCpuTime=0.1  expiredTime=no  totalExploration=no  nbFoundSolutions=1
0.94	     globalCpuTime=0.51
0.94	       =>  wckTime=0.64  cpuTime=0.47  mem=16M582
0.94	   
0.94	s SATISFIABLE
0.94	v 99 99 99 99 99 99 99 99 99 99 99 99 99 99 99 99 99 99 99 99 99 99 99 99 99 99 99 99 99 99 99 99 99 99 99 99 99 99 99 99 99 99 99 99 99 99 99 99 99 99 99 99 99 99 99 99 99 99 99 99 99 99 99 99 99 99 99 99 99 99 99 99 99 99 99 99 99 99 99 99 99 99 99 99 99 99 99 99 99 99 99 99 99 99 99 99 99 99 99 99 99 99 99 99 99 99 99 99 99 99 99 99 99 99 99 99 99 99 99 99 99 99 99 99 99 99 99 99 99 99 99 99 99 99 99 99 99 99 99 99 99 99 99 99 99 99 99 99 99 99 99 99 99 99 99 99 99 99 99 99 99 99 99 99 99 99 99 99 99 99 99 99 99 99 99 99 99 99 99 99 99 99 99 99 99 99 99 99 99 99 99 99 99 99 99 99 99 99 99 99 99 99 99 99 99 99 99 99 99 99 99 99 99 99 99 99 99 99 99 99 99 99 99 99 99 99 99 99 99 99 99 99 99 99 99 99 99 99 99 99 99 99 99 99 99 99 99 99 99 99 99 99 99 99 99 99 99 99 99 99 99 99 99 99 99 99 99 99 99 99 99 99 99 99 99 99 99 99 99 99 99 99 99 99 99 99 99 99 99 99 99 99 99 99 99 99 99 99 99 99 
0.94	d NODES 0
0.94	d CHECKS 2465805
0.94	   
0.94	   totalWckTime=0.719  totalCpuTime=0.51

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/node10/watcher-203929-1168165033 -o ROOT/results/node10/solver-203929-1168165033 -C 1800 -M 900 java -Xms756M -Xmx756M -XX:PermSize=10m -XX:MaxPermSize=10m -jar abscon109.jar esac.xml 1 XSax /tmp/evaluation/203929-1168165033/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.60 1.89 1.96 4/86 29088
/proc/meminfo: memFree=1523224/2055920 swapFree=4178216/4192956
[pid=29087] ppid=29085 vsize=172 CPUtime=0
/proc/29087/stat : 29087 (java) R 29085 29087 28794 0 -1 0 217 0 0 0 0 0 0 0 18 0 1 0 164898738 176128 24 18446744073709551615 134512640 134570532 4294956464 18446744073709551615 8905508 0 0 4096 0 0 0 0 17 0 0 0
/proc/29087/statm: 43 24 18 14 0 3 0

[startup+0.107545 s]
/proc/loadavg: 1.60 1.89 1.96 4/86 29088
/proc/meminfo: memFree=1523224/2055920 swapFree=4178216/4192956
[pid=29087] ppid=29085 vsize=914988 CPUtime=0.09
/proc/29087/stat : 29087 (java) R 29085 29087 28794 0 -1 0 3062 0 1 0 8 1 0 0 23 0 8 0 164898738 936947712 2808 18446744073709551615 134512640 134570532 4294956464 18446744073709551615 4294960144 0 4 0 23759 18446744073709551615 0 0 17 0 0 0
/proc/29087/statm: 228747 2808 1450 14 0 215242 0
Current children cumulated CPU time (s) 0.09
Current children cumulated vsize (KiB) 914988

[startup+0.515682 s]
/proc/loadavg: 1.60 1.89 1.96 4/86 29088
/proc/meminfo: memFree=1523224/2055920 swapFree=4178216/4192956
[pid=29087] ppid=29085 vsize=915328 CPUtime=0.5
/proc/29087/stat : 29087 (java) R 29085 29087 28794 0 -1 0 6745 0 1 0 45 5 0 0 25 0 8 0 164898738 937295872 6484 18446744073709551615 134512640 134570532 4294956464 18446744073709551615 4073468326 0 4 0 23759 18446744073709551615 0 0 17 0 0 0
/proc/29087/statm: 228832 6484 2147 14 0 215302 0
Current children cumulated CPU time (s) 0.5
Current children cumulated vsize (KiB) 915328

Child status: 0
Real time (s): 0.96882
CPU time (s): 0.940856
CPU user time (s): 0.857869
CPU system time (s): 0.082987
CPU usage (%): 97.1136
Max. virtual memory (cumulated for all children) (KiB): 915460

getrusage(RUSAGE_CHILDREN,...) data:
user time used= 0.857869
system time used= 0.082987
maximum resident set size= 0
integral shared memory size= 0
integral unshared data size= 0
integral unshared stack size= 0
page reclaims= 9097
page faults= 1
swaps= 0
block input operations= 0
block output operations= 0
messages sent= 0
messages received= 0
signals received= 0
voluntary context switches= 965
involuntary context switches= 961

runsolver used 0.002999 s user time and 0.007998 s system time

The end

Launcher Data (download as text)

Begin job on node10 on Sun Jan  7 10:17:15 UTC 2007


IDJOB= 203929
IDBENCH= 3990
FILE ID= node10/203929-1168165033

PBS_JOBID= 3478322

Free space on /tmp= 66372 MiB

BENCH NAME= HOME/pub/bench/CPAI06/domino/domino-300-100.xml
COMMAND LINE= java -Xms756M -Xmx756M -XX:PermSize=10m -XX:MaxPermSize=10m -jar abscon109.jar esac.xml 1 XSax /tmp/evaluation/203929-1168165033/unknown.xml
RUNSOLVER COMMAND LINE= runsolver  --timestamp  -w ROOT/results/node10/watcher-203929-1168165033 -o ROOT/results/node10/solver-203929-1168165033 -C 1800 -M 900  java -Xms756M -Xmx756M -XX:PermSize=10m -XX:MaxPermSize=10m -jar abscon109.jar esac.xml 1 XSax /tmp/evaluation/203929-1168165033/unknown.xml

META MD5SUM SOLVER= 9b91398c18c9fe54a6c4cfb50dadce08
MD5SUM BENCH=  eff2a61155581d1c1ba66ec540fd5989

RANDOM SEED= 356684159

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.232
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.232
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:       1523640 kB
Buffers:         54948 kB
Cached:         356540 kB
SwapCached:       2088 kB
Active:         123100 kB
Inactive:       324736 kB
HighTotal:           0 kB
HighFree:            0 kB
LowTotal:      2055920 kB
LowFree:       1523640 kB
SwapTotal:     4192956 kB
SwapFree:      4178216 kB
Dirty:            2116 kB
Writeback:           0 kB
Mapped:          49308 kB
Slab:            69232 kB
Committed_AS:  3993900 kB
PageTables:       2180 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= 66372 MiB



End job on node10 on Sun Jan  7 10:17:17 UTC 2007