Trace number 204074

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 ACSAT 0.768882 0.912252

DiagnosticValue
CHECKS821605
NODES100

General information on the benchmark

Namedomino/
domino-100-100.xml
MD5SUMfe5d3a596c95f9421040a43fb0a74448
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.021996
SatisfiableYES
(Un)Satisfiability was provedYES
Number of variables100
Number of constraints100
Maximum constraint arity2
Maximum domain size100
Number of constraints which are defined in extension0
Number of constraints which are defined in intension100
Global constraints used (with number of constraints)

Solver Data (download as text)

0.37	   
0.37	Abscon 109 (November, 2006)
0.37	   
0.37	   configuration
0.37	     name=mac.xml
0.40	   
0.40	   instance
0.40	     name=/tmp/evaluation/204074-1168073243/unknown.xml
0.43	   
0.43	   domains being loaded...
0.43	   
0.43	   variables being loaded...
0.47	     nbVariables=100  nbDomainTypes=1  minDomainSize=100  maxDomainSize=100
0.47	       =>  wckTime=0.105  cpuTime=0.1  mem=7M927
0.47	   
0.47	   predicates being loaded...
0.48	   
0.48	   constraints being loaded...
0.57	     nbConstraints=100  nbConvertedConstraints=100  nbConvertConstraintsChecks=20000  nbExtensionStructures=2
0.57	     nbSharedExtensionStructures=98  nbConflictsStructures=2  nbSharedConflictsStructures=98
0.57	     nbSharedBinaryRepresentations=298  maxDegree=2  maxArity=2
0.57	       =>  wckTime=0.201  cpuTime=0.16  mem=8M902
0.61	   
0.61	   solver IterativeSystematicSolver being built... 
0.76	       =>  wckTime=0.395  cpuTime=0.28  mem=14M533
0.82	   
0.82	   preprocessing
0.82	     nbConstraintChecks=821505  nbPropagations=9901  nbRevisions=10000  nbUselessRevisions=100  nbRemovedValues=9900
0.82	     detectedInconsistency=no
0.82	       =>  wckTime=0.055  cpuTime=0.04  mem=14M533
0.85	   
0.85	   search
0.85	     run=0  nbConstraintChecks=100  nbPropagations=9901  nbRevisions=10000  nbUselessRevisions=100  nbAssignments=100
0.85	     nbFailedAssignments=0  nbBacktracks=0  nbVisitedNodes=101  nbRestartNogoods=0  mapSize=0  nbInferences=0
0.85	     nbTooLargeKeys=0
0.85	       =>  wckTime=0.078  cpuTime=0.05  mem=14M533
0.85	   
0.85	   global
0.85	     nbConstraintChecks=821605  nbPropagations=19802  nbRevisions=20000  nbUselessRevisions=200  nbRestartNogoods=0
0.85	     solvingWckTime=0.081  solvingCpuTime=0.05  expiredTime=no  totalExploration=no  nbFoundSolutions=1
0.85	     globalCpuTime=0.39
0.85	       =>  wckTime=0.479  cpuTime=0.34  mem=14M533
0.85	   
0.85	s SATISFIABLE
0.85	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 
0.85	d NODES 100
0.85	d CHECKS 821605
0.85	   
0.85	   totalWckTime=0.555  totalCpuTime=0.39

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/node9/watcher-204074-1168073243 -o ROOT/results/node9/solver-204074-1168073243 -C 1800 -M 900 java -Xms756M -Xmx756M -XX:PermSize=10m -XX:MaxPermSize=10m -jar abscon109.jar mac.xml 1 XSax /tmp/evaluation/204074-1168073243/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.88 1.90 3/93 15623
/proc/meminfo: memFree=1112736/2055920 swapFree=4191880/4192956
[pid=15622] ppid=15620 vsize=1784 CPUtime=0
/proc/15622/stat : 15622 (java) R 15620 15622 15331 0 -1 0 342 0 0 0 0 0 0 0 18 0 1 0 155719569 1826816 136 18446744073709551615 134512640 134570532 4294956464 18446744073709551615 4294960144 0 0 4096 0 0 0 0 17 1 0 0
/proc/15622/statm: 446 140 106 14 0 91 0

[startup+0.102874 s]
/proc/loadavg: 1.60 1.88 1.90 3/93 15623
/proc/meminfo: memFree=1112736/2055920 swapFree=4191880/4192956
[pid=15622] ppid=15620 vsize=913228 CPUtime=0.08
/proc/15622/stat : 15622 (java) D 15620 15622 15331 0 -1 0 2920 0 1 0 7 1 0 0 24 0 8 0 155719569 935145472 2666 18446744073709551615 134512640 134570532 4294956464 18446744073709551615 4294960144 0 2147483391 0 23759 18446744073709551615 0 0 17 0 0 0
/proc/15622/statm: 228307 2666 1396 14 0 215208 0
Current children cumulated CPU time (s) 0.08
Current children cumulated vsize (KiB) 913228

[startup+0.510919 s]
/proc/loadavg: 1.60 1.88 1.90 3/93 15623
/proc/meminfo: memFree=1112736/2055920 swapFree=4191880/4192956
[pid=15622] ppid=15620 vsize=915328 CPUtime=0.41
/proc/15622/stat : 15622 (java) R 15620 15622 15331 0 -1 0 6274 0 1 0 38 3 0 0 19 0 8 0 155719569 937295872 6013 18446744073709551615 134512640 134570532 4294956464 18446744073709551615 4072935154 0 4 0 23759 18446744073709551615 0 0 17 0 0 0
/proc/15622/statm: 228832 6013 2145 14 0 215302 0
Current children cumulated CPU time (s) 0.41
Current children cumulated vsize (KiB) 915328

Child status: 0
Real time (s): 0.912252
CPU time (s): 0.768882
CPU user time (s): 0.705892
CPU system time (s): 0.06299
CPU usage (%): 84.2839
Max. virtual memory (cumulated for all children) (KiB): 915460

getrusage(RUSAGE_CHILDREN,...) data:
user time used= 0.705892
system time used= 0.06299
maximum resident set size= 0
integral shared memory size= 0
integral unshared data size= 0
integral unshared stack size= 0
page reclaims= 8576
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= 759
involuntary context switches= 840

runsolver used 0.002999 s user time and 0.008998 s system time

The end

Launcher Data (download as text)

Begin job on node9 on Sat Jan  6 08:47:23 UTC 2007


IDJOB= 204074
IDBENCH= 3999
FILE ID= node9/204074-1168073243

PBS_JOBID= 3475759

Free space on /tmp= 66537 MiB

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

META MD5SUM SOLVER= 9b91398c18c9fe54a6c4cfb50dadce08
MD5SUM BENCH=  fe5d3a596c95f9421040a43fb0a74448

RANDOM SEED= 86964374

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.231
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.231
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:       1113408 kB
Buffers:         83316 kB
Cached:         521412 kB
SwapCached:        268 kB
Active:         498408 kB
Inactive:       342016 kB
HighTotal:           0 kB
HighFree:            0 kB
LowTotal:      2055920 kB
LowFree:       1113408 kB
SwapTotal:     4192956 kB
SwapFree:      4191880 kB
Dirty:            1848 kB
Writeback:           0 kB
Mapped:         257488 kB
Slab:            86464 kB
Committed_AS:  4704388 kB
PageTables:       2704 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= 66537 MiB



End job on node9 on Sat Jan  6 08:47:25 UTC 2007