Trace number 2670668

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 ClOPT3 0.027995 0.027548

General information on the benchmark

Namenormalized-PB07/OPT-SMALLINT-NLC/submittedPB07/roussel/
factor-mod-B/factor-mod-size=6-P0=59-P1=29-B.opb
MD5SUM2136726fbb803f220f38b254700007d3
Bench CategoryOPT-SMALLINT-NLC (optimisation, small integers, non linear constraints)
Best result obtained on this benchmarkOPT
Best value of the objective obtained on this benchmark3
Best CPU time to get the best result obtained on this benchmark0.027995
Has Objective FunctionYES
SatisfiableYES
(Un)Satisfiability was provedYES
Best value of the objective function 3
Optimality of the best value was proved YES
Number of variables18
Total number of constraints3
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 constraints3
Minimum length of a constraint6
Maximum length of a constraint42
Number of terms in the objective function 6
Biggest coefficient in the objective function 32
Number of bits for the biggest coefficient in the objective function 6
Sum of the numbers in the objective function 63
Number of bits of the sum of numbers in the objective function 6
Biggest number in a constraint 2048
Number of bits of the biggest number in a constraint 12
Biggest sum of numbers in a constraint 8048
Number of bits of the biggest sum of numbers13
Number of products (including duplicates)36
Sum of products size (including duplicates)72
Number of different products36
Sum of products size72

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-2670668-1276704130.opb
0.00/0.00	c File size is 2626 bytes.
0.00/0.00	c Highest Coefficient sum: 8048
0.00/0.00	c Parsing was ok!!
0.00/0.00	c Total parsing time: 0 s
0.00/0.00	c Var: 54 Constr: 76 36/0/40 Lit: 312 Watch. Lit: 200
0.00/0.00	c Obj. Vars: 6 (11.1111 % of total variables)
0.00/0.00	c Pre-processing Time: 0 s
0.00/0.00	c    Confl   Vars     Ctrs     Lits  LPC   W.Lits     Max Learnt Conf/s Time
0.00/0.00	c        0     54       76      312    4      268     419      0      0 0.00
0.00/0.00	c Switching off lower bounding mode.
0.00/0.02	c      101     54      177     3095   17      462     461    101  14428 0.01
0.00/0.02	c      251     54      327     7651   23      768     508    251  13944 0.02
0.00/0.02	o 25
0.00/0.02	c    Confl   Vars     Ctrs     Lits  LPC   W.Lits     Max Learnt Conf/s Time
0.00/0.02	c      332     54      409    10221   24      937     431    333  13833 0.02
0.00/0.02	o 7
0.00/0.02	c    Confl   Vars     Ctrs     Lits  LPC   W.Lits     Max Learnt Conf/s Time
0.00/0.02	c      341     54      419    10474   24      962     431    343  14208 0.02
0.00/0.02	o 3
0.00/0.02	c    Confl   Vars     Ctrs     Lits  LPC   W.Lits     Max Learnt Conf/s Time
0.00/0.02	c      348     27      427    10519   24      961     423    351  13920 0.03
0.00/0.02	v x1 x2 -x3 -x4 -x5 -x6 x7 -x8 x9 -x10 -x11 x12 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 x13 -x14 -x15 -x16 -x17 -x18 
0.00/0.02	c  Rst    Confl    NCB      Dec     Ctrs     Lits Learnt Conf/s Time
0.00/0.02	c    5      349      8      437      428    10520    352  13960 0.03
0.00/0.02	c Objective: 3
0.00/0.02	s OPTIMUM FOUND
0.00/0.02	c Total time: 0.025 s

Verifier Data 

OK	3

Watcher Data 

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

command line: BIN/runsolver --timestamp -w /tmp/evaluation-result-2670668-1276704130/watcher-2670668-1276704130 -o /tmp/evaluation-result-2670668-1276704130/solver-2670668-1276704130 -C 1800 -W 2000 -M 1800 bsolo_pb10 -t1800 -l1 HOME/instance-2670668-1276704130.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 1.00 3/106 17318
/proc/meminfo: memFree=1814284/2059040 swapFree=4140124/4192956
[pid=17318] ppid=17316 vsize=18600 CPUtime=0
/proc/17318/stat : 17318 (bsolo_pb10) R 17316 17318 16765 0 -1 4202496 327 0 0 0 0 0 0 0 18 0 1 0 11705508 19046400 244 1992294400 134512640 137138936 4287783952 18446744073709551615 136570369 0 0 4096 16384 0 0 0 17 1 0 0 0
/proc/17318/statm: 4650 244 190 642 0 4006 0

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

Child status: 0
Real time (s): 0.027548
CPU time (s): 0.027995
CPU user time (s): 0.024996
CPU system time (s): 0.002999
CPU usage (%): 101.623
Max. virtual memory (cumulated for all children) (KiB): 0

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

The end

Launcher Data 

Begin job on node042 at 2010-06-16 18:02:10
IDJOB=2670668
IDBENCH=48050
IDSOLVER=1163
FILE ID=node042/2670668-1276704130
PBS_JOBID= 11174101
Free space on /tmp= 62580 MiB

SOLVER NAME= bsolo 3.2 Cl
BENCH NAME= PB07/normalized-PB07/OPT-SMALLINT-NLC/submittedPB07/roussel/factor-mod-B/factor-mod-size=6-P0=59-P1=29-B.opb
COMMAND LINE= bsolo_pb10 -tTIMEOUT -l1 BENCHNAME
CONVERSION SCRIPT= PBconversionToLinear BENCHNAME
RUNSOLVER COMMAND LINE= BIN/runsolver --timestamp -w /tmp/evaluation-result-2670668-1276704130/watcher-2670668-1276704130 -o /tmp/evaluation-result-2670668-1276704130/solver-2670668-1276704130 -C 1800 -W 2000 -M 1800  bsolo_pb10 -t1800 -l1 HOME/instance-2670668-1276704130.opb

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

MD5SUM BENCH= 2136726fbb803f220f38b254700007d3
RANDOM SEED=1733940622

node042.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.213
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.42
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.213
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:       1814936 kB
Buffers:         44904 kB
Cached:         119960 kB
SwapCached:       6424 kB
Active:          85476 kB
Inactive:        92500 kB
HighTotal:           0 kB
HighFree:            0 kB
LowTotal:      2059040 kB
LowFree:       1814936 kB
SwapTotal:     4192956 kB
SwapFree:      4140124 kB
Dirty:            3868 kB
Writeback:           0 kB
AnonPages:       10720 kB
Mapped:          13020 kB
Slab:            44304 kB
PageTables:       3976 kB
NFS_Unstable:        0 kB
Bounce:              0 kB
CommitLimit:   5222476 kB
Committed_AS:   183988 kB
VmallocTotal: 34359738367 kB
VmallocUsed:    264948 kB
VmallocChunk: 34359471699 kB
HugePages_Total:     0
HugePages_Free:      0
HugePages_Rsvd:      0
Hugepagesize:     2048 kB

CONVERSION COMMAND LINE= PBconversionToLinear HOME/instance-2670668-1276704130.opb

Free space on /tmp at the end= 62576 MiB
End job on node042 at 2010-06-16 18:02:10