Trace number 454191

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, and are wall clock time (not CPU 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.0.17OPT-12 0.351945 0.355671

General information on the benchmark

Namenormalized-PB07/OPT-SMALLINT-NLC/submittedPB07/
manquinho/mis/normalized-mis_50_10_4.opb
MD5SUM3e57d3cba1755ede057d969ec9fbcff0
Bench CategoryOPT-SMALLINT-NLC (optimisation, small integers, non linear constraints)
Best result obtained on this benchmarkOPT
Best value of the objective obtained on this benchmark-12
Best CPU time to get the best result obtained on this benchmark0.158974
Has Objective FunctionYES
SatisfiableYES
(Un)Satisfiability was provedYES
Best value of the objective function -12
Optimality of the best value was proved YES
Number of variables50
Total number of constraints50
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 constraints50
Minimum length of a constraint10
Maximum length of a constraint16
Number of terms in the objective function 50
Biggest coefficient in the objective function 1
Number of bits for the biggest coefficient in the objective function 1
Sum of the numbers in the objective function 50
Number of bits of the sum of numbers in the objective function 6
Biggest number in a constraint 1
Number of bits of the biggest number in a constraint 1
Biggest sum of numbers in a constraint 50
Number of bits of the biggest sum of numbers6
Number of products (including duplicates)614
Sum of products size (including duplicates)1228
Number of different products307
Sum of products size614

Quality of the solution as a function of time


Download the above graph as a PDF file / as an EPS file

Solver Data (download as text)

0.00/0.00	c bsolo beta version 3.0.17 - 27/04/2007 : 1600 GMT
0.00/0.00	c Developed by Vasco Manquinho 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 Memory Limit set to 1800 MB
0.00/0.00	c Instance file /tmp/evaluation/454191-1178022499/instance-454191-1178022499.opb
0.00/0.00	c File size is 7362 bytes.
0.00/0.00	c Highest Coefficient sum: 50
0.00/0.00	c Parsing was ok!!
0.00/0.00	c Total parsing time: 0.003 s
0.00/0.00	c Var: 664 Constr: 1328 664/50/614 Lit: 4912 Watch. Lit: 3684
0.00/0.00	c Obj. Vars: 50 (7.53012 % of total variables)
0.00/0.01	c Pre-processing Time: 0.008 s
0.00/0.01	c    Confl   Vars     Ctrs     Lits  LPC   W.Lits     Max Learnt Conf/s Time
0.00/0.01	c        0     50      307      921    3      614     102      0      0 0.01
0.00/0.01	c Switching off LPR mode.
0.00/0.01	o -10	0.009
0.00/0.01	c    Confl   Vars     Ctrs     Lits  LPC   W.Lits     Max Learnt Conf/s Time
0.00/0.01	c        0     50      308      971    3      626     285      1      0 0.01
0.00/0.01	o -11	0.009
0.00/0.01	c    Confl   Vars     Ctrs     Lits  LPC   W.Lits     Max Learnt Conf/s Time
0.00/0.01	c       12     50      321     1459    4      663     302     14   1333 0.01
0.00/0.01	o -12	0.009
0.29/0.35	c    Confl   Vars     Ctrs     Lits  LPC   W.Lits     Max Learnt Conf/s Time
0.29/0.35	c       12     50      322     1509    4      677     318     15   1333 0.01
0.29/0.35	c      112     50      422     4929   11      877     350    115   8615 0.01
0.29/0.35	c      362     50      672    13365   19     1377     386    365  13923 0.03
0.29/0.35	c      839     50     1149    29431   25     2331     425    842  12712 0.07
0.29/0.35	c     1652     48     1110    27076   24     2230     468    803  13322 0.12
0.29/0.35	c     2972     43      700    11357   16     1405     515    393  13887 0.21
0.29/0.35	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
0.29/0.35	v x30 -x31 x32 x33 -x34 -x35 -x36 -x37 x38 -x39 -x40 x41 -x42 x43 -x44 -x45 x46 -x47 x48 -x49 -x50
0.29/0.35	c  Rst    Confl    NCB      Dec     Ctrs     Lits Learnt Conf/s Time
0.29/0.35	c    8     4619    203     4909     1464    26128   1157  13234 0.35
0.29/0.35	c Objective: -12
0.29/0.35	s OPTIMUM FOUND
0.29/0.35	c Total time: 0.349 s

Verifier Data (download as text)

OK	-12

Watcher Data (download as text)

runsolver version 3.2.3 (c) roussel@cril.univ-artois.fr

command line: runsolver --timestamp -w ROOT/results/node70/watcher-454191-1178022499 -o ROOT/results/node70/solver-454191-1178022499 -C 1800 -W 3600 -M 1800 --output-limit 1,15 bsolo3.0.17 -m1800 /tmp/evaluation/454191-1178022499/instance-454191-1178022499.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): 3600 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
Solver output will be limited to a maximum of 15728640 bytes. The first 1048576 bytes and the last 14680064 bytes will be preserved
Current StackSize limit: 10240 KiB


[startup+0 s]
/proc/loadavg: 1.05 1.03 1.00 3/64 5431
/proc/meminfo: memFree=1905728/2055920 swapFree=4183764/4192956
[pid=5431] ppid=5429 vsize=19556 CPUtime=0
/proc/5431/stat : 5431 (bsolo3.0.17) R 5429 5431 4891 0 -1 4194304 373 0 0 0 0 0 0 0 18 0 1 0 241787203 20025344 343 18446744073709551615 134512640 135840783 4294956688 18446744073709551615 8849019 0 0 4096 16384 0 0 0 17 1 0 0
/proc/5431/statm: 4889 344 289 324 0 3957 0

[startup+0.0599389 s]
/proc/loadavg: 1.05 1.03 1.00 3/64 5431
/proc/meminfo: memFree=1905728/2055920 swapFree=4183764/4192956
[pid=5431] ppid=5429 vsize=4464 CPUtime=0.05
/proc/5431/stat : 5431 (bsolo3.0.17) R 5429 5431 4891 0 -1 4194304 538 0 0 0 5 0 0 0 18 0 1 0 241787203 4571136 506 18446744073709551615 134512640 135840783 4294956688 18446744073709551615 134547799 0 0 4096 16384 0 0 0 17 1 0 0
/proc/5431/statm: 1116 506 311 324 0 186 0
Current children cumulated CPU time (s) 0.05
Current children cumulated vsize (KiB) 4464

[startup+0.101942 s]
/proc/loadavg: 1.05 1.03 1.00 3/64 5431
/proc/meminfo: memFree=1905728/2055920 swapFree=4183764/4192956
[pid=5431] ppid=5429 vsize=4724 CPUtime=0.09
/proc/5431/stat : 5431 (bsolo3.0.17) R 5429 5431 4891 0 -1 4194304 577 0 0 0 9 0 0 0 18 0 1 0 241787203 4837376 545 18446744073709551615 134512640 135840783 4294956688 18446744073709551615 134550904 0 0 4096 16384 0 0 0 17 1 0 0
/proc/5431/statm: 1181 545 311 324 0 251 0
Current children cumulated CPU time (s) 0.09
Current children cumulated vsize (KiB) 4724

[startup+0.301962 s]
/proc/loadavg: 1.05 1.03 1.00 3/64 5431
/proc/meminfo: memFree=1905728/2055920 swapFree=4183764/4192956
[pid=5431] ppid=5429 vsize=4724 CPUtime=0.29
/proc/5431/stat : 5431 (bsolo3.0.17) R 5429 5431 4891 0 -1 4194304 579 0 0 0 29 0 0 0 19 0 1 0 241787203 4837376 547 18446744073709551615 134512640 135840783 4294956688 18446744073709551615 134550893 0 0 4096 16384 0 0 0 17 1 0 0
/proc/5431/statm: 1181 547 311 324 0 251 0
Current children cumulated CPU time (s) 0.29
Current children cumulated vsize (KiB) 4724

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

Child status: 0
Real time (s): 0.355671
CPU time (s): 0.351945
CPU user time (s): 0.349946
CPU system time (s): 0.001999
CPU usage (%): 98.9524
Max. virtual memory (cumulated for all children) (KiB): 4724

getrusage(RUSAGE_CHILDREN,...) data:
user time used= 0.349946
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= 583
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= 12
involuntary context switches= 0

runsolver used 0.003999 second user time and 0.003999 second system time

The end

Launcher Data (download as text)

Begin job on node70 on Tue May  1 12:28:19 UTC 2007

IDJOB= 454191
IDBENCH= 48180
IDSOLVER= 199
FILE ID= node70/454191-1178022499

PBS_JOBID= 4728334

Free space on /tmp= 66558 MiB

SOLVER NAME= bsolo 3.0.17
BENCH NAME= HOME/pub/bench/PB07/normalized-PB07/OPT-SMALLINT-NLC/submittedPB07/manquinho/mis/normalized-mis_50_10_4.opb
COMMAND LINE= bsolo3.0.17 -m1800 /tmp/evaluation/454191-1178022499/instance-454191-1178022499.opb            
RUNSOLVER COMMAND LINE= runsolver  --timestamp  -w ROOT/results/node70/watcher-454191-1178022499 -o ROOT/results/node70/solver-454191-1178022499 -C 1800 -W 3600 -M 1800 --output-limit 1,15  bsolo3.0.17 -m1800 /tmp/evaluation/454191-1178022499/instance-454191-1178022499.opb            

META MD5SUM SOLVER= c9b15312c639dd71a11a1e3ca1b27020
MD5SUM BENCH=  3e57d3cba1755ede057d969ec9fbcff0

RANDOM SEED= 354081737

TIME LIMIT= 1800 seconds
MEMORY LIMIT= 1800 MiB

Linux node70.alineos.net 2.6.9-22.EL.rootsmp #1 SMP Mon Oct 3 08:59:52 CEST 2005 x86_64 x86_64 x86_64 GNU/Linux

/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.218
cache size	: 2048 KB
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 pni monitor ds_cpl cid cx16 xtpr
bogomips	: 5914.62
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.218
cache size	: 2048 KB
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 pni monitor ds_cpl cid cx16 xtpr
bogomips	: 5586.94
clflush size	: 64
cache_alignment	: 128
address sizes	: 36 bits physical, 48 bits virtual
power management:


/proc/meminfo:
MemTotal:      2055920 kB
MemFree:       1906136 kB
Buffers:          5256 kB
Cached:          67684 kB
SwapCached:       2948 kB
Active:          57152 kB
Inactive:        28396 kB
HighTotal:           0 kB
HighFree:            0 kB
LowTotal:      2055920 kB
LowFree:       1906136 kB
SwapTotal:     4192956 kB
SwapFree:      4183764 kB
Dirty:            6608 kB
Writeback:           0 kB
Mapped:          18500 kB
Slab:            50240 kB
Committed_AS:  4334688 kB
PageTables:       1404 kB
VmallocTotal: 536870911 kB
VmallocUsed:    264952 kB
VmallocChunk: 536605679 kB
HugePages_Total:     0
HugePages_Free:      0
Hugepagesize:     2048 kB

Free space on /tmp at the end= 66558 MiB

End job on node70 on Tue May  1 12:28:19 UTC 2007