Trace number 431080

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.442932 0.445647

General information on the benchmark

Namenormalized-PB07/OPT-SMALLINT-NLC/submittedPB07/roussel/
factor-mod-B/factor-mod-size=9-P0=271-P1=293-B.opb
MD5SUM2e3c7287841521f4043e8a0d4ae495d6
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.031994
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 variables27
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 constraint9
Maximum length of a constraint90
Number of terms in the objective function 9
Biggest coefficient in the objective function 256
Number of bits for the biggest coefficient in the objective function 9
Sum of the numbers in the objective function 511
Number of bits of the sum of numbers in the objective function 9
Biggest number in a constraint 131072
Number of bits of the biggest number in a constraint 18
Biggest sum of numbers in a constraint 522796
Number of bits of the biggest sum of numbers19
Number of products (including duplicates)81
Sum of products size (including duplicates)162
Number of different products81
Sum of products size162

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/431080-1178002617/instance-431080-1178002617.opb
0.00/0.00	c File size is 1584 bytes.
0.00/0.00	c Highest Coefficient sum: 522796
0.00/0.00	c Parsing was ok!!
0.00/0.00	c Total parsing time: 0 s
0.00/0.00	c Var: 108 Constr: 166 81/0/85 Lit: 684 Watch. Lit: 425
0.00/0.00	c Obj. Vars: 9 (8.33333 % of total variables)
0.00/0.00	c Pre-processing Time: 0.003 s
0.00/0.00	c    Confl   Vars     Ctrs     Lits  LPC   W.Lits     Max Learnt Conf/s Time
0.00/0.00	c        0    108      166      684    4      589     908      0      0 0.00
0.00/0.00	c Switching off LPR mode.
0.39/0.43	c      103    108      269     7220   26      785     999    103   8583 0.01
0.39/0.43	c      254    108      420    16621   39     1078    1099    254   9769 0.03
0.39/0.43	c      479    108      645    32216   49     1538    1209    479   9211 0.05
0.39/0.43	c      818    108      984    57621   58     2206    1330    818   8702 0.09
0.39/0.43	c     1326    108     1492    94337   63     3237    1464   1326   7577 0.17
0.39/0.43	c     2089    108     1465    96257   65     3135    1611   1299   7228 0.29
0.39/0.43	o 5	0.435
0.39/0.44	c    Confl   Vars     Ctrs     Lits  LPC   W.Lits     Max Learnt Conf/s Time
0.39/0.44	c     3133    108     1642   111020   67     3535     926   1476   7202 0.43
0.39/0.44	o 3	0.439
0.39/0.44	c    Confl   Vars     Ctrs     Lits  LPC   W.Lits     Max Learnt Conf/s Time
0.39/0.44	c     3143    108      641    34060   53     1537     926    475   7159 0.44
0.39/0.44	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
0.39/0.44	c  Rst    Confl    NCB      Dec     Ctrs     Lits Learnt Conf/s Time
0.39/0.44	c    8     3150     39     3568      648    34081    482   7159 0.44
0.39/0.44	c Objective: 3
0.39/0.44	s OPTIMUM FOUND
0.39/0.44	c Total time: 0.44 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/node33/watcher-431080-1178002617 -o ROOT/results/node33/solver-431080-1178002617 -C 1800 -W 3600 -M 1800 --output-limit 1,15 bsolo3.0.16 -t1800 -m1800 /tmp/evaluation/431080-1178002617/instance-431080-1178002617.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.78 0.95 0.98 3/77 30664
/proc/meminfo: memFree=1816592/2055920 swapFree=4147808/4192956
[pid=30664] ppid=30662 vsize=11740 CPUtime=0
/proc/30664/stat : 30664 (bsolo3.0.16) R 30662 30664 28595 0 -1 4194304 378 0 0 0 0 0 0 0 18 0 1 0 248177239 12021760 347 18446744073709551615 134512640 135841103 4294956672 18446744073709551615 11380347 0 0 4096 16384 0 0 0 17 1 0 0
/proc/30664/statm: 982 348 291 324 0 50 0

[startup+0.0800169 s]
/proc/loadavg: 0.78 0.95 0.98 3/77 30664
/proc/meminfo: memFree=1816592/2055920 swapFree=4147808/4192956
[pid=30664] ppid=30662 vsize=4696 CPUtime=0.07
/proc/30664/stat : 30664 (bsolo3.0.16) R 30662 30664 28595 0 -1 4194304 570 0 0 0 7 0 0 0 18 0 1 0 248177239 4808704 538 18446744073709551615 134512640 135841103 4294956672 18446744073709551615 4294960144 0 0 4096 16384 0 0 0 17 1 0 0
/proc/30664/statm: 1174 538 311 324 0 243 0
Current children cumulated CPU time (s) 0.07
Current children cumulated vsize (KiB) 4696

[startup+0.10102 s]
/proc/loadavg: 0.78 0.95 0.98 3/77 30664
/proc/meminfo: memFree=1816592/2055920 swapFree=4147808/4192956
[pid=30664] ppid=30662 vsize=4828 CPUtime=0.09
/proc/30664/stat : 30664 (bsolo3.0.16) R 30662 30664 28595 0 -1 4194304 616 0 0 0 9 0 0 0 18 0 1 0 248177239 4943872 584 18446744073709551615 134512640 135841103 4294956672 18446744073709551615 4294960144 0 0 4096 16384 0 0 0 17 1 0 0
/proc/30664/statm: 1207 584 311 324 0 276 0
Current children cumulated CPU time (s) 0.09
Current children cumulated vsize (KiB) 4828

[startup+0.301062 s]
/proc/loadavg: 0.78 0.95 0.98 3/77 30664
/proc/meminfo: memFree=1816592/2055920 swapFree=4147808/4192956
[pid=30664] ppid=30662 vsize=5600 CPUtime=0.29
/proc/30664/stat : 30664 (bsolo3.0.16) R 30662 30664 28595 0 -1 4194304 795 0 0 0 29 0 0 0 19 0 1 0 248177239 5734400 763 18446744073709551615 134512640 135841103 4294956672 18446744073709551615 4294960144 0 0 4096 16384 0 0 0 17 1 0 0
/proc/30664/statm: 1400 763 311 324 0 469 0
Current children cumulated CPU time (s) 0.29
Current children cumulated vsize (KiB) 5600

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

[startup+0.401083 s]
/proc/loadavg: 0.78 0.95 0.98 3/77 30664
/proc/meminfo: memFree=1816592/2055920 swapFree=4147808/4192956
[pid=30664] ppid=30662 vsize=5728 CPUtime=0.39
/proc/30664/stat : 30664 (bsolo3.0.16) R 30662 30664 28595 0 -1 4194304 849 0 0 0 39 0 0 0 19 0 1 0 248177239 5865472 817 18446744073709551615 134512640 135841103 4294956672 18446744073709551615 4294960144 0 0 4096 16384 0 0 0 17 1 0 0
/proc/30664/statm: 1432 817 311 324 0 501 0
Current children cumulated CPU time (s) 0.39
Current children cumulated vsize (KiB) 5728

Child status: 0
Real time (s): 0.445647
CPU time (s): 0.442932
CPU user time (s): 0.433934
CPU system time (s): 0.008998
CPU usage (%): 99.3908
Max. virtual memory (cumulated for all children) (KiB): 5728

getrusage(RUSAGE_CHILDREN,...) data:
user time used= 0.433934
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= 851
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 node33 on Tue May  1 06:56:58 UTC 2007

IDJOB= 431080
IDBENCH= 48026
IDSOLVER= 163
FILE ID= node33/431080-1178002617

PBS_JOBID= 4728246

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=9-P0=271-P1=293-B.opb
COMMAND LINE= bsolo3.0.16 -t1800 -m1800 /tmp/evaluation/431080-1178002617/instance-431080-1178002617.opb            
RUNSOLVER COMMAND LINE= runsolver  --timestamp  -w ROOT/results/node33/watcher-431080-1178002617 -o ROOT/results/node33/solver-431080-1178002617 -C 1800 -W 3600 -M 1800 --output-limit 1,15  bsolo3.0.16 -t1800 -m1800 /tmp/evaluation/431080-1178002617/instance-431080-1178002617.opb            

META MD5SUM SOLVER= b11bf0769a124f73ad50b0fdfcd50482
MD5SUM BENCH=  2e3c7287841521f4043e8a0d4ae495d6

RANDOM SEED= 349989129

TIME LIMIT= 1800 seconds
MEMORY LIMIT= 1800 MiB

Linux node33.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.272
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.272
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:       1817192 kB
Buffers:         48276 kB
Cached:         103540 kB
SwapCached:      13560 kB
Active:         107676 kB
Inactive:        68072 kB
HighTotal:           0 kB
HighFree:            0 kB
LowTotal:      2055920 kB
LowFree:       1817192 kB
SwapTotal:     4192956 kB
SwapFree:      4147808 kB
Dirty:            6776 kB
Writeback:           0 kB
Mapped:          30448 kB
Slab:            48360 kB
Committed_AS:  2637848 kB
PageTables:       1992 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 node33 on Tue May  1 06:56:58 UTC 2007