Trace number 201918

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 ACUNSAT 0.815875 0.880507

DiagnosticValue
CHECKS3477
NODES5

General information on the benchmark

Namecomposed/composed-25-1-80/
composed-25-1-80-8_ext.xml
MD5SUMdf9fee37b400f024f0beb4d0cffbb7c8
Bench Category2-ARY-EXT (binary constraints in extension)
Best result obtained on this benchmarkUNSAT
Best CPU time to get the best result obtained on this benchmark0.026995
SatisfiableNO
(Un)Satisfiability was provedNO
Number of variables33
Number of constraints302
Maximum constraint arity2
Maximum domain size10
Number of constraints which are defined in extension302
Number of constraints which are defined in intension0
Global constraints used (with number of constraints)

Solver Data (download as text)

0.31	   
0.31	Abscon 109 (November, 2006)
0.31	   
0.31	   configuration
0.31	     name=mac.xml
0.35	   
0.35	   instance
0.35	     name=/tmp/evaluation/201918-1168072495/unknown.xml
0.38	   
0.38	   domains being loaded...
0.38	   
0.38	   variables being loaded...
0.42	     nbVariables=33  nbDomainTypes=1  minDomainSize=10  maxDomainSize=10
0.42	       =>  wckTime=0.104  cpuTime=0.09  mem=6M951
0.42	   
0.42	   relations being loaded...
0.49	   
0.49	   constraints being loaded...
0.59	     nbConstraints=302  nbRelationTypes=302  nbExtensionStructures=302  nbSharedExtensionStructures=0
0.59	     nbConflictsStructures=302  nbSharedConflictsStructures=0  nbSharedBinaryRepresentations=5462  maxDegree=23
0.59	     maxArity=2
0.59	       =>  wckTime=0.279  cpuTime=0.19  mem=9M975
0.63	   
0.63	   solver IterativeSystematicSolver being built... 
0.79	       =>  wckTime=0.475  cpuTime=0.32  mem=13M547
0.80	   
0.80	   preprocessing
0.80	     nbConstraintChecks=245  nbPropagations=36  nbRevisions=26  nbUselessRevisions=20  nbRemovedValues=7
0.80	     detectedInconsistency=no
0.80	       =>  wckTime=0.0050  cpuTime=0.01  mem=13M547
0.82	   
0.82	   search
0.82	     run=0  nbConstraintChecks=3232  nbPropagations=86  nbRevisions=486  nbUselessRevisions=304  nbAssignments=5
0.82	     nbFailedAssignments=5  nbBacktracks=1  nbVisitedNodes=11  nbRestartNogoods=0  mapSize=0  nbInferences=0
0.82	     nbTooLargeKeys=0
0.82	       =>  wckTime=0.029  cpuTime=0.02  mem=14M538
0.82	   
0.82	   global
0.82	     nbConstraintChecks=3477  nbPropagations=122  nbRevisions=512  nbUselessRevisions=324  nbRestartNogoods=0
0.82	     solvingWckTime=0.032  solvingCpuTime=0.02  expiredTime=no  totalExploration=yes  nbFoundSolutions=0
0.82	     globalCpuTime=0.4
0.82	       =>  wckTime=0.508  cpuTime=0.34  mem=14M538
0.83	   
0.83	s UNSATISFIABLE
0.83	d NODES 5
0.83	d CHECKS 3477
0.83	   
0.83	   totalWckTime=0.589  totalCpuTime=0.4

Verifier Data (download as text)

No possible verification on an UNSAT instance

Watcher Data (download as text)

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

command line: runsolver --timestamp -w ROOT/results/node15/watcher-201918-1168072495 -o ROOT/results/node15/solver-201918-1168072495 -C 1800 -M 900 java -Xms756M -Xmx756M -XX:PermSize=10m -XX:MaxPermSize=10m -jar abscon109.jar mac.xml 1 XSax /tmp/evaluation/201918-1168072495/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.95 1.97 4/93 13403
/proc/meminfo: memFree=1025896/2055920 swapFree=4174172/4192956
[pid=13402] ppid=13400 vsize=1784 CPUtime=0
/proc/13402/stat : 13402 (java) R 13400 13402 13223 0 -1 0 169 0 0 0 0 0 0 0 19 0 1 0 155644528 1826816 140 18446744073709551615 134512640 134570532 4294956624 18446744073709551615 4294960144 0 2147483391 4096 0 0 0 0 17 1 0 0
/proc/13402/statm: 446 140 106 14 0 91 0

[startup+0.10901 s]
/proc/loadavg: 1.80 1.95 1.97 4/93 13403
/proc/meminfo: memFree=1025896/2055920 swapFree=4174172/4192956
[pid=13402] ppid=13400 vsize=914988 CPUtime=0.09
/proc/13402/stat : 13402 (java) R 13400 13402 13223 0 -1 0 3005 0 1 0 7 2 0 0 17 0 8 0 155644528 936947712 2751 18446744073709551615 134512640 134570532 4294956464 18446744073709551615 4155476519 0 4 0 23759 18446744073709551615 0 0 17 1 0 0
/proc/13402/statm: 228747 2751 1430 14 0 215242 0
Current children cumulated CPU time (s) 0.09
Current children cumulated vsize (KiB) 914988

[startup+0.51708 s]
/proc/loadavg: 1.80 1.95 1.97 4/93 13403
/proc/meminfo: memFree=1025896/2055920 swapFree=4174172/4192956
[pid=13402] ppid=13400 vsize=915328 CPUtime=0.48
/proc/13402/stat : 13402 (java) R 13400 13402 13223 0 -1 0 6311 0 1 0 45 3 0 0 19 0 8 0 155644528 937295872 6050 18446744073709551615 134512640 134570532 4294956464 18446744073709551615 4072917011 0 4 0 23759 18446744073709551615 0 0 17 1 0 0
/proc/13402/statm: 228832 6050 2138 14 0 215302 0
Current children cumulated CPU time (s) 0.48
Current children cumulated vsize (KiB) 915328

Child status: 0
Real time (s): 0.880507
CPU time (s): 0.815875
CPU user time (s): 0.751885
CPU system time (s): 0.06399
CPU usage (%): 92.6597
Max. virtual memory (cumulated for all children) (KiB): 915456

getrusage(RUSAGE_CHILDREN,...) data:
user time used= 0.751885
system time used= 0.06399
maximum resident set size= 0
integral shared memory size= 0
integral unshared data size= 0
integral unshared stack size= 0
page reclaims= 8534
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= 718
involuntary context switches= 801

runsolver used 0.003999 s user time and 0.007998 s system time

The end

Launcher Data (download as text)

Begin job on node15 on Sat Jan  6 08:34:57 UTC 2007


IDJOB= 201918
IDBENCH= 3792
FILE ID= node15/201918-1168072495

PBS_JOBID= 3475750

Free space on /tmp= 66283 MiB

BENCH NAME= HOME/pub/bench/CPAI06/composed/composed-25-1-80/composed-25-1-80-8_ext.xml
COMMAND LINE= java -Xms756M -Xmx756M -XX:PermSize=10m -XX:MaxPermSize=10m -jar abscon109.jar mac.xml 1 XSax /tmp/evaluation/201918-1168072495/unknown.xml
RUNSOLVER COMMAND LINE= runsolver  --timestamp  -w ROOT/results/node15/watcher-201918-1168072495 -o ROOT/results/node15/solver-201918-1168072495 -C 1800 -M 900  java -Xms756M -Xmx756M -XX:PermSize=10m -XX:MaxPermSize=10m -jar abscon109.jar mac.xml 1 XSax /tmp/evaluation/201918-1168072495/unknown.xml

META MD5SUM SOLVER= 9b91398c18c9fe54a6c4cfb50dadce08
MD5SUM BENCH=  df9fee37b400f024f0beb4d0cffbb7c8

RANDOM SEED= 926113446

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.276
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.276
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:       1026312 kB
Buffers:         85084 kB
Cached:         769212 kB
SwapCached:       7128 kB
Active:         369584 kB
Inactive:       556444 kB
HighTotal:           0 kB
HighFree:            0 kB
LowTotal:      2055920 kB
LowFree:       1026312 kB
SwapTotal:     4192956 kB
SwapFree:      4174172 kB
Dirty:            2044 kB
Writeback:           0 kB
Mapped:          90392 kB
Slab:            87944 kB
Committed_AS:  4914668 kB
PageTables:       2516 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= 66283 MiB



End job on node15 on Sat Jan  6 08:34:59 UTC 2007