Trace number 2681797

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 fixedOPT3951 0.052991 0.052831

General information on the benchmark

Namenormalized-PB07/OPT-SMALLINT-LIN/submittedPB07/
poldner/PB/testset/normalized-5_10.opb
MD5SUMba69a176dcc33e2f7eda6b169d4d1c84
Bench CategoryOPT-SMALLINT-LIN (optimisation, small integers, linear constraints)
Best result obtained on this benchmarkOPT
Best value of the objective obtained on this benchmark3951
Best CPU time to get the best result obtained on this benchmark0.012997
Has Objective FunctionYES
SatisfiableYES
(Un)Satisfiability was provedYES
Best value of the objective function 3951
Optimality of the best value was proved YES
Number of variables55
Total number of constraints60
Number of constraints which are clauses50
Number of constraints which are cardinality constraints (but not clauses)10
Number of constraints which are nor clauses,nor cardinality constraints0
Minimum length of a constraint2
Maximum length of a constraint5
Number of terms in the objective function 55
Biggest coefficient in the objective function 1772
Number of bits for the biggest coefficient in the objective function 11
Sum of the numbers in the objective function 25669
Number of bits of the sum of numbers in the objective function 15
Biggest number in a constraint 1772
Number of bits of the biggest number in a constraint 11
Biggest sum of numbers in a constraint 25669
Number of bits of the biggest sum of numbers15
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.1 http://www.residual.se/pbct
0.00/0.00	c Based on OpenSMT/CT 20091015
0.00/0.00	c constraints 10/0 clauses 50/0 units 0
0.00/0.00	c vars 55
0.00/0.00	c objective 55 + 0
0.00/0.01	c 0.008998 3.75391 1 76
0.00/0.01	o 5352
0.00/0.01	c 0.009998 3.75391 30 136
0.00/0.01	o 5262
0.00/0.01	c 0.010998 3.75391 43 156
0.00/0.01	o 5048
0.00/0.01	c 0.012998 3.75391 65 191
0.00/0.01	o 4981
0.00/0.01	c 0.013997 3.75391 75 219
0.00/0.01	o 4929
0.00/0.01	c 0.013997 3.75391 75 224
0.00/0.01	o 4066
0.00/0.01	c 0.014997 3.75391 96 257
0.00/0.01	o 4063
0.00/0.03	c 0.029995 3.75391 147 582
0.00/0.03	o 4018
0.00/0.04	c 0.035994 3.75391 90 686
0.00/0.04	o 3951
0.03/0.05	c 0.040993 3.75391 45 810
0.03/0.05	s OPTIMUM FOUND
0.03/0.05	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

Verifier Data 

OK	3951

Watcher Data 

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

command line: BIN/runsolver --timestamp -w /tmp/evaluation-result-2681797-1277495251/watcher-2681797-1277495251 -o /tmp/evaluation-result-2681797-1277495251/solver-2681797-1277495251 -C 1800 -W 2000 -M 1800 HOME/pbct --model HOME/instance-2681797-1277495251.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.07 1.00 1.00 3/105 30364
/proc/meminfo: memFree=1835372/2059040 swapFree=4135356/4192956
[pid=30364] ppid=30362 vsize=3708 CPUtime=0
/proc/30364/stat : 30364 (pbct) R 30362 30364 30089 0 -1 4202496 652 0 0 0 0 0 0 0 25 0 1 0 90818927 3796992 571 1992294400 134512640 136421960 4294121760 18446744073709551615 134640520 0 0 4096 16387 0 0 0 17 1 0 0 0
/proc/30364/statm: 927 572 203 467 0 458 0

[startup+0.045731 s]
/proc/loadavg: 1.07 1.00 1.00 3/105 30364
/proc/meminfo: memFree=1835372/2059040 swapFree=4135356/4192956
[pid=30364] ppid=30362 vsize=3840 CPUtime=0.03
/proc/30364/stat : 30364 (pbct) R 30362 30364 30089 0 -1 4202496 722 0 0 0 3 0 0 0 25 0 1 0 90818927 3932160 632 1992294400 134512640 136421960 4294121760 18446744073709551615 135874657 0 0 4096 16387 0 0 0 17 1 0 0 0
/proc/30364/statm: 960 632 237 467 0 491 0
Current children cumulated CPU time (s) 0.03
Current children cumulated vsize (KiB) 3840

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

[startup+0.045731 s]
/proc/loadavg: 1.07 1.00 1.00 3/105 30364
/proc/meminfo: memFree=1835372/2059040 swapFree=4135356/4192956
[pid=30364] ppid=30362 vsize=3840 CPUtime=0.03
/proc/30364/stat : 30364 (pbct) R 30362 30364 30089 0 -1 4202496 722 0 0 0 3 0 0 0 25 0 1 0 90818927 3932160 632 1992294400 134512640 136421960 4294121760 18446744073709551615 135874657 0 0 4096 16387 0 0 0 17 1 0 0 0
/proc/30364/statm: 960 632 237 467 0 491 0
Current children cumulated CPU time (s) 0.03
Current children cumulated vsize (KiB) 3840

Child status: 0
Real time (s): 0.052831
CPU time (s): 0.052991
CPU user time (s): 0.041993
CPU system time (s): 0.010998
CPU usage (%): 100.303
Max. virtual memory (cumulated for all children) (KiB): 3840

getrusage(RUSAGE_CHILDREN,...) data:
user time used= 0.041993
system time used= 0.010998
maximum resident set size= 0
integral shared memory size= 0
integral unshared data size= 0
integral unshared stack size= 0
page reclaims= 727
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.009998 second system time

The end

Launcher Data 

Begin job on node084 at 2010-06-25 21:47:31
IDJOB=2681797
IDBENCH=24968
IDSOLVER=1192
FILE ID=node084/2681797-1277495251
PBS_JOBID= 11190561
Free space on /tmp= 62456 MiB

SOLVER NAME= PB/CT 0.1 fixed
BENCH NAME= PB07/normalized-PB07/OPT-SMALLINT-LIN/submittedPB07/poldner/PB/testset/normalized-5_10.opb
COMMAND LINE= HOME/pbct --model BENCHNAME
RUNSOLVER COMMAND LINE= BIN/runsolver --timestamp -w /tmp/evaluation-result-2681797-1277495251/watcher-2681797-1277495251 -o /tmp/evaluation-result-2681797-1277495251/solver-2681797-1277495251 -C 1800 -W 2000 -M 1800  HOME/pbct --model HOME/instance-2681797-1277495251.opb

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

MD5SUM BENCH= ba69a176dcc33e2f7eda6b169d4d1c84
RANDOM SEED=188365463

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


/proc/meminfo:
MemTotal:      2059040 kB
MemFree:       1835900 kB
Buffers:         25032 kB
Cached:         102044 kB
SwapCached:       9708 kB
Active:          24764 kB
Inactive:       114912 kB
HighTotal:           0 kB
HighFree:            0 kB
LowTotal:      2059040 kB
LowFree:       1835900 kB
SwapTotal:     4192956 kB
SwapFree:      4135356 kB
Dirty:            1880 kB
Writeback:           0 kB
AnonPages:       11320 kB
Mapped:           8280 kB
Slab:            61508 kB
PageTables:       4100 kB
NFS_Unstable:        0 kB
Bounce:              0 kB
CommitLimit:   5222476 kB
Committed_AS:   180700 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= 62456 MiB
End job on node084 at 2010-06-25 21:47:31