Trace number 278884

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
AbsconMax 109 EPFCSAT 0.773881 0.862148

General information on the benchmark

NameMaxCSP/kbtree/kbtree-5-2-4-5/kbtree-5-2-4-5-10/
kbtree-5-2-4-5-10-11_ext.xml
MD5SUMdebf20c9c3a9d1634dfc0a3e3d366fb8
Bench Category2-ARY-EXT (binary constraints in extension)
Best result obtained on this benchmarkSAT
Best Number of satisfied constraints211
Best CPU time to get the best result obtained on this benchmark0.079987
SatisfiableYES
(Un)Satisfiability was proved
Number of variables62
Number of constraints211
Maximum constraint arity2
Maximum domain size5
Number of constraints which are defined in extension211
Number of constraints which are defined in intension0
Global constraints used (with number of constraints)

Quality of the solution as a function of time


Download the above graph as a PDF file / as an EPS file

Solver Data (download as text)

0.36	   
0.36	Abscon 109 (November, 2006)
0.36	   
0.36	   configuration
0.36	     name=epfc.xml
0.39	   
0.39	   instance
0.39	     name=/tmp/evaluation/278884-1169289445/unknown.xml
0.42	   
0.42	   domains being loaded...
0.43	   
0.43	   variables being loaded...
0.47	     nbVariables=62  nbDomainTypes=1  minDomainSize=5  maxDomainSize=5
0.47	       =>  wckTime=0.104  cpuTime=0.09  mem=6M887
0.47	   
0.47	   relations being loaded...
0.50	   
0.50	   constraints being loaded...
0.58	     nbConstraints=211  nbRelationTypes=152  nbExtensionStructures=152  nbSharedExtensionStructures=59
0.58	     nbConflictsStructures=152  nbSharedConflictsStructures=59  nbSharedBinaryRepresentations=1504  maxDegree=17
0.58	     maxArity=2
0.58	       =>  wckTime=0.218  cpuTime=0.16  mem=8M837
0.62	   
0.62	   solver LocalSearchSolver being built... 
0.66	       =>  wckTime=0.299  cpuTime=0.2  mem=5M547
0.66	
0.66	s SATISFIABLE
0.66	o 205
0.66	c 6
0.67	o 206
0.67	c 5
0.67	o 207
0.67	c 4
0.67	o 208
0.67	c 3
0.67	o 209
0.67	c 2
0.67	o 210
0.67	c 1
0.67	   
0.67	   search
0.67	     run=0  nbConstraintChecks=1484  nbAssignments=6
0.67	       =>  wckTime=0.0080  cpuTime=0.0  mem=5M547
0.67	   
0.67	   global
0.67	     nbConstraintChecks=1484  nbValidityChecks=0  nbPropagations=0  nbRevisions=0  nbUselessRevisions=0
0.67	     solvingWckTime=0.0070  solvingCpuTime=0.0  expiredTime=no  totalExploration=no  nbFoundSolutions=0
0.67	     globalCpuTime=0.25
0.67	       =>  wckTime=0.307  cpuTime=0.2  mem=5M547
0.67	   
0.67	   solver IterativeSystematicSolver being built... 
0.80	       =>  wckTime=0.436  cpuTime=0.32  mem=16M431
0.84	o 211
0.84	c 0
0.84	   
0.84	   preprocessing
0.84	     nbConstraintChecks=26070  nbPropagations=0  nbRevisions=0  nbUselessRevisions=0  nbRemovedValues=0
0.84	     detectedInconsistency=yes
0.84	       =>  wckTime=0.042  cpuTime=0.02  mem=16M431
0.84	   
0.84	   global
0.84	     nbConstraintChecks=26070  nbRestartNogoods=0  solvingWckTime=0.044  solvingCpuTime=0.02  expiredTime=no
0.84	     totalExploration=yes  nbFoundSolutions=0  globalCpuTime=0.39
0.84	       =>  wckTime=0.482  cpuTime=0.34  mem=16M431
0.85	
0.85	s OPTIMUM FOUND
0.85	v 0 0 0 0 0 1 0 1 1 0 0 0 0 1 0 0 0 0 0 0 0 1 1 0 1 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 1 0 0 0 1 0 0 0 0 0 0 0 0 0 0 1 0 
0.85	   
0.85	   totalWckTime=0.557  totalCpuTime=0.4

Verifier Data (download as text)

0 unsatisfied constraints, 211 satisfied constraints

Watcher Data (download as text)

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

command line: runsolver --timestamp -w ROOT/results/node38/watcher-278884-1169289445 -o ROOT/results/node38/solver-278884-1169289445 -C 2400 -M 900 java -Xms756M -Xmx756M -XX:PermSize=10m -XX:MaxPermSize=10m -jar abscon109.jar epfc.xml 1 XSax /tmp/evaluation/278884-1169289445/unknown.xml 

Enforcing CPUTime limit (soft limit, will send SIGTERM then SIGKILL): 2400 seconds
Enforcing CPUTime limit (hard limit, will send SIGXCPU): 2430 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: 0.85 1.13 1.50 3/65 29798
/proc/meminfo: memFree=1456648/2055920 swapFree=4192812/4192956
[pid=29797] ppid=29795 vsize=172 CPUtime=0
/proc/29797/stat : 29797 (java) R 29795 29797 29143 0 -1 0 217 0 0 0 0 0 0 0 19 0 1 0 277344112 176128 24 18446744073709551615 134512640 134570532 4294956480 18446744073709551615 8605995 0 0 4096 0 0 0 0 17 1 0 0
/proc/29797/statm: 43 24 18 14 0 3 0

[startup+0.10407 s]
/proc/loadavg: 0.85 1.13 1.50 3/65 29798
/proc/meminfo: memFree=1456648/2055920 swapFree=4192812/4192956
[pid=29797] ppid=29795 vsize=914100 CPUtime=0.08
/proc/29797/stat : 29797 (java) D 29795 29797 29143 0 -1 0 2923 0 1 0 7 1 0 0 17 0 8 0 277344112 936038400 2669 18446744073709551615 134512640 134570532 4294956480 18446744073709551615 4294960144 0 2147483391 0 23759 18446744073709551615 0 0 17 0 0 0
/proc/29797/statm: 228525 2669 1396 14 0 215426 0
Current children cumulated CPU time (s) 0.08
Current children cumulated vsize (KiB) 914100

[startup+0.512147 s]
/proc/loadavg: 0.85 1.13 1.50 3/65 29798
/proc/meminfo: memFree=1456648/2055920 swapFree=4192812/4192956
[pid=29797] ppid=29795 vsize=915956 CPUtime=0.43
/proc/29797/stat : 29797 (java) R 29795 29797 29143 0 -1 0 6226 0 1 0 39 4 0 0 16 0 8 0 277344112 937938944 5965 18446744073709551615 134512640 134570532 4294956480 18446744073709551615 4152819938 0 4 0 23759 18446744073709551615 0 0 17 1 0 0
/proc/29797/statm: 228989 5965 2143 14 0 215459 0
Current children cumulated CPU time (s) 0.43
Current children cumulated vsize (KiB) 915956

Child status: 0
Real time (s): 0.862148
CPU time (s): 0.773881
CPU user time (s): 0.697893
CPU system time (s): 0.075988
CPU usage (%): 89.762
Max. virtual memory (cumulated for all children) (KiB): 916208

getrusage(RUSAGE_CHILDREN,...) data:
user time used= 0.697893
system time used= 0.075988
maximum resident set size= 0
integral shared memory size= 0
integral unshared data size= 0
integral unshared stack size= 0
page reclaims= 9025
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= 550
involuntary context switches= 54

runsolver used 0.003999 s user time and 0.007998 s system time

The end

Launcher Data (download as text)

Begin job on node38 on Sat Jan 20 10:37:25 UTC 2007


IDJOB= 278884
IDBENCH= 9051
IDSOLVER= 68
FILE ID= node38/278884-1169289445

PBS_JOBID= 3609680

Free space on /tmp= 66563 MiB

SOLVER NAME= AbsconMax 109 EPFC
BENCH NAME= HOME/pub/bench/CPAI06/MaxCSP/kbtree/kbtree-5-2-4-5/kbtree-5-2-4-5-10/kbtree-5-2-4-5-10-11_ext.xml
COMMAND LINE= java -Xms756M -Xmx756M -XX:PermSize=10m -XX:MaxPermSize=10m -jar abscon109.jar epfc.xml 1 XSax /tmp/evaluation/278884-1169289445/unknown.xml
RUNSOLVER COMMAND LINE= runsolver  --timestamp  -w ROOT/results/node38/watcher-278884-1169289445 -o ROOT/results/node38/solver-278884-1169289445 -C 2400 -M 900  java -Xms756M -Xmx756M -XX:PermSize=10m -XX:MaxPermSize=10m -jar abscon109.jar epfc.xml 1 XSax /tmp/evaluation/278884-1169289445/unknown.xml

META MD5SUM SOLVER= 9b91398c18c9fe54a6c4cfb50dadce08
MD5SUM BENCH=  debf20c9c3a9d1634dfc0a3e3d366fb8

RANDOM SEED= 381300070

TIME LIMIT= 2400 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.267
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.267
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:       1457000 kB
Buffers:         37744 kB
Cached:         474704 kB
SwapCached:          0 kB
Active:         129256 kB
Inactive:       398568 kB
HighTotal:           0 kB
HighFree:            0 kB
LowTotal:      2055920 kB
LowFree:       1457000 kB
SwapTotal:     4192956 kB
SwapFree:      4192812 kB
Dirty:            2004 kB
Writeback:           0 kB
Mapped:          25556 kB
Slab:            57052 kB
Committed_AS:  5274388 kB
PageTables:       1468 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= 66563 MiB



End job on node38 on Sat Jan 20 10:37:26 UTC 2007