Trace number 2656227

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.4bOPT11 0.012997 0.011925

General information on the benchmark

Namenormalized-PB06/OPT-SMALLINT/
submitted-PB06/manquiho/golomb-rulers/normalized-OGR_5.opb
MD5SUMf7ce1bbc714a6b404586716e62ae4fc9
Bench CategoryOPT-SMALLINT (optimisation, small integers)
Best result obtained on this benchmarkOPT
Best value of the objective obtained on this benchmark11
Best CPU time to get the best result obtained on this benchmark0.016997
Has Objective FunctionYES
SatisfiableYES
(Un)Satisfiability was provedYES
Best value of the objective function 11
Optimality of the best value was proved YES
Number of variables75
Total number of constraints104
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 constraints104
Minimum length of a constraint10
Maximum length of a constraint21
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 32
Number of bits of the biggest number in a constraint 6
Biggest sum of numbers in a constraint 173
Number of bits of the biggest sum of numbers8
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 wbo 1.4 beta - 20100517
0.00/0.00	c Parsing opb file format. File HOME/instance-2656227-1276583857.opb.
0.00/0.00	c Instance file HOME/instance-2656227-1276583857.opb
0.00/0.00	c File size is 12435 bytes.
0.00/0.00	c Highest Coefficient sum: 173
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:      75                                                  |
0.00/0.00	c |  Number Clauses:        0                                                   |
0.00/0.00	c |  Number Cardinality:    0                                                   |
0.00/0.00	c |  Number PB Constraints: 104                                                 |
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 |      75      104     1640 |     5000        0    nan |  0.000 % |
0.00/0.00	c ===============================================================================
0.00/0.00	c New solution: 28
0.00/0.00	o 28
0.00/0.00	c Elapsed CPU time: 0.005999 s	Remaining CPU time: 179.994 s
0.00/0.00	c ===============================================================================
0.00/0.00	c |        36 |      75      105     1645 |     5000       36     12 |  0.000 % |
0.00/0.00	c ===============================================================================
0.00/0.00	c New solution: 12
0.00/0.00	o 12
0.00/0.00	c Elapsed CPU time: 0.006998 s	Remaining CPU time: 179.993 s
0.00/0.00	c ===============================================================================
0.00/0.00	c |        52 |      75      106     1650 |     5000       52     12 |  0.000 % |
0.00/0.00	c ===============================================================================
0.00/0.00	c New solution: 11
0.00/0.00	o 11
0.00/0.00	c Elapsed CPU time: 0.008998 s	Remaining CPU time: 179.991 s
0.00/0.00	c ===============================================================================
0.00/0.00	c |        75 |      68      107     1655 |     5000       75     12 |  0.000 % |
0.00/0.01	c ===============================================================================
0.00/0.01	c Best Solution: 11
0.00/0.01	s OPTIMUM FOUND
0.00/0.01	c Total CPU time: 0.010998 s
0.00/0.01	v x1 x2 -x3 x4 -x5 -x16 -x17 x18 -x19 -x20 x21 -x22 -x23 x24 -x25 -x75 x6 -x7 -x8 -x9 -x10 -x74 -x73 -x72 x71 x70 -x11 -x12 -x13 -x14 -x15 -x69 -x68 x67 -x66 x65 x64 x63 x62 x61 x60 x59 x58 x57 x56 -x55 -x54 x53 x52 -x51 x50 x49 x48 x47 x46 x45 x44 x43 x42 x41 x40 x39 x38 x37 x36 x35 x34 x33 x32 x31 x30 x29 x28 x27 x26

Verifier Data 

OK	11

Watcher Data 

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

command line: BIN/runsolver --timestamp -w /tmp/evaluation-result-2656227-1276583857/watcher-2656227-1276583857 -o /tmp/evaluation-result-2656227-1276583857/solver-2656227-1276583857 -C 1800 -W 2000 -M 1800 wbo1.4b -file-format=opb -time-limit=1800 HOME/instance-2656227-1276583857.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.02 1.00 3/106 1908
/proc/meminfo: memFree=1804740/2059040 swapFree=4134576/4192956
[pid=1908] ppid=1906 vsize=2572 CPUtime=0
/proc/1908/stat : 1908 (wbo1.4b) R 1906 1908 1033 0 -1 4202496 285 0 0 0 0 0 0 0 20 0 1 0 33972092 2633728 199 1992294400 134512640 135751879 4294585168 18446744073709551615 135270609 0 0 4096 3 0 0 0 17 1 0 0 0
/proc/1908/statm: 643 199 146 303 0 338 0

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

Child status: 0
Real time (s): 0.011925
CPU time (s): 0.012997
CPU user time (s): 0.010998
CPU system time (s): 0.001999
CPU usage (%): 108.989
Max. virtual memory (cumulated for all children) (KiB): 0

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

The end

Launcher Data 

Begin job on node017 at 2010-06-15 08:37:37
IDJOB=2656227
IDBENCH=2629
IDSOLVER=1161
FILE ID=node017/2656227-1276583857
PBS_JOBID= 11173528
Free space on /tmp= 62540 MiB

SOLVER NAME= wbo 1.4b
BENCH NAME= PB06/final/normalized-PB06/OPT-SMALLINT/submitted-PB06/manquiho/golomb-rulers/normalized-OGR_5.opb
COMMAND LINE= wbo1.4b -file-format=opb -time-limit=TIMEOUT BENCHNAME
RUNSOLVER COMMAND LINE= BIN/runsolver --timestamp -w /tmp/evaluation-result-2656227-1276583857/watcher-2656227-1276583857 -o /tmp/evaluation-result-2656227-1276583857/solver-2656227-1276583857 -C 1800 -W 2000 -M 1800  wbo1.4b -file-format=opb -time-limit=1800 HOME/instance-2656227-1276583857.opb

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

MD5SUM BENCH= f7ce1bbc714a6b404586716e62ae4fc9
RANDOM SEED=1824492570

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


/proc/meminfo:
MemTotal:      2059040 kB
MemFree:       1805144 kB
Buffers:         58172 kB
Cached:         115096 kB
SwapCached:      11648 kB
Active:         107572 kB
Inactive:        79672 kB
HighTotal:           0 kB
HighFree:            0 kB
LowTotal:      2059040 kB
LowFree:       1805144 kB
SwapTotal:     4192956 kB
SwapFree:      4134576 kB
Dirty:            2992 kB
Writeback:           0 kB
AnonPages:       12352 kB
Mapped:           9232 kB
Slab:            44888 kB
PageTables:       4060 kB
NFS_Unstable:        0 kB
Bounce:              0 kB
CommitLimit:   5222476 kB
Committed_AS:   183224 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= 62536 MiB
End job on node017 at 2010-06-15 08:37:37