Trace number 2669271

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. The first timestamp (if present) is estimated CPU time. The last timestamp is wall clock 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 NameAnswerobjective functionCPU timeWall clock time
PB/CT 0.1OPT89 0.086985 0.086614

General information on the benchmark

Namenormalized-PB06/OPT-SMALLINT/submitted-PB05/
manquinho/primes-dimacs-cnf/normalized-jnh7.opb
MD5SUM6d6b2f4631faf3412de4fc57bbefcdf3
Bench CategoryOPT-SMALLINT (optimisation, small integers)
Best result obtained on this benchmarkOPT
Best value of the objective obtained on this benchmark89
Best CPU time to get the best result obtained on this benchmark0.084986
Has Objective FunctionYES
SatisfiableYES
(Un)Satisfiability was provedYES
Best value of the objective function 89
Optimality of the best value was proved YES
Number of variables200
Total number of constraints950
Number of constraints which are clauses950
Number of constraints which are cardinality constraints (but not clauses)0
Number of constraints which are nor clauses,nor cardinality constraints0
Minimum length of a constraint2
Maximum length of a constraint10
Number of terms in the objective function 200
Biggest coefficient in the objective function 1
Number of bits for the biggest coefficient in the objective function 1
Sum of the numbers in the objective function 200
Number of bits of the sum of numbers in the objective function 8
Biggest number in a constraint 1
Number of bits of the biggest number in a constraint 1
Biggest sum of numbers in a constraint 200
Number of bits of the biggest sum of numbers8
Number of products (including duplicates)0
Sum of products size (including duplicates)0
Number of different products0
Sum of products size0

Quality of the solution as a function of time


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

Solver Data 

0.00/0.00	c PB/CT 0.1 http://www.residual.se/pbct
0.00/0.00	c Based on OpenSMT/CT 20091015
0.00/0.01	c constraints 0/0 clauses 950/0 units 0
0.00/0.01	c vars 200
0.00/0.01	c objective 200 + 0
0.03/0.05	c 0.045993 6.38281 7 42
0.03/0.05	o 94
0.03/0.05	c 0.046992 6.53906 9 56
0.03/0.05	o 93
0.03/0.05	c 0.049992 6.53906 54 119
0.03/0.05	o 92
0.03/0.05	c 0.053991 6.53906 96 176
0.03/0.05	o 91
0.03/0.05	c 0.054991 6.53906 102 194
0.03/0.05	o 90
0.03/0.06	c 0.055991 6.53906 113 220
0.03/0.06	o 89
0.03/0.07	c 0.068989 6.53906 39 448
0.03/0.07	s OPTIMUM FOUND
0.03/0.07	v -x1 x2 -x3 x4 -x5 x6 x7 -x8 -x9 -x10 -x11 -x12 x13 -x14 -x15 x16 -x17 -x18 -x19 x20 -x21 -x22 -x23 x24 -x25 -x26 x27 -x28 -x29 x30 x31 -x32 x33 -x34 -x35 x36 -x37 x38 -x39 x40 -x41 x42 -x43 x44 x45 -x46 -x47 -x48 x49 -x50 x51 -x52 -x53 -x54 -x55 x56 x57 -x58 -x59 x60 x61 -x62 x63 -x64 -x65 x66 x67 -x68 x69 -x70 x71 -x72 -x73 x74 x75 -x76 -x77 x78 x79 -x80 x81 -x82 x83 -x84 -x85 x86 x87 -x88 -x89 x90 -x91 x92 -x93 x94 -x95 x96 x97 -x98 -x99 x100 x101 -x102 x103 -x104 x105 -x106 x107 -x108 x109 -x110 x111 -x112 x113 -x114 -x115 x116 -x117 x118 x119 -x120 -x121 x122 x123 -x124 x125 -x126 -x127 x128 x129 -x130 x131 -x132 -x133 x134 -x135 x136 -x137 x138 x139 -x140 x141 -x142 -x143 x144 x145 -x146 x147 -x148 x149 -x150 x151 -x152 x153 -x154 -x155 -x156 x157 -x158 x159 -x160 -x161 x162 x163 -x164 x165 -x166 -x167 x168 x169 -x170 -x171 x172 x173 -x174 x175 -x176 -x177 x178 x179 -x180 -x181 x182 x183 -x184 -x185 -x186 x187 -x188 x189 -x190 x191 -x192 -x193 x194 x195 -x196 -x197 -x198 -x199 -x200

Verifier Data 

OK	89

Watcher Data 

runsolver version 3.2.9 (svn:492) (c) roussel@cril.univ-artois.fr

command line: BIN/runsolver --timestamp -w /tmp/evaluation-result-2669271-1276466317/watcher-2669271-1276466317 -o /tmp/evaluation-result-2669271-1276466317/solver-2669271-1276466317 -C 1800 -W 2000 -M 1800 HOME/pbct --model HOME/instance-2669271-1276466317.opb 

Enforcing CPUTime limit (soft limit, will send SIGTERM then SIGKILL): 1800 seconds
Enforcing CPUTime limit (hard limit, will send SIGXCPU): 1830 seconds
Enforcing wall clock limit (soft limit, will send SIGTERM then SIGKILL): 2000 seconds
Enforcing VSIZE limit (soft limit, will send SIGTERM then SIGKILL): 1843200 KiB
Enforcing VSIZE limit (hard limit, stack expansion will fail with SIGSEGV, brk() and mmap() will return ENOMEM): 1894400 KiB
Current StackSize limit: 10240 KiB


[startup+0 s]
/proc/loadavg: 0.85 0.95 0.98 3/106 27916
/proc/meminfo: memFree=1791024/2059040 swapFree=4136456/4192956
[pid=27916] ppid=27914 vsize=2208 CPUtime=0
/proc/27916/stat : 27916 (pbct) R 27914 27916 26699 0 -1 4202496 259 0 0 0 0 0 0 0 20 0 1 0 22235737 2260992 181 1992294400 134512640 136485738 4290217488 18446744073709551615 135850441 0 0 4096 0 0 0 0 17 1 0 0 0
/proc/27916/statm: 552 181 156 482 0 68 0

[startup+0.041626 s]
/proc/loadavg: 0.85 0.95 0.98 3/106 27916
/proc/meminfo: memFree=1791024/2059040 swapFree=4136456/4192956
[pid=27916] ppid=27914 vsize=6396 CPUtime=0.03
/proc/27916/stat : 27916 (pbct) R 27914 27916 26699 0 -1 4202496 1300 0 0 0 3 0 0 0 20 0 1 0 22235737 6549504 1222 1992294400 134512640 136485738 4290217488 18446744073709551615 135849325 0 0 4096 16387 0 0 0 17 1 0 0 0
/proc/27916/statm: 1599 1223 210 482 0 1115 0
Current children cumulated CPU time (s) 0.03
Current children cumulated vsize (KiB) 6396

Solver just ended. Dumping a history of the last processes samples

[startup+0.041626 s]
/proc/loadavg: 0.85 0.95 0.98 3/106 27916
/proc/meminfo: memFree=1791024/2059040 swapFree=4136456/4192956
[pid=27916] ppid=27914 vsize=6396 CPUtime=0.03
/proc/27916/stat : 27916 (pbct) R 27914 27916 26699 0 -1 4202496 1300 0 0 0 3 0 0 0 20 0 1 0 22235737 6549504 1222 1992294400 134512640 136485738 4290217488 18446744073709551615 135849325 0 0 4096 16387 0 0 0 17 1 0 0 0
/proc/27916/statm: 1599 1223 210 482 0 1115 0
Current children cumulated CPU time (s) 0.03
Current children cumulated vsize (KiB) 6396

Child status: 0
Real time (s): 0.086614
CPU time (s): 0.086985
CPU user time (s): 0.078987
CPU system time (s): 0.007998
CPU usage (%): 100.428
Max. virtual memory (cumulated for all children) (KiB): 6396

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

runsolver used 0.001999 second user time and 0.011998 second system time

The end

Launcher Data 

Begin job on node001 at 2010-06-13 23:58:37
IDJOB=2669271
IDBENCH=2184
IDSOLVER=1170
FILE ID=node001/2669271-1276466317
PBS_JOBID= 11173348
Free space on /tmp= 62392 MiB

SOLVER NAME= PB/CT 0.1
BENCH NAME= PB06//final/normalized-PB06/OPT-SMALLINT/submitted-PB05/manquinho/primes-dimacs-cnf/normalized-jnh7.opb
COMMAND LINE= HOME/pbct --model BENCHNAME
RUNSOLVER COMMAND LINE= BIN/runsolver --timestamp -w /tmp/evaluation-result-2669271-1276466317/watcher-2669271-1276466317 -o /tmp/evaluation-result-2669271-1276466317/solver-2669271-1276466317 -C 1800 -W 2000 -M 1800  HOME/pbct --model HOME/instance-2669271-1276466317.opb

TIME LIMIT= 1800 seconds
MEMORY LIMIT= 1800 MiB
MAX NB THREAD= 0

MD5SUM BENCH= 6d6b2f4631faf3412de4fc57bbefcdf3
RANDOM SEED=690747989

node001.alineos.net Linux 2.6.18-164.el5 #1 SMP Thu Sep 3 03:28:30 EDT 2009

/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.202
cache size	: 2048 KB
physical id	: 0
siblings	: 1
core id		: 0
cpu cores	: 1
apicid		: 0
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 constant_tsc pni monitor ds_cpl cid cx16 xtpr
bogomips	: 6000.40
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.202
cache size	: 2048 KB
physical id	: 3
siblings	: 1
core id		: 0
cpu cores	: 1
apicid		: 6
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 constant_tsc pni monitor ds_cpl cid cx16 xtpr
bogomips	: 5599.46
clflush size	: 64
cache_alignment	: 128
address sizes	: 36 bits physical, 48 bits virtual
power management:


/proc/meminfo:
MemTotal:      2059040 kB
MemFree:       1791544 kB
Buffers:         47768 kB
Cached:         140432 kB
SwapCached:       9528 kB
Active:          95980 kB
Inactive:       104844 kB
HighTotal:           0 kB
HighFree:            0 kB
LowTotal:      2059040 kB
LowFree:       1791544 kB
SwapTotal:     4192956 kB
SwapFree:      4136456 kB
Dirty:            2096 kB
Writeback:           0 kB
AnonPages:       11068 kB
Mapped:           9300 kB
Slab:            44828 kB
PageTables:       4044 kB
NFS_Unstable:        0 kB
Bounce:              0 kB
CommitLimit:   5222476 kB
Committed_AS:   180952 kB
VmallocTotal: 34359738367 kB
VmallocUsed:    264948 kB
VmallocChunk: 34359471699 kB
HugePages_Total:     0
HugePages_Free:      0
HugePages_Rsvd:      0
Hugepagesize:     2048 kB

Free space on /tmp at the end= 62388 MiB
End job on node001 at 2010-06-13 23:58:37