Trace number 2680405

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
wbo 1.4b (fixed)OPT5867 0.028995 0.0294931

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

Solver Data 

0.00/0.00	c wbo 1.4 beta - 20100610
0.00/0.00	c Parsing opb file format. File HOME/instance-2680405-1277459186.opb.
0.00/0.00	c Instance file HOME/instance-2680405-1277459186.opb
0.00/0.00	c File size is 2969 bytes.
0.00/0.00	c Highest Coefficient sum: 7
0.00/0.00	c ============================[ Problem Statistics ]=============================
0.00/0.00	c |                                                                             |
0.00/0.00	c |  Parsing time:          0.00         s                                      |
0.00/0.00	c |  Number Variables:      78                                                  |
0.00/0.00	c |  Number Clauses:        84                                                  |
0.00/0.00	c |  Number Cardinality:    12                                                  |
0.00/0.00	c |  Number PB Constraints: 0                                                   |
0.00/0.00	c ============================[ Search Statistics ]==============================
0.00/0.00	c | Conflicts |          ORIGINAL         |          LEARNT          | Progress |
0.00/0.00	c |           |    Vars     Ctrs     Lits |    Limit  Clauses Lit/Cl |          |
0.00/0.00	c ===============================================================================
0.00/0.00	c |         0 |      78       96      288 |     5000        0    nan |  0.000 % |
0.00/0.00	c ===============================================================================
0.00/0.00	c New solution: 5867
0.00/0.00	o 5867
0.00/0.00	c Elapsed CPU time: 0.000999 s	Remaining CPU time: 179.999 s
0.00/0.00	c ===============================================================================
0.00/0.00	c |         0 |      78       97      366 |     5000        0    nan |  0.000 % |
0.00/0.00	c |       101 |      78       97      366 |     5500      101     18 |  0.017 % |
0.00/0.00	c |       251 |      78       97      366 |     6050      251     18 |  0.019 % |
0.00/0.01	c |       476 |      78       97      366 |     6655      476     18 |  0.215 % |
0.00/0.02	c |       814 |      77       97      366 |     7320      781     19 |  1.512 % |
0.00/0.02	c ===============================================================================
0.00/0.02	c Best Solution: 5867
0.00/0.02	s OPTIMUM FOUND
0.00/0.02	c Total CPU time: 0.023996 s
0.00/0.02	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-2680405-1277459186/watcher-2680405-1277459186 -o /tmp/evaluation-result-2680405-1277459186/solver-2680405-1277459186 -C 1800 -W 2000 -M 1800 wbo1.4b -file-format=opb -time-limit=1800 HOME/instance-2680405-1277459186.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 0.93 3/107 22543
/proc/meminfo: memFree=1797264/2059040 swapFree=4139780/4192956
[pid=22543] ppid=22541 vsize=2576 CPUtime=0
/proc/22543/stat : 22543 (wbo1.4b) R 22541 22543 22155 0 -1 4202496 279 0 0 0 0 0 0 0 20 0 1 0 119574376 2637824 196 1992294400 134512640 135752675 4294245168 18446744073709551615 135271249 0 0 4096 3 0 0 0 17 1 0 0 0
/proc/22543/statm: 644 196 145 303 0 339 0

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

Child status: 0
Real time (s): 0.0294931
CPU time (s): 0.028995
CPU user time (s): 0.023996
CPU system time (s): 0.004999
CPU usage (%): 98.3112
Max. virtual memory (cumulated for all children) (KiB): 0

getrusage(RUSAGE_CHILDREN,...) data:
user time used= 0.023996
system time used= 0.004999
maximum resident set size= 0
integral shared memory size= 0
integral unshared data size= 0
integral unshared stack size= 0
page reclaims= 316
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= 2
involuntary context switches= 1

runsolver used 0.005999 second user time and 0.007998 second system time

The end

Launcher Data 

Begin job on node025 at 2010-06-25 11:46:26
IDJOB=2680405
IDBENCH=24967
IDSOLVER=1190
FILE ID=node025/2680405-1277459186
PBS_JOBID= 11188139
Free space on /tmp= 62324 MiB

SOLVER NAME= wbo 1.4b (fixed)
BENCH NAME= PB07/normalized-PB07/OPT-SMALLINT-LIN/submittedPB07/poldner/PB/testset/normalized-6_12.opb
COMMAND LINE= wbo1.4b -file-format=opb -time-limit=TIMEOUT BENCHNAME
RUNSOLVER COMMAND LINE= BIN/runsolver --timestamp -w /tmp/evaluation-result-2680405-1277459186/watcher-2680405-1277459186 -o /tmp/evaluation-result-2680405-1277459186/solver-2680405-1277459186 -C 1800 -W 2000 -M 1800  wbo1.4b -file-format=opb -time-limit=1800 HOME/instance-2680405-1277459186.opb

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

MD5SUM BENCH= d3b3d1e364c50657a7515a2e4087a65b
RANDOM SEED=1748227679

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:       1797668 kB
Buffers:         30840 kB
Cached:         125588 kB
SwapCached:       5912 kB
Active:          65324 kB
Inactive:       105020 kB
HighTotal:           0 kB
HighFree:            0 kB
LowTotal:      2059040 kB
LowFree:       1797668 kB
SwapTotal:     4192956 kB
SwapFree:      4139780 kB
Dirty:            2676 kB
Writeback:           0 kB
AnonPages:       12440 kB
Mapped:          11852 kB
Slab:            69032 kB
PageTables:       4232 kB
NFS_Unstable:        0 kB
Bounce:              0 kB
CommitLimit:   5222476 kB
Committed_AS:   184652 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= 62324 MiB
End job on node025 at 2010-06-25 11:46:27