Trace number 2681512

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 0.557914 0.557253

General information on the benchmark

Namenormalized-PB07/OPT-SMALLINT-NLC/submittedPB07/roussel/
factor-mod-B/factor-mod-size=8-P0=223-P1=73-B.opb
MD5SUM922420a68683b7e293a59c451b6ae509
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.052991
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 130456
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.39/0.40	c 0.359945 4.92578 696 8460
0.39/0.40	o 39
0.49/0.50	c 0.447931 5.07812 265 10680
0.49/0.50	o 13
0.49/0.50	c 0.45593 5.07812 249 10872
0.49/0.50	o 11
0.49/0.55	c 0.498924 5.07812 289 12047
0.49/0.55	o 3
0.49/0.55	c 0.498924 5.07812 289 12047
0.49/0.55	s OPTIMUM FOUND
0.49/0.55	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-2681512-1277499034/watcher-2681512-1277499034 -o /tmp/evaluation-result-2681512-1277499034/solver-2681512-1277499034 -C 1800 -W 2000 -M 1800 HOME/pbct --model HOME/instance-2681512-1277499034.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.99 0.98 0.99 3/106 21909
/proc/meminfo: memFree=1803912/2059040 swapFree=4135892/4192956
[pid=21909] ppid=21907 vsize=3576 CPUtime=0
/proc/21909/stat : 21909 (pbct) R 21907 21909 21470 0 -1 4202496 587 0 0 0 0 0 0 0 20 0 1 0 125504764 3661824 506 1992294400 134512640 136421960 4288861856 18446744073709551615 135811817 0 0 4096 16387 0 0 0 17 1 0 0 0
/proc/21909/statm: 894 507 193 467 0 425 0

[startup+0.0732699 s]
/proc/loadavg: 0.99 0.98 0.99 3/106 21909
/proc/meminfo: memFree=1803912/2059040 swapFree=4135892/4192956
[pid=21909] ppid=21907 vsize=5040 CPUtime=0.07
/proc/21909/stat : 21909 (pbct) R 21907 21909 21470 0 -1 4202496 970 0 0 0 6 1 0 0 20 0 1 0 125504764 5160960 889 1992294400 134512640 136421960 4288861856 18446744073709551615 135874657 0 0 4096 16387 0 0 0 17 1 0 0 0
/proc/21909/statm: 1260 889 214 467 0 791 0
Current children cumulated CPU time (s) 0.07
Current children cumulated vsize (KiB) 5040

[startup+0.100274 s]
/proc/loadavg: 0.99 0.98 0.99 3/106 21909
/proc/meminfo: memFree=1803912/2059040 swapFree=4135892/4192956
[pid=21909] ppid=21907 vsize=5040 CPUtime=0.09
/proc/21909/stat : 21909 (pbct) R 21907 21909 21470 0 -1 4202496 978 0 0 0 8 1 0 0 20 0 1 0 125504764 5160960 897 1992294400 134512640 136421960 4288861856 18446744073709551615 135874657 0 0 4096 16387 0 0 0 17 1 0 0 0
/proc/21909/statm: 1260 897 214 467 0 791 0
Current children cumulated CPU time (s) 0.09
Current children cumulated vsize (KiB) 5040

[startup+0.300308 s]
/proc/loadavg: 0.99 0.98 0.99 3/106 21909
/proc/meminfo: memFree=1803912/2059040 swapFree=4135892/4192956
[pid=21909] ppid=21907 vsize=5040 CPUtime=0.29
/proc/21909/stat : 21909 (pbct) R 21907 21909 21470 0 -1 4202496 993 0 0 0 26 3 0 0 20 0 1 0 125504764 5160960 912 1992294400 134512640 136421960 4288861856 18446744073709551615 135874657 0 0 4096 16387 0 0 0 17 1 0 0 0
/proc/21909/statm: 1260 912 214 467 0 791 0
Current children cumulated CPU time (s) 0.29
Current children cumulated vsize (KiB) 5040

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

[startup+0.500343 s]
/proc/loadavg: 0.99 0.98 0.99 3/106 21909
/proc/meminfo: memFree=1803912/2059040 swapFree=4135892/4192956
[pid=21909] ppid=21907 vsize=5196 CPUtime=0.49
/proc/21909/stat : 21909 (pbct) R 21907 21909 21470 0 -1 4202496 1034 0 0 0 44 5 0 0 20 0 1 0 125504764 5320704 952 1992294400 134512640 136421960 4288861856 18446744073709551615 135874657 0 0 4096 16387 0 0 0 17 1 0 0 0
/proc/21909/statm: 1299 952 237 467 0 830 0
Current children cumulated CPU time (s) 0.49
Current children cumulated vsize (KiB) 5196

Child status: 0
Real time (s): 0.557253
CPU time (s): 0.557914
CPU user time (s): 0.502923
CPU system time (s): 0.054991
CPU usage (%): 100.119
Max. virtual memory (cumulated for all children) (KiB): 5196

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

runsolver used 0.001999 second user time and 0.008998 second system time

The end

Launcher Data

Begin job on node014 at 2010-06-25 22:50:34
IDJOB=2681512
IDBENCH=48001
IDSOLVER=1192
FILE ID=node014/2681512-1277499034
PBS_JOBID= 11190565
Free space on /tmp= 62436 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=223-P1=73-B.opb
COMMAND LINE= HOME/pbct --model BENCHNAME
RUNSOLVER COMMAND LINE= BIN/runsolver --timestamp -w /tmp/evaluation-result-2681512-1277499034/watcher-2681512-1277499034 -o /tmp/evaluation-result-2681512-1277499034/solver-2681512-1277499034 -C 1800 -W 2000 -M 1800  HOME/pbct --model HOME/instance-2681512-1277499034.opb

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

MD5SUM BENCH= 922420a68683b7e293a59c451b6ae509
RANDOM SEED=550325911

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


/proc/meminfo:
MemTotal:      2059040 kB
MemFree:       1804316 kB
Buffers:         50796 kB
Cached:         101656 kB
SwapCached:       9968 kB
Active:          60988 kB
Inactive:       104884 kB
HighTotal:           0 kB
HighFree:            0 kB
LowTotal:      2059040 kB
LowFree:       1804316 kB
SwapTotal:     4192956 kB
SwapFree:      4135892 kB
Dirty:            1908 kB
Writeback:           0 kB
AnonPages:       12068 kB
Mapped:           8400 kB
Slab:            66836 kB
PageTables:       4172 kB
NFS_Unstable:        0 kB
Bounce:              0 kB
CommitLimit:   5222476 kB
Committed_AS:   182708 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= 62436 MiB
End job on node014 at 2010-06-25 22:50:34