Trace number 2667943

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.1OPT3 1.62575 1.62659

General information on the benchmark

Namenormalized-PB07/OPT-SMALLINT-NLC/submittedPB07/roussel/
factor-mod-B/factor-mod-size=9-P0=271-P1=293-B.opb
MD5SUM2e3c7287841521f4043e8a0d4ae495d6
Bench CategoryOPT-SMALLINT-NLC (optimisation, small integers, non linear constraints)
Best result obtained on this benchmarkOPT
Best value of the objective obtained on this benchmark3
Best CPU time to get the best result obtained on this benchmark0.072988
Has Objective FunctionYES
SatisfiableYES
(Un)Satisfiability was provedYES
Best value of the objective function 3
Optimality of the best value was proved YES
Number of variables27
Total number of constraints3
Number of constraints which are clauses0
Number of constraints which are cardinality constraints (but not clauses)0
Number of constraints which are nor clauses,nor cardinality constraints3
Minimum length of a constraint9
Maximum length of a constraint90
Number of terms in the objective function 9
Biggest coefficient in the objective function 256
Number of bits for the biggest coefficient in the objective function 9
Sum of the numbers in the objective function 511
Number of bits of the sum of numbers in the objective function 9
Biggest number in a constraint 131072
Number of bits of the biggest number in a constraint 18
Biggest sum of numbers in a constraint 522796
Number of bits of the biggest sum of numbers19
Number of products (including duplicates)81
Sum of products size (including duplicates)162
Number of different products81
Sum of products size162

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.00	c constraints 82/0 clauses 83/0 units 0
0.00/0.00	c vars 27
0.00/0.00	c objective 9 + 0
0.89/0.95	c 0.85387 5.72656 881 19080
0.89/0.95	o 185
1.59/1.61	c 1.44478 5.72656 433 36286
1.59/1.61	o 3
1.59/1.62	c 1.44678 5.72656 277 36347
1.59/1.62	s OPTIMUM FOUND
1.59/1.62	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

Verifier Data

OK	3

Watcher Data

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

command line: BIN/runsolver --timestamp -w /tmp/evaluation-result-2667943-1276649422/watcher-2667943-1276649422 -o /tmp/evaluation-result-2667943-1276649422/solver-2667943-1276649422 -C 1800 -W 2000 -M 1800 HOME/pbct --model HOME/instance-2667943-1276649422.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: 1.16 1.04 1.01 3/106 4642
/proc/meminfo: memFree=1849864/2059040 swapFree=4140244/4192956
[pid=4642] ppid=4640 vsize=3508 CPUtime=0
/proc/4642/stat : 4642 (pbct) R 4640 4642 3853 0 -1 4202496 576 0 0 0 0 0 0 0 20 0 1 0 40546161 3592192 498 1992294400 134512640 136485738 4288566656 18446744073709551615 135850441 0 0 4096 16387 0 0 0 17 1 0 0 0
/proc/4642/statm: 877 500 198 482 0 393 0

[startup+0.089683 s]
/proc/loadavg: 1.16 1.04 1.01 3/106 4642
/proc/meminfo: memFree=1849864/2059040 swapFree=4140244/4192956
[pid=4642] ppid=4640 vsize=5608 CPUtime=0.08
/proc/4642/stat : 4642 (pbct) R 4640 4642 3853 0 -1 4202496 1106 0 0 0 8 0 0 0 20 0 1 0 40546161 5742592 1028 1992294400 134512640 136485738 4288566656 18446744073709551615 135913329 0 0 4096 16387 0 0 0 17 1 0 0 0
/proc/4642/statm: 1402 1028 226 482 0 918 0
Current children cumulated CPU time (s) 0.08
Current children cumulated vsize (KiB) 5608

[startup+0.100684 s]
/proc/loadavg: 1.16 1.04 1.01 3/106 4642
/proc/meminfo: memFree=1849864/2059040 swapFree=4140244/4192956
[pid=4642] ppid=4640 vsize=5608 CPUtime=0.09
/proc/4642/stat : 4642 (pbct) R 4640 4642 3853 0 -1 4202496 1106 0 0 0 9 0 0 0 20 0 1 0 40546161 5742592 1028 1992294400 134512640 136485738 4288566656 18446744073709551615 135913329 0 0 4096 16387 0 0 0 17 1 0 0 0
/proc/4642/statm: 1402 1028 226 482 0 918 0
Current children cumulated CPU time (s) 0.09
Current children cumulated vsize (KiB) 5608

[startup+0.300699 s]
/proc/loadavg: 1.16 1.04 1.01 3/106 4642
/proc/meminfo: memFree=1849864/2059040 swapFree=4140244/4192956
[pid=4642] ppid=4640 vsize=5736 CPUtime=0.29
/proc/4642/stat : 4642 (pbct) R 4640 4642 3853 0 -1 4202496 1137 0 0 0 27 2 0 0 20 0 1 0 40546161 5873664 1059 1992294400 134512640 136485738 4288566656 18446744073709551615 135913329 0 0 4096 16387 0 0 0 17 1 0 0 0
/proc/4642/statm: 1434 1059 226 482 0 950 0
Current children cumulated CPU time (s) 0.29
Current children cumulated vsize (KiB) 5736

[startup+0.700732 s]
/proc/loadavg: 1.16 1.04 1.01 3/106 4642
/proc/meminfo: memFree=1849864/2059040 swapFree=4140244/4192956
[pid=4642] ppid=4640 vsize=5860 CPUtime=0.69
/proc/4642/stat : 4642 (pbct) R 4640 4642 3853 0 -1 4202496 1161 0 0 0 62 7 0 0 20 0 1 0 40546161 6000640 1083 1992294400 134512640 136485738 4288566656 18446744073709551615 135913329 0 0 4096 16387 0 0 0 17 1 0 0 0
/proc/4642/statm: 1465 1083 226 482 0 981 0
Current children cumulated CPU time (s) 0.69
Current children cumulated vsize (KiB) 5860

[startup+1.5008 s]
/proc/loadavg: 1.16 1.04 1.01 2/107 4643
/proc/meminfo: memFree=1846260/2059040 swapFree=4140244/4192956
[pid=4642] ppid=4640 vsize=5860 CPUtime=1.49
/proc/4642/stat : 4642 (pbct) R 4640 4642 3853 0 -1 4202496 1199 0 0 0 133 16 0 0 23 0 1 0 40546161 6000640 1120 1992294400 134512640 136485738 4288566656 18446744073709551615 135913329 0 0 4096 16387 0 0 0 17 1 0 0 0
/proc/4642/statm: 1465 1120 244 482 0 981 0
Current children cumulated CPU time (s) 1.49
Current children cumulated vsize (KiB) 5860

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

[startup+1.60081 s]
/proc/loadavg: 1.16 1.04 1.01 2/107 4643
/proc/meminfo: memFree=1846260/2059040 swapFree=4140244/4192956
[pid=4642] ppid=4640 vsize=5860 CPUtime=1.59
/proc/4642/stat : 4642 (pbct) R 4640 4642 3853 0 -1 4202496 1199 0 0 0 142 17 0 0 23 0 1 0 40546161 6000640 1120 1992294400 134512640 136485738 4288566656 18446744073709551615 135913329 0 0 4096 16387 0 0 0 17 1 0 0 0
/proc/4642/statm: 1465 1120 244 482 0 981 0
Current children cumulated CPU time (s) 1.59
Current children cumulated vsize (KiB) 5860

Child status: 0
Real time (s): 1.62659
CPU time (s): 1.62575
CPU user time (s): 1.45178
CPU system time (s): 0.173973
CPU usage (%): 99.9487
Max. virtual memory (cumulated for all children) (KiB): 5864

getrusage(RUSAGE_CHILDREN,...) data:
user time used= 1.45178
system time used= 0.173973
maximum resident set size= 0
integral shared memory size= 0
integral unshared data size= 0
integral unshared stack size= 0
page reclaims= 1206
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= 21

runsolver used 0.008998 second user time and 0.014997 second system time

The end

Launcher Data

Begin job on node003 at 2010-06-16 02:50:22
IDJOB=2667943
IDBENCH=48026
IDSOLVER=1170
FILE ID=node003/2667943-1276649422
PBS_JOBID= 11172402
Free space on /tmp= 62580 MiB

SOLVER NAME= PB/CT 0.1
BENCH NAME= PB07/normalized-PB07/OPT-SMALLINT-NLC/submittedPB07/roussel/factor-mod-B/factor-mod-size=9-P0=271-P1=293-B.opb
COMMAND LINE= HOME/pbct --model BENCHNAME
RUNSOLVER COMMAND LINE= BIN/runsolver --timestamp -w /tmp/evaluation-result-2667943-1276649422/watcher-2667943-1276649422 -o /tmp/evaluation-result-2667943-1276649422/solver-2667943-1276649422 -C 1800 -W 2000 -M 1800  HOME/pbct --model HOME/instance-2667943-1276649422.opb

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

MD5SUM BENCH= 2e3c7287841521f4043e8a0d4ae495d6
RANDOM SEED=1307921491

node003.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.251
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.50
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.251
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.45
clflush size	: 64
cache_alignment	: 128
address sizes	: 36 bits physical, 48 bits virtual
power management:


/proc/meminfo:
MemTotal:      2059040 kB
MemFree:       1850268 kB
Buffers:         25960 kB
Cached:         102452 kB
SwapCached:       6080 kB
Active:          95152 kB
Inactive:        46580 kB
HighTotal:           0 kB
HighFree:            0 kB
LowTotal:      2059040 kB
LowFree:       1850268 kB
SwapTotal:     4192956 kB
SwapFree:      4140244 kB
Dirty:            2044 kB
Writeback:           8 kB
AnonPages:       11640 kB
Mapped:          13200 kB
Slab:            45280 kB
PageTables:       4036 kB
NFS_Unstable:        0 kB
Bounce:              0 kB
CommitLimit:   5222476 kB
Committed_AS:   181972 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= 62580 MiB
End job on node003 at 2010-06-16 02:50:24