Trace number 430492

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.16OPT3 0.503922 0.50543

General information on the benchmark

Namenormalized-PB07/OPT-SMALLINT-NLC/submittedPB07/roussel/
factor-mod-B/factor-mod-size=8-P0=179-P1=37-B.opb
MD5SUM7c55947c8932da669a6320e0df24c1e1
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.024996
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 variables24
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 constraint8
Maximum length of a constraint72
Number of terms in the objective function 8
Biggest coefficient in the objective function 128
Number of bits for the biggest coefficient in the objective function 8
Sum of the numbers in the objective function 255
Number of bits of the sum of numbers in the objective function 8
Biggest number in a constraint 32768
Number of bits of the biggest number in a constraint 16
Biggest sum of numbers in a constraint 130528
Number of bits of the biggest sum of numbers17
Number of products (including duplicates)64
Sum of products size (including duplicates)128
Number of different products64
Sum of products size128

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.16 - 04/04/2007 : 1458 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 Time Limit set to 1800
0.00/0.00	c Memory Limit set to 1800 MB
0.00/0.00	c Instance file /tmp/evaluation/430492-1177995839/instance-430492-1177995839.opb
0.00/0.00	c File size is 1316 bytes.
0.00/0.00	c Highest Coefficient sum: 130528
0.00/0.00	c Parsing was ok!!
0.00/0.00	c Total parsing time: 0 s
0.00/0.00	c Var: 88 Constr: 132 64/0/68 Lit: 544 Watch. Lit: 340
0.00/0.00	c Obj. Vars: 8 (9.09091 % 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     88      132      544    4      468     725      0      0 0.00
0.00/0.00	c Switching off LPR mode.
0.39/0.49	c      100     88      232     5491   23      658     798    100  12500 0.01
0.39/0.49	c      250     88      382    13373   35      958     878    250  12500 0.02
0.39/0.49	c      475     88      607    26191   43     1407     966    475  11585 0.04
0.39/0.49	c      814     88      946    45667   48     2087    1063    814  10049 0.08
0.39/0.49	c     1322     88      860    41887   48     1915    1170    728   9054 0.15
0.39/0.49	c     2085     88      972    48785   50     2143    1288    840   8760 0.24
0.39/0.49	c     3232     88      777    36228   46     1753    1417    645   8039 0.40
0.39/0.49	o 133	0.492
0.49/0.50	c    Confl   Vars     Ctrs     Lits  LPC   W.Lits     Max Learnt Conf/s Time
0.49/0.50	c     4057     88      862    45343   52     1918     741    730   8245 0.49
0.49/0.50	o 3	0.497
0.49/0.50	c    Confl   Vars     Ctrs     Lits  LPC   W.Lits     Max Learnt Conf/s Time
0.49/0.50	c     4101     88      504    23093   45     1202     741    372   8234 0.50
0.49/0.50	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
0.49/0.50	c  Rst    Confl    NCB      Dec     Ctrs     Lits Learnt Conf/s Time
0.49/0.50	c    9     4107     22     4379      510    23099    378   8230 0.50
0.49/0.50	c Objective: 3
0.49/0.50	s OPTIMUM FOUND
0.49/0.50	c Total time: 0.499 s

Verifier Data (download as text)

OK	3

Watcher Data (download as text)

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

command line: runsolver --timestamp -w ROOT/results/node34/watcher-430492-1177995839 -o ROOT/results/node34/solver-430492-1177995839 -C 1800 -W 3600 -M 1800 --output-limit 1,15 bsolo3.0.16 -t1800 -m1800 /tmp/evaluation/430492-1177995839/instance-430492-1177995839.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: 0.85 0.97 0.97 3/77 10693
/proc/meminfo: memFree=1775648/2055920 swapFree=4159588/4192956
[pid=10693] ppid=10691 vsize=11736 CPUtime=0
/proc/10693/stat : 10693 (bsolo3.0.16) R 10691 10693 9508 0 -1 4194304 386 0 0 0 0 0 0 0 18 0 1 0 247499311 12017664 355 18446744073709551615 134512640 135841103 4294956672 18446744073709551615 8182907 0 0 4096 16384 0 0 0 17 1 0 0
/proc/10693/statm: 2934 357 301 324 0 2003 0

[startup+0.011792 s]
/proc/loadavg: 0.85 0.97 0.97 3/77 10693
/proc/meminfo: memFree=1775648/2055920 swapFree=4159588/4192956
[pid=10693] ppid=10691 vsize=11868 CPUtime=0
/proc/10693/stat : 10693 (bsolo3.0.16) R 10691 10693 9508 0 -1 4194304 420 0 0 0 0 0 0 0 18 0 1 0 247499311 12152832 388 18446744073709551615 134512640 135841103 4294956672 18446744073709551615 4294960144 0 0 4096 16384 0 0 0 17 1 0 0
/proc/10693/statm: 2967 389 311 324 0 2036 0
Current children cumulated CPU time (s) 0
Current children cumulated vsize (KiB) 11868

[startup+0.1018 s]
/proc/loadavg: 0.85 0.97 0.97 3/77 10693
/proc/meminfo: memFree=1775648/2055920 swapFree=4159588/4192956
[pid=10693] ppid=10691 vsize=12516 CPUtime=0.09
/proc/10693/stat : 10693 (bsolo3.0.16) R 10691 10693 9508 0 -1 4194304 600 0 0 0 9 0 0 0 18 0 1 0 247499311 12816384 568 18446744073709551615 134512640 135841103 4294956672 18446744073709551615 4294960144 0 0 4096 16384 0 0 0 17 1 0 0
/proc/10693/statm: 3129 568 311 324 0 2198 0
Current children cumulated CPU time (s) 0.09
Current children cumulated vsize (KiB) 12516

[startup+0.301815 s]
/proc/loadavg: 0.85 0.97 0.97 3/77 10693
/proc/meminfo: memFree=1775648/2055920 swapFree=4159588/4192956
[pid=10693] ppid=10691 vsize=12900 CPUtime=0.29
/proc/10693/stat : 10693 (bsolo3.0.16) R 10691 10693 9508 0 -1 4194304 679 0 0 0 29 0 0 0 19 0 1 0 247499311 13209600 647 18446744073709551615 134512640 135841103 4294956672 18446744073709551615 4294960144 0 0 4096 16384 0 0 0 17 1 0 0
/proc/10693/statm: 3225 647 311 324 0 2294 0
Current children cumulated CPU time (s) 0.29
Current children cumulated vsize (KiB) 12900

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

[startup+0.501831 s]
/proc/loadavg: 0.85 0.97 0.97 3/77 10693
/proc/meminfo: memFree=1775648/2055920 swapFree=4159588/4192956
[pid=10693] ppid=10691 vsize=13028 CPUtime=0.49
/proc/10693/stat : 10693 (bsolo3.0.16) R 10691 10693 9508 0 -1 4194304 719 0 0 0 49 0 0 0 20 0 1 0 247499311 13340672 687 18446744073709551615 134512640 135841103 4294956672 18446744073709551615 4294960144 0 0 4096 16384 0 0 0 17 1 0 0
/proc/10693/statm: 3257 687 312 324 0 2326 0
Current children cumulated CPU time (s) 0.49
Current children cumulated vsize (KiB) 13028

Child status: 0
Real time (s): 0.50543
CPU time (s): 0.503922
CPU user time (s): 0.495924
CPU system time (s): 0.007998
CPU usage (%): 99.7017
Max. virtual memory (cumulated for all children) (KiB): 13028

getrusage(RUSAGE_CHILDREN,...) data:
user time used= 0.495924
system time used= 0.007998
maximum resident set size= 0
integral shared memory size= 0
integral unshared data size= 0
integral unshared stack size= 0
page reclaims= 720
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.001999 second user time and 0.006998 second system time

The end

Launcher Data (download as text)

Begin job on node34 on Tue May  1 05:03:59 UTC 2007

IDJOB= 430492
IDBENCH= 47984
IDSOLVER= 163
FILE ID= node34/430492-1177995839

PBS_JOBID= 4728208

Free space on /tmp= 66558 MiB

SOLVER NAME= bsolo 3.0.16
BENCH NAME= HOME/pub/bench/PB07/normalized-PB07/OPT-SMALLINT-NLC/submittedPB07/roussel/factor-mod-B/factor-mod-size=8-P0=179-P1=37-B.opb
COMMAND LINE= bsolo3.0.16 -t1800 -m1800 /tmp/evaluation/430492-1177995839/instance-430492-1177995839.opb            
RUNSOLVER COMMAND LINE= runsolver  --timestamp  -w ROOT/results/node34/watcher-430492-1177995839 -o ROOT/results/node34/solver-430492-1177995839 -C 1800 -W 3600 -M 1800 --output-limit 1,15  bsolo3.0.16 -t1800 -m1800 /tmp/evaluation/430492-1177995839/instance-430492-1177995839.opb            

META MD5SUM SOLVER= b11bf0769a124f73ad50b0fdfcd50482
MD5SUM BENCH=  7c55947c8932da669a6320e0df24c1e1

RANDOM SEED= 625635606

TIME LIMIT= 1800 seconds
MEMORY LIMIT= 1800 MiB

Linux node34.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.236
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.236
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:       1776056 kB
Buffers:         33052 kB
Cached:         158424 kB
SwapCached:       3140 kB
Active:          95404 kB
Inactive:       119776 kB
HighTotal:           0 kB
HighFree:            0 kB
LowTotal:      2055920 kB
LowFree:       1776056 kB
SwapTotal:     4192956 kB
SwapFree:      4159588 kB
Dirty:            6772 kB
Writeback:           0 kB
Mapped:          30352 kB
Slab:            49980 kB
Committed_AS:  1814316 kB
PageTables:       1976 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 node34 on Tue May  1 05:03:59 UTC 2007