Trace number 2657242

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
bsolo 3.2 ClOPT3951 0.037994 0.0387981

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 bsolo beta version 3.2 - 23/05/2010 : 1630 GMT
0.00/0.00	c Developed by Vasco Manquinho and José Santos IST/UTL - INESC-ID
0.00/0.00	c type "bsolo -h" for help
0.00/0.00	c Time Limit set via environment variable PBTIMEOUT to 1800
0.00/0.00	c Time Limit set to 1800
0.00/0.00	c Learning Strategy: Clause Learning
0.00/0.00	c Instance file HOME/instance-2657242-1276629801.opb
0.00/0.00	c File size is 2131 bytes.
0.00/0.00	c Highest Coefficient sum: 25669
0.00/0.00	c Parsing was ok!!
0.00/0.00	c Total parsing time: 0 s
0.00/0.00	c Var: 55 Constr: 70 60/10/0 Lit: 200 Watch. Lit: 170
0.00/0.00	c Obj. Vars: 55 (100 % of total variables)
0.00/0.00	c Pre-processing Time: 0.001 s
0.00/0.00	c    Confl   Vars     Ctrs     Lits  LPC   W.Lits     Max Learnt Conf/s Time
0.00/0.00	c        0     55       70      200    2      170      86      0      0 0.00
0.00/0.00	c Switching off lower bounding mode.
0.00/0.00	o 5444
0.00/0.00	c    Confl   Vars     Ctrs     Lits  LPC   W.Lits     Max Learnt Conf/s Time
0.00/0.00	c        0     55       71      255    3      218     196      1      0 0.00
0.00/0.00	o 4066
0.00/0.00	c    Confl   Vars     Ctrs     Lits  LPC   W.Lits     Max Learnt Conf/s Time
0.00/0.00	c       33     55      105      803    7      329     196     35  16500 0.00
0.00/0.00	o 4018
0.00/0.03	c    Confl   Vars     Ctrs     Lits  LPC   W.Lits     Max Learnt Conf/s Time
0.00/0.03	c       89     55      162     1633   10      491     196     92  22250 0.00
0.00/0.03	c      190     55      263     3517   13      699     216    193  17272 0.01
0.00/0.03	c      441     55      260     2307    8      599     238    190  18375 0.02
0.00/0.03	o 3996
0.00/0.03	c    Confl   Vars     Ctrs     Lits  LPC   W.Lits     Max Learnt Conf/s Time
0.00/0.03	c      619     53      302     2379    7      725     192    232  18205 0.03
0.00/0.03	o 3951
0.00/0.03	c    Confl   Vars     Ctrs     Lits  LPC   W.Lits     Max Learnt Conf/s Time
0.00/0.03	c      683     19      235     1534    6      555     124    165  18459 0.04
0.00/0.03	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 
0.00/0.03	c  Rst    Confl    NCB      Dec     Ctrs     Lits Learnt Conf/s Time
0.00/0.03	c    7      686     81      857      150      748     80  18540 0.04
0.00/0.03	c Objective: 3951
0.00/0.03	s OPTIMUM FOUND
0.00/0.03	c Total time: 0.037 s

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-2657242-1276629801/watcher-2657242-1276629801 -o /tmp/evaluation-result-2657242-1276629801/solver-2657242-1276629801 -C 1800 -W 2000 -M 1800 bsolo_pb10 -t1800 -l1 HOME/instance-2657242-1276629801.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 4490
/proc/meminfo: memFree=1844540/2059040 swapFree=4140108/4192956
[pid=4490] ppid=4488 vsize=18600 CPUtime=0
/proc/4490/stat : 4490 (bsolo_pb10) R 4488 4490 4047 0 -1 4202496 327 0 0 0 0 0 0 0 20 0 1 0 36635814 19046400 244 1992294400 134512640 137138936 4290993664 18446744073709551615 136570369 0 0 4096 16384 0 0 0 17 1 0 0 0
/proc/4490/statm: 4650 244 191 642 0 4006 0

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

Child status: 0
Real time (s): 0.0387981
CPU time (s): 0.037994
CPU user time (s): 0.037994
CPU system time (s): 0
CPU usage (%): 97.9275
Max. virtual memory (cumulated for all children) (KiB): 0

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

The end

Launcher Data 

Begin job on node025 at 2010-06-15 21:23:21
IDJOB=2657242
IDBENCH=24968
IDSOLVER=1163
FILE ID=node025/2657242-1276629801
PBS_JOBID= 11172360
Free space on /tmp= 62580 MiB

SOLVER NAME= bsolo 3.2 Cl
BENCH NAME= PB07/normalized-PB07/OPT-SMALLINT-LIN/submittedPB07/poldner/PB/testset/normalized-5_10.opb
COMMAND LINE= bsolo_pb10 -tTIMEOUT -l1 BENCHNAME
RUNSOLVER COMMAND LINE= BIN/runsolver --timestamp -w /tmp/evaluation-result-2657242-1276629801/watcher-2657242-1276629801 -o /tmp/evaluation-result-2657242-1276629801/solver-2657242-1276629801 -C 1800 -W 2000 -M 1800  bsolo_pb10 -t1800 -l1 HOME/instance-2657242-1276629801.opb

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

MD5SUM BENCH= ba69a176dcc33e2f7eda6b169d4d1c84
RANDOM SEED=2000698190

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:       1844936 kB
Buffers:         21628 kB
Cached:         103848 kB
SwapCached:       7140 kB
Active:          49308 kB
Inactive:        90392 kB
HighTotal:           0 kB
HighFree:            0 kB
LowTotal:      2059040 kB
LowFree:       1844936 kB
SwapTotal:     4192956 kB
SwapFree:      4140108 kB
Dirty:            4296 kB
Writeback:           0 kB
AnonPages:       11864 kB
Mapped:          13060 kB
Slab:            52496 kB
PageTables:       4112 kB
NFS_Unstable:        0 kB
Bounce:              0 kB
CommitLimit:   5222476 kB
Committed_AS:   181916 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= 62576 MiB
End job on node025 at 2010-06-15 21:23:21