Trace number 240606

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.71689 0.767431

DiagnosticValue
CHECKS30
NODES116

General information on the benchmark

Namebqwh/bqwh-15-106_glb/
bqwh-15-106-95_glb.xml
MD5SUMdd741c0af2140d21a67ff354d912215d
Bench CategoryGLOBAL (global constraints)
Best result obtained on this benchmarkSAT
Best CPU time to get the best result obtained on this benchmark0.018996
SatisfiableYES
(Un)Satisfiability was proved
Number of variables106
Number of constraints30
Maximum constraint arity8
Maximum domain size6
Number of constraints which are defined in extension0
Number of constraints which are defined in intension0
Global constraints used (with number of constraints)allDifferent(30)

Solver Data (download as text)

0.30	   
0.30	Abscon 109 (November, 2006)
0.30	   
0.30	   configuration
0.30	     name=mac.xml
0.34	   
0.34	   instance
0.34	     name=/tmp/evaluation/240606-1168085245/unknown.xml
0.37	   
0.37	   domains being loaded...
0.39	   
0.39	   variables being loaded...
0.44	     nbVariables=106  nbDomainTypes=98  minDomainSize=1  maxDomainSize=6
0.44	       =>  wckTime=0.132  cpuTime=0.1  mem=6M896
0.44	   
0.44	   constraints being loaded...
0.47	     nbConstraints=30  nbGlobalConstraints=30  nbSingletonDomainVariables=1  nbSharedBinaryRepresentations=0
0.47	     maxDegree=2  maxArity=8
0.47	       =>  wckTime=0.159  cpuTime=0.11  mem=6M896
0.50	   
0.50	   solver IterativeSystematicSolver being built... 
0.67	       =>  wckTime=0.367  cpuTime=0.26  mem=14M365
0.69	   
0.69	   preprocessing
0.69	     nbConstraintChecks=0  nbPropagations=106  nbRevisions=0  nbUselessRevisions=0  nbRemovedValues=7
0.69	     detectedInconsistency=no
0.69	       =>  wckTime=0.016  cpuTime=0.0  mem=14M365
0.73	   
0.73	   search
0.73	     run=0  nbConstraintChecks=30  nbPropagations=443  nbRevisions=0  nbUselessRevisions=0  nbAssignments=116
0.73	     nbFailedAssignments=4  nbBacktracks=6  nbVisitedNodes=122  nbRestartNogoods=0  mapSize=2  nbInferences=0
0.73	     nbTooLargeKeys=0
0.73	       =>  wckTime=0.051  cpuTime=0.02  mem=15M340
0.73	   
0.73	   global
0.73	     nbConstraintChecks=30  nbPropagations=549  nbRestartNogoods=0  solvingWckTime=0.053  solvingCpuTime=0.02
0.73	     expiredTime=no  totalExploration=no  nbFoundSolutions=1  globalCpuTime=0.33
0.73	       =>  wckTime=0.423  cpuTime=0.28  mem=15M340
0.73	   
0.73	s SATISFIABLE
0.73	v 11 5 12 3 14 2 6 10 5 14 0 7 1 3 10 1 11 12 7 4 14 9 3 11 12 13 14 5 7 11 1 13 4 3 10 1 4 2 0 7 8 10 2 9 7 14 10 3 8 14 7 9 12 8 5 4 12 7 4 2 5 8 13 4 2 14 0 11 10 8 1 14 3 6 8 4 0 12 4 3 12 6 11 14 9 9 13 10 3 11 4 1 8 5 10 12 3 1 14 8 7 10 9 14 4 1 
0.73	d NODES 116
0.73	d CHECKS 30
0.73	   
0.73	   totalWckTime=0.5  totalCpuTime=0.33

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/node5/watcher-240606-1168085245 -o ROOT/results/node5/solver-240606-1168085245 -C 1800 -M 900 java -Xms756M -Xmx756M -XX:PermSize=10m -XX:MaxPermSize=10m -jar abscon109.jar mac.xml 1 XSax /tmp/evaluation/240606-1168085245/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.21 1.73 1.83 4/93 9171
/proc/meminfo: memFree=1366280/2055920 swapFree=4192812/4192956
[pid=9170] ppid=9168 vsize=18540 CPUtime=0
/proc/9170/stat : 9170 (runsolver) R 9168 9170 8733 0 -1 4194368 17 0 0 0 0 0 0 0 20 0 1 0 137140951 18984960 279 18446744073709551615 4194304 4267372 548682068960 18446744073709551615 226913479975 0 2147483391 4096 24578 0 0 0 17 0 0 0
/proc/9170/statm: 4635 279 244 17 0 2626 0

[startup+0.107525 s]
/proc/loadavg: 1.21 1.73 1.83 4/93 9171
/proc/meminfo: memFree=1366280/2055920 swapFree=4192812/4192956
[pid=9170] ppid=9168 vsize=914988 CPUtime=0.08
/proc/9170/stat : 9170 (java) S 9168 9170 8733 0 -1 0 2997 0 1 0 7 1 0 0 24 0 8 0 137140951 936947712 2743 18446744073709551615 134512640 134570532 4294956480 18446744073709551615 4294960144 0 4 0 23759 18446744073709551615 0 0 17 0 0 0
/proc/9170/statm: 228747 2743 1427 14 0 215242 0
Current children cumulated CPU time (s) 0.08
Current children cumulated vsize (KiB) 914988

[startup+0.515573 s]
/proc/loadavg: 1.21 1.73 1.83 4/93 9171
/proc/meminfo: memFree=1366280/2055920 swapFree=4192812/4192956
[pid=9170] ppid=9168 vsize=915460 CPUtime=0.49
/proc/9170/stat : 9170 (java) R 9168 9170 8733 0 -1 0 6584 0 1 0 45 4 0 0 25 0 8 0 137140951 937431040 6322 18446744073709551615 134512640 134570532 4294956480 18446744073709551615 4152172390 0 4 0 23759 18446744073709551615 0 0 17 0 0 0
/proc/9170/statm: 228865 6322 2359 14 0 215335 0
Current children cumulated CPU time (s) 0.49
Current children cumulated vsize (KiB) 915460

Child status: 0
Real time (s): 0.767431
CPU time (s): 0.71689
CPU user time (s): 0.6539
CPU system time (s): 0.06299
CPU usage (%): 93.4143
Max. virtual memory (cumulated for all children) (KiB): 915460

getrusage(RUSAGE_CHILDREN,...) data:
user time used= 0.6539
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= 8723
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= 733
involuntary context switches= 744

runsolver used 0.003999 s user time and 0.008998 s system time

The end

Launcher Data (download as text)

Begin job on node5 on Sat Jan  6 12:07:31 UTC 2007


IDJOB= 240606
IDBENCH= 7141
FILE ID= node5/240606-1168085245

PBS_JOBID= 3476271

Free space on /tmp= 66331 MiB

BENCH NAME= HOME/pub/bench/CPAI06/bqwh/bqwh-15-106_glb/bqwh-15-106-95_glb.xml
COMMAND LINE= java -Xms756M -Xmx756M -XX:PermSize=10m -XX:MaxPermSize=10m -jar abscon109.jar mac.xml 1 XSax /tmp/evaluation/240606-1168085245/unknown.xml
RUNSOLVER COMMAND LINE= runsolver  --timestamp  -w ROOT/results/node5/watcher-240606-1168085245 -o ROOT/results/node5/solver-240606-1168085245 -C 1800 -M 900  java -Xms756M -Xmx756M -XX:PermSize=10m -XX:MaxPermSize=10m -jar abscon109.jar mac.xml 1 XSax /tmp/evaluation/240606-1168085245/unknown.xml

META MD5SUM SOLVER= 9b91398c18c9fe54a6c4cfb50dadce08
MD5SUM BENCH=  dd741c0af2140d21a67ff354d912215d

RANDOM SEED= 860792259

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.240
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.240
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:       1366624 kB
Buffers:         50644 kB
Cached:         448884 kB
SwapCached:          0 kB
Active:         151744 kB
Inactive:       450212 kB
HighTotal:           0 kB
HighFree:            0 kB
LowTotal:      2055920 kB
LowFree:       1366624 kB
SwapTotal:     4192956 kB
SwapFree:      4192812 kB
Dirty:            1748 kB
Writeback:           0 kB
Mapped:         131500 kB
Slab:            71912 kB
Committed_AS:  4045032 kB
PageTables:       2328 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= 66331 MiB



End job on node5 on Sat Jan  6 12:07:54 UTC 2007