Trace number 2696562

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_cplex 2010-06-29OPT6 0.05599 0.057157

General information on the benchmark

Namenormalized-PB06/OPT-SMALLINT/
submitted-PB06/manquiho/golomb-rulers/normalized-OGR_4.opb
MD5SUM8b1fbd52a1a4f2762439b4bdacc06a04
Bench CategoryOPT-SMALLINT (optimisation, small integers)
Best result obtained on this benchmarkOPT
Best value of the objective obtained on this benchmark6
Best CPU time to get the best result obtained on this benchmark0.003999
Has Objective FunctionYES
SatisfiableYES
(Un)Satisfiability was provedYES
Best value of the objective function 6
Optimality of the best value was proved YES
Number of variables40
Total number of constraints43
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 constraints43
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 155
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

Solver Data 

0.00/0.00	c pb_cplex 1.0 - 20100701
0.00/0.00	c Parsing opb file format. File HOME/instance-2696562-1278019838.opb.
0.00/0.00	c Instance file HOME/instance-2696562-1278019838.opb
0.00/0.00	c File size is 4895 bytes.
0.00/0.00	c Highest Coefficient sum: 155
0.00/0.00	c  IBM ILOG License Manager: "IBM ILOG Optimization Suite for Academic Initiative" is accessing CPLEX 12 with option(s): "e m b q ".
0.00/0.01	c ============================[ Problem Statistics ]=============================
0.00/0.01	c |                                                                             |
0.00/0.01	c |  Parsing time:          0.00         s                                      |
0.00/0.01	c |  Number Variables:      40                                                  |
0.00/0.01	c |  Number Constraints:    43                                                  |
0.00/0.01	c ===============================================================================
0.00/0.05	c Remaining time 1800.00 sec.
0.00/0.05	s OPTIMUM FOUND
0.00/0.05	c Solution value = 6.00
0.00/0.05	v -x1 x2 x3 -x4 -x5 -x6 x7 -x8 -x9 -x10 x16 -x17 x18 -x19 -x20 -x40 -x11 -x12 -x13 -x14 -x15 -x39 -x38 -x37 x36 x35 -x34 -x33 x32 -x31 x30 x29 x28 x27 x26 x25 x24 x23 x22 x21
0.00/0.05	c Total CPU time              : 0.046992 s

Verifier Data 

OK	6

Watcher Data 

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

command line: BIN/runsolver --timestamp -w /tmp/evaluation-result-2696562-1278019838/watcher-2696562-1278019838 -o /tmp/evaluation-result-2696562-1278019838/solver-2696562-1278019838 -C 1800 -W 2000 -M 1800 run HOME/instance-2696562-1278019838.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.70 1.82 1.70 3/106 29020
/proc/meminfo: memFree=1414056/2059040 swapFree=4135380/4192956
[pid=29020] ppid=29018 vsize=8700 CPUtime=0
/proc/29020/stat : 29020 (run) S 29018 29020 28616 0 -1 4202496 365 0 0 0 0 0 0 0 18 0 1 0 177585405 8908800 249 1992294400 4194304 4922060 140733453736272 18446744073709551615 223060008069 0 65536 4100 65538 18446744071562232103 0 0 17 1 0 0 0
/proc/29020/statm: 2175 249 208 178 0 68 0

[startup+0.0468649 s]
/proc/loadavg: 1.70 1.82 1.70 3/106 29020
/proc/meminfo: memFree=1414056/2059040 swapFree=4135380/4192956
[pid=29020] ppid=29018 vsize=8700 CPUtime=0
/proc/29020/stat : 29020 (run) S 29018 29020 28616 0 -1 4202496 365 0 0 0 0 0 0 0 18 0 1 0 177585405 8908800 249 1992294400 4194304 4922060 140733453736272 18446744073709551615 223060008069 0 65536 4100 65538 18446744071562232103 0 0 17 1 0 0 0
/proc/29020/statm: 2175 249 208 178 0 68 0
Current children cumulated CPU time (s) 0
Current children cumulated vsize (KiB) 8700

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

[startup+0.0468649 s]
/proc/loadavg: 1.70 1.82 1.70 3/106 29020
/proc/meminfo: memFree=1414056/2059040 swapFree=4135380/4192956
[pid=29020] ppid=29018 vsize=8700 CPUtime=0
/proc/29020/stat : 29020 (run) S 29018 29020 28616 0 -1 4202496 365 0 0 0 0 0 0 0 18 0 1 0 177585405 8908800 249 1992294400 4194304 4922060 140733453736272 18446744073709551615 223060008069 0 65536 4100 65538 18446744071562232103 0 0 17 1 0 0 0
/proc/29020/statm: 2175 249 208 178 0 68 0
Current children cumulated CPU time (s) 0
Current children cumulated vsize (KiB) 8700

Child status: 0
Real time (s): 0.057157
CPU time (s): 0.05599
CPU user time (s): 0.046992
CPU system time (s): 0.008998
CPU usage (%): 97.9582
Max. virtual memory (cumulated for all children) (KiB): 8700

getrusage(RUSAGE_CHILDREN,...) data:
user time used= 0.046992
system time used= 0.008998
maximum resident set size= 0
integral shared memory size= 0
integral unshared data size= 0
integral unshared stack size= 0
page reclaims= 2078
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= 69
involuntary context switches= 4

runsolver used 0.003999 second user time and 0.010998 second system time

The end

Launcher Data 

Begin job on node011 at 2010-07-01 23:30:38
IDJOB=2696562
IDBENCH=2638
IDSOLVER=1209
FILE ID=node011/2696562-1278019838
PBS_JOBID= 11198744
Free space on /tmp= 62284 MiB

SOLVER NAME= pb_cplex 2010-06-29
BENCH NAME= PB06/final/normalized-PB06/OPT-SMALLINT/submitted-PB06/manquiho/golomb-rulers/normalized-OGR_4.opb
COMMAND LINE= run BENCHNAME
RUNSOLVER COMMAND LINE= BIN/runsolver --timestamp -w /tmp/evaluation-result-2696562-1278019838/watcher-2696562-1278019838 -o /tmp/evaluation-result-2696562-1278019838/solver-2696562-1278019838 -C 1800 -W 2000 -M 1800  run HOME/instance-2696562-1278019838.opb

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

MD5SUM BENCH= 8b1fbd52a1a4f2762439b4bdacc06a04
RANDOM SEED=1603586955

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


/proc/meminfo:
MemTotal:      2059040 kB
MemFree:       1414460 kB
Buffers:        152444 kB
Cached:         381324 kB
SwapCached:      10780 kB
Active:         228544 kB
Inactive:       319108 kB
HighTotal:           0 kB
HighFree:            0 kB
LowTotal:      2059040 kB
LowFree:       1414460 kB
SwapTotal:     4192956 kB
SwapFree:      4135380 kB
Dirty:           16636 kB
Writeback:           0 kB
AnonPages:       12340 kB
Mapped:           8552 kB
Slab:            74952 kB
PageTables:       4188 kB
NFS_Unstable:        0 kB
Bounce:              0 kB
CommitLimit:   5222476 kB
Committed_AS:   183108 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= 62268 MiB
End job on node011 at 2010-07-01 23:30:39