Trace number 2668202

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.1OPT5867 0.167973 0.167303

General information on the benchmark

Namenormalized-PB07/OPT-SMALLINT-LIN/submittedPB07/
poldner/PB/testset/normalized-6_12.opb
MD5SUMd3b3d1e364c50657a7515a2e4087a65b
Bench CategoryOPT-SMALLINT-LIN (optimisation, small integers, linear constraints)
Best result obtained on this benchmarkOPT
Best value of the objective obtained on this benchmark5867
Best CPU time to get the best result obtained on this benchmark0.024995
Has Objective FunctionYES
SatisfiableYES
(Un)Satisfiability was provedYES
Best value of the objective function 5867
Optimality of the best value was proved YES
Number of variables78
Total number of constraints84
Number of constraints which are clauses72
Number of constraints which are cardinality constraints (but not clauses)12
Number of constraints which are nor clauses,nor cardinality constraints0
Minimum length of a constraint2
Maximum length of a constraint6
Number of terms in the objective function 78
Biggest coefficient in the objective function 2194
Number of bits for the biggest coefficient in the objective function 12
Sum of the numbers in the objective function 39785
Number of bits of the sum of numbers in the objective function 16
Biggest number in a constraint 2194
Number of bits of the biggest number in a constraint 12
Biggest sum of numbers in a constraint 39785
Number of bits of the biggest sum of numbers16
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 http://www.residual.se/pbct
0.00/0.00	c Based on OpenSMT/CT 20091015
0.00/0.00	c constraints 12/0 clauses 72/0 units 0
0.00/0.00	c vars 78
0.00/0.00	c objective 78 + 0
0.00/0.01	c 0.011998 4.20703 1 115
0.00/0.01	o 7468
0.00/0.03	c 0.023996 4.20703 174 342
0.00/0.03	o 7287
0.00/0.03	c 0.024996 4.20703 93 366
0.00/0.03	o 7183
0.00/0.03	c 0.025996 4.20703 106 394
0.00/0.03	o 7152
0.02/0.04	c 0.032994 4.20703 114 560
0.02/0.04	o 6412
0.02/0.04	c 0.035994 4.20703 154 606
0.02/0.04	o 5867
0.09/0.16	c 0.136979 4.20703 10 2378
0.09/0.16	s OPTIMUM FOUND
0.09/0.16	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 x56 -x57 -x58 -x59 -x60 -x61 x62 -x63 -x64 -x65 -x66 -x67 x68 -x69 -x70 -x71 -x72 -x73 x74 -x75 -x76 -x77 -x78

Verifier Data 

OK	5867

Watcher Data 

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

command line: BIN/runsolver --timestamp -w /tmp/evaluation-result-2668202-1276629799/watcher-2668202-1276629799 -o /tmp/evaluation-result-2668202-1276629799/solver-2668202-1276629799 -C 1800 -W 2000 -M 1800 HOME/pbct --model HOME/instance-2668202-1276629799.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.98 1.07 1.27 3/107 4409
/proc/meminfo: memFree=1846648/2059040 swapFree=4140108/4192956
[pid=4409] ppid=4407 vsize=3512 CPUtime=0
/proc/4409/stat : 4409 (pbct) R 4407 4409 4047 0 -1 4202496 567 0 0 0 0 0 0 0 20 0 1 0 36635670 3596288 490 1992294400 134512640 136485738 4287339536 18446744073709551615 135850441 0 0 4096 16387 0 0 0 17 1 0 0 0
/proc/4409/statm: 878 491 198 482 0 394 0

[startup+0.0334259 s]
/proc/loadavg: 0.98 1.07 1.27 3/107 4409
/proc/meminfo: memFree=1846648/2059040 swapFree=4140108/4192956
[pid=4409] ppid=4407 vsize=4304 CPUtime=0.02
/proc/4409/stat : 4409 (pbct) R 4407 4409 4047 0 -1 4202496 812 0 0 0 2 0 0 0 20 0 1 0 36635670 4407296 731 1992294400 134512640 136485738 4287339536 18446744073709551615 135913329 0 0 4096 16387 0 0 0 17 1 0 0 0
/proc/4409/statm: 1076 731 244 482 0 592 0
Current children cumulated CPU time (s) 0.02
Current children cumulated vsize (KiB) 4304

[startup+0.100431 s]
/proc/loadavg: 0.98 1.07 1.27 3/107 4409
/proc/meminfo: memFree=1846648/2059040 swapFree=4140108/4192956
[pid=4409] ppid=4407 vsize=4304 CPUtime=0.09
/proc/4409/stat : 4409 (pbct) R 4407 4409 4047 0 -1 4202496 819 0 0 0 7 2 0 0 20 0 1 0 36635670 4407296 736 1992294400 134512640 136485738 4287339536 18446744073709551615 135913329 0 0 4096 16387 0 0 0 17 1 0 0 0
/proc/4409/statm: 1076 736 244 482 0 592 0
Current children cumulated CPU time (s) 0.09
Current children cumulated vsize (KiB) 4304

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

Child status: 0
Real time (s): 0.167303
CPU time (s): 0.167973
CPU user time (s): 0.138978
CPU system time (s): 0.028995
CPU usage (%): 100.4
Max. virtual memory (cumulated for all children) (KiB): 4304

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

The end

Launcher Data 

Begin job on node025 at 2010-06-15 21:23:19
IDJOB=2668202
IDBENCH=24967
IDSOLVER=1170
FILE ID=node025/2668202-1276629799
PBS_JOBID= 11172360
Free space on /tmp= 62580 MiB

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

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

MD5SUM BENCH= d3b3d1e364c50657a7515a2e4087a65b
RANDOM SEED=162324927

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


/proc/meminfo:
MemTotal:      2059040 kB
MemFree:       1847052 kB
Buffers:         21544 kB
Cached:         101784 kB
SwapCached:       7140 kB
Active:          44548 kB
Inactive:        93024 kB
HighTotal:           0 kB
HighFree:            0 kB
LowTotal:      2059040 kB
LowFree:       1847052 kB
SwapTotal:     4192956 kB
SwapFree:      4140108 kB
Dirty:            2276 kB
Writeback:           0 kB
AnonPages:       11852 kB
Mapped:          13104 kB
Slab:            52516 kB
PageTables:       4112 kB
NFS_Unstable:        0 kB
Bounce:              0 kB
CommitLimit:   5222476 kB
Committed_AS:   183816 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 node025 at 2010-06-15 21:23:20