Trace number 2681593

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.1 fixedOPT3 1.21581 1.21646

General information on the benchmark

Namenormalized-PB07/OPT-SMALLINT-NLC/submittedPB07/roussel/
factor-mod-B/factor-mod-size=8-P0=157-P1=107-B.opb
MD5SUM81bcbf479f290ea51f43d1561f9d15dc
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.05999
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 variables24
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 constraint8
Maximum length of a constraint72
Number of terms in the objective function 8
Biggest coefficient in the objective function 128
Number of bits for the biggest coefficient in the objective function 8
Sum of the numbers in the objective function 255
Number of bits of the sum of numbers in the objective function 8
Biggest number in a constraint 32768
Number of bits of the biggest number in a constraint 16
Biggest sum of numbers in a constraint 130464
Number of bits of the biggest sum of numbers17
Number of products (including duplicates)64
Sum of products size (including duplicates)128
Number of different products64
Sum of products size128

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.1 http://www.residual.se/pbct
0.00/0.00	c Based on OpenSMT/CT 20091015
0.00/0.00	c constraints 67/0 clauses 64/0 units 0
0.00/0.00	c vars 24
0.00/0.00	c objective 8 + 0
0.69/0.70	c 0.619905 5.05469 588 14985
0.69/0.70	o 53
1.19/1.20	c 1.06484 5.05469 317 27300
1.19/1.20	o 3
1.19/1.21	c 1.06784 5.05469 249 27390
1.19/1.21	s OPTIMUM FOUND
1.19/1.21	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

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-2681593-1277500384/watcher-2681593-1277500384 -o /tmp/evaluation-result-2681593-1277500384/solver-2681593-1277500384 -C 1800 -W 2000 -M 1800 HOME/pbct --model HOME/instance-2681593-1277500384.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.00 1.00 1.00 3/106 26769
/proc/meminfo: memFree=1864148/2059040 swapFree=4136476/4192956
[pid=26769] ppid=26767 vsize=3576 CPUtime=0
/proc/26769/stat : 26769 (pbct) R 26767 26769 26266 0 -1 4202496 589 0 0 0 0 0 0 0 18 0 1 0 125639934 3661824 509 1992294400 134512640 136421960 4289955904 18446744073709551615 135811817 0 0 4096 16387 0 0 0 17 1 0 0 0
/proc/26769/statm: 894 510 193 467 0 425 0

[startup+0.0118131 s]
/proc/loadavg: 1.00 1.00 1.00 3/106 26769
/proc/meminfo: memFree=1864148/2059040 swapFree=4136476/4192956
[pid=26769] ppid=26767 vsize=3848 CPUtime=0
/proc/26769/stat : 26769 (pbct) R 26767 26769 26266 0 -1 4202496 654 0 0 0 0 0 0 0 20 0 1 0 125639934 3940352 574 1992294400 134512640 136421960 4289955904 18446744073709551615 135811817 0 0 4096 16387 0 0 0 17 1 0 0 0
/proc/26769/statm: 962 579 193 467 0 493 0
Current children cumulated CPU time (s) 0
Current children cumulated vsize (KiB) 3848

[startup+0.100827 s]
/proc/loadavg: 1.00 1.00 1.00 3/106 26769
/proc/meminfo: memFree=1864148/2059040 swapFree=4136476/4192956
[pid=26769] ppid=26767 vsize=5040 CPUtime=0.09
/proc/26769/stat : 26769 (pbct) R 26767 26769 26266 0 -1 4202496 981 0 0 0 8 1 0 0 20 0 1 0 125639934 5160960 901 1992294400 134512640 136421960 4289955904 18446744073709551615 135874657 0 0 4096 16387 0 0 0 17 1 0 0 0
/proc/26769/statm: 1260 901 214 467 0 791 0
Current children cumulated CPU time (s) 0.09
Current children cumulated vsize (KiB) 5040

[startup+0.300863 s]
/proc/loadavg: 1.00 1.00 1.00 3/106 26769
/proc/meminfo: memFree=1864148/2059040 swapFree=4136476/4192956
[pid=26769] ppid=26767 vsize=5040 CPUtime=0.29
/proc/26769/stat : 26769 (pbct) R 26767 26769 26266 0 -1 4202496 993 0 0 0 26 3 0 0 20 0 1 0 125639934 5160960 913 1992294400 134512640 136421960 4289955904 18446744073709551615 135874657 0 0 4096 16387 0 0 0 17 1 0 0 0
/proc/26769/statm: 1260 913 214 467 0 791 0
Current children cumulated CPU time (s) 0.29
Current children cumulated vsize (KiB) 5040

[startup+0.700934 s]
/proc/loadavg: 1.00 1.00 1.00 3/106 26769
/proc/meminfo: memFree=1864148/2059040 swapFree=4136476/4192956
[pid=26769] ppid=26767 vsize=5172 CPUtime=0.69
/proc/26769/stat : 26769 (pbct) R 26767 26769 26266 0 -1 4202496 1005 0 0 0 61 8 0 0 20 0 1 0 125639934 5296128 925 1992294400 134512640 136421960 4289955904 18446744073709551615 135874657 0 0 4096 16387 0 0 0 17 1 0 0 0
/proc/26769/statm: 1293 925 214 467 0 824 0
Current children cumulated CPU time (s) 0.69
Current children cumulated vsize (KiB) 5172

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

[startup+1.10901 s]
/proc/loadavg: 1.00 1.00 1.00 2/107 26770
/proc/meminfo: memFree=1861164/2059040 swapFree=4136476/4192956
[pid=26769] ppid=26767 vsize=5172 CPUtime=1.1
/proc/26769/stat : 26769 (pbct) R 26767 26769 26266 0 -1 4202496 1038 0 0 0 98 12 0 0 21 0 1 0 125639934 5296128 957 1992294400 134512640 136421960 4289955904 18446744073709551615 135874657 0 0 4096 16387 0 0 0 17 1 0 0 0
/proc/26769/statm: 1293 957 237 467 0 824 0
Current children cumulated CPU time (s) 1.1
Current children cumulated vsize (KiB) 5172

[startup+1.20102 s]
/proc/loadavg: 1.00 1.00 1.00 2/107 26770
/proc/meminfo: memFree=1861164/2059040 swapFree=4136476/4192956
[pid=26769] ppid=26767 vsize=5172 CPUtime=1.19
/proc/26769/stat : 26769 (pbct) R 26767 26769 26266 0 -1 4202496 1038 0 0 0 105 14 0 0 22 0 1 0 125639934 5296128 957 1992294400 134512640 136421960 4289955904 18446744073709551615 135874657 0 0 4096 16387 0 0 0 17 1 0 0 0
/proc/26769/statm: 1293 957 237 467 0 824 0
Current children cumulated CPU time (s) 1.19
Current children cumulated vsize (KiB) 5172

Child status: 0
Real time (s): 1.21646
CPU time (s): 1.21581
CPU user time (s): 1.07184
CPU system time (s): 0.143978
CPU usage (%): 99.9466
Max. virtual memory (cumulated for all children) (KiB): 5172

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

runsolver used 0.007998 second user time and 0.013997 second system time

The end

Launcher Data 

Begin job on node012 at 2010-06-25 23:13:04
IDJOB=2681593
IDBENCH=48082
IDSOLVER=1192
FILE ID=node012/2681593-1277500384
PBS_JOBID= 11190579
Free space on /tmp= 62428 MiB

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

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

MD5SUM BENCH= 81bcbf479f290ea51f43d1561f9d15dc
RANDOM SEED=455054497

node012.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.258
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.51
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.258
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:       1864676 kB
Buffers:         25604 kB
Cached:          72552 kB
SwapCached:       8996 kB
Active:          62708 kB
Inactive:        48532 kB
HighTotal:           0 kB
HighFree:            0 kB
LowTotal:      2059040 kB
LowFree:       1864676 kB
SwapTotal:     4192956 kB
SwapFree:      4136476 kB
Dirty:            1876 kB
Writeback:           0 kB
AnonPages:       11656 kB
Mapped:           8404 kB
Slab:            61024 kB
PageTables:       4180 kB
NFS_Unstable:        0 kB
Bounce:              0 kB
CommitLimit:   5222476 kB
Committed_AS:   182372 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= 62428 MiB
End job on node012 at 2010-06-25 23:13:05