Trace number 2681549

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.09183 1.09089

General information on the benchmark

Namenormalized-PB07/OPT-SMALLINT-NLC/submittedPB07/roussel/
factor-mod-B/factor-mod-size=5-P0=19-P1=23-P2=23-P3=23-B.opb
MD5SUMa7d7ec970e4707afa1937f254331884d
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.079987
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 variables45
Total number of constraints7
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 constraints7
Minimum length of a constraint5
Maximum length of a constraint35
Number of terms in the objective function 5
Biggest coefficient in the objective function 16
Number of bits for the biggest coefficient in the objective function 5
Sum of the numbers in the objective function 31
Number of bits of the sum of numbers in the objective function 5
Biggest number in a constraint 512
Number of bits of the biggest number in a constraint 10
Biggest sum of numbers in a constraint 1984
Number of bits of the biggest sum of numbers11
Number of products (including duplicates)75
Sum of products size (including duplicates)150
Number of different products75
Sum of products size150

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 82/0 clauses 75/0 units 0
0.00/0.00	c vars 45
0.00/0.00	c objective 5 + 0
0.09/0.12	c 0.103984 5.17578 371 2679
0.09/0.12	o 3
0.99/1.08	c 0.948855 5.17578 496 26402
0.99/1.08	s OPTIMUM FOUND
0.99/1.08	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

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-2681549-1277499488/watcher-2681549-1277499488 -o /tmp/evaluation-result-2681549-1277499488/solver-2681549-1277499488 -C 1800 -W 2000 -M 1800 HOME/pbct --model HOME/instance-2681549-1277499488.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 0.99 0.99 3/106 24825
/proc/meminfo: memFree=1822692/2059040 swapFree=4139932/4192956
[pid=24825] ppid=24823 vsize=3444 CPUtime=0
/proc/24825/stat : 24825 (pbct) R 24823 24825 24403 0 -1 4202496 578 0 0 0 0 0 0 0 20 0 1 0 125552504 3526656 497 1992294400 134512640 136421960 4289149936 18446744073709551615 135811817 0 0 4096 16387 0 0 0 17 1 0 0 0
/proc/24825/statm: 861 498 193 467 0 392 0

[startup+0.0652791 s]
/proc/loadavg: 1.00 0.99 0.99 3/106 24825
/proc/meminfo: memFree=1822692/2059040 swapFree=4139932/4192956
[pid=24825] ppid=24823 vsize=5296 CPUtime=0.06
/proc/24825/stat : 24825 (pbct) R 24823 24825 24403 0 -1 4202496 1036 0 0 0 5 1 0 0 20 0 1 0 125552504 5423104 955 1992294400 134512640 136421960 4289149936 18446744073709551615 135874657 0 0 4096 16387 0 0 0 17 1 0 0 0
/proc/24825/statm: 1324 955 214 467 0 855 0
Current children cumulated CPU time (s) 0.06
Current children cumulated vsize (KiB) 5296

[startup+0.101282 s]
/proc/loadavg: 1.00 0.99 0.99 3/106 24825
/proc/meminfo: memFree=1822692/2059040 swapFree=4139932/4192956
[pid=24825] ppid=24823 vsize=5296 CPUtime=0.09
/proc/24825/stat : 24825 (pbct) R 24823 24825 24403 0 -1 4202496 1040 0 0 0 8 1 0 0 20 0 1 0 125552504 5423104 959 1992294400 134512640 136421960 4289149936 18446744073709551615 135874657 0 0 4096 16387 0 0 0 17 1 0 0 0
/proc/24825/statm: 1324 959 214 467 0 855 0
Current children cumulated CPU time (s) 0.09
Current children cumulated vsize (KiB) 5296

[startup+0.301304 s]
/proc/loadavg: 1.00 0.99 0.99 3/106 24825
/proc/meminfo: memFree=1822692/2059040 swapFree=4139932/4192956
[pid=24825] ppid=24823 vsize=5296 CPUtime=0.29
/proc/24825/stat : 24825 (pbct) R 24823 24825 24403 0 -1 4202496 1074 0 0 0 26 3 0 0 20 0 1 0 125552504 5423104 992 1992294400 134512640 136421960 4289149936 18446744073709551615 135874657 0 0 4096 16387 0 0 0 17 1 0 0 0
/proc/24825/statm: 1324 992 237 467 0 855 0
Current children cumulated CPU time (s) 0.29
Current children cumulated vsize (KiB) 5296

[startup+0.701349 s]
/proc/loadavg: 1.00 0.99 0.99 3/106 24825
/proc/meminfo: memFree=1822692/2059040 swapFree=4139932/4192956
[pid=24825] ppid=24823 vsize=5296 CPUtime=0.69
/proc/24825/stat : 24825 (pbct) R 24823 24825 24403 0 -1 4202496 1078 0 0 0 60 9 0 0 20 0 1 0 125552504 5423104 996 1992294400 134512640 136421960 4289149936 18446744073709551615 135874657 0 0 4096 16387 0 0 0 17 1 0 0 0
/proc/24825/statm: 1324 996 237 467 0 855 0
Current children cumulated CPU time (s) 0.69
Current children cumulated vsize (KiB) 5296

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

[startup+0.901371 s]
/proc/loadavg: 1.00 0.99 0.99 3/106 24825
/proc/meminfo: memFree=1822692/2059040 swapFree=4139932/4192956
[pid=24825] ppid=24823 vsize=5296 CPUtime=0.89
/proc/24825/stat : 24825 (pbct) R 24823 24825 24403 0 -1 4202496 1081 0 0 0 78 11 0 0 21 0 1 0 125552504 5423104 999 1992294400 134512640 136421960 4289149936 18446744073709551615 135874657 0 0 4096 16387 0 0 0 17 1 0 0 0
/proc/24825/statm: 1324 999 237 467 0 855 0
Current children cumulated CPU time (s) 0.89
Current children cumulated vsize (KiB) 5296

[startup+1.00138 s]
/proc/loadavg: 1.00 0.99 0.99 2/107 24826
/proc/meminfo: memFree=1819336/2059040 swapFree=4139932/4192956
[pid=24825] ppid=24823 vsize=5296 CPUtime=0.99
/proc/24825/stat : 24825 (pbct) R 24823 24825 24403 0 -1 4202496 1081 0 0 0 87 12 0 0 21 0 1 0 125552504 5423104 999 1992294400 134512640 136421960 4289149936 18446744073709551615 135874657 0 0 4096 16387 0 0 0 17 1 0 0 0
/proc/24825/statm: 1324 999 237 467 0 855 0
Current children cumulated CPU time (s) 0.99
Current children cumulated vsize (KiB) 5296

Child status: 0
Real time (s): 1.09089
CPU time (s): 1.09183
CPU user time (s): 0.952855
CPU system time (s): 0.138978
CPU usage (%): 100.086
Max. virtual memory (cumulated for all children) (KiB): 5296

getrusage(RUSAGE_CHILDREN,...) data:
user time used= 0.952855
system time used= 0.138978
maximum resident set size= 0
integral shared memory size= 0
integral unshared data size= 0
integral unshared stack size= 0
page reclaims= 1086
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.004999 second user time and 0.012998 second system time

The end

Launcher Data 

Begin job on node005 at 2010-06-25 22:58:08
IDJOB=2681549
IDBENCH=48038
IDSOLVER=1192
FILE ID=node005/2681549-1277499488
PBS_JOBID= 11190567
Free space on /tmp= 62528 MiB

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

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

MD5SUM BENCH= a7d7ec970e4707afa1937f254331884d
RANDOM SEED=1870506713

node005.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.246
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.49
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.246
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:       1823096 kB
Buffers:         46500 kB
Cached:          90764 kB
SwapCached:       5480 kB
Active:          67572 kB
Inactive:        82664 kB
HighTotal:           0 kB
HighFree:            0 kB
LowTotal:      2059040 kB
LowFree:       1823096 kB
SwapTotal:     4192956 kB
SwapFree:      4139932 kB
Dirty:            1900 kB
Writeback:           8 kB
AnonPages:       11604 kB
Mapped:          11932 kB
Slab:            63692 kB
PageTables:       4096 kB
NFS_Unstable:        0 kB
Bounce:              0 kB
CommitLimit:   5222476 kB
Committed_AS:   181956 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= 62528 MiB
End job on node005 at 2010-06-25 22:58:09