Trace number 433291

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.17UNSAT 1.48177 1.48365

General information on the benchmark

Namenormalized-PB06/OPT-BIGINT/mps-v2-20-10/ftp.netlib.org/
lp/data/normalized-mps-v2-20-10-bnl2.opb
MD5SUM1aac4473a72704481ef90ef3ff1598a7
Bench CategoryOPT-BIGINT (optimisation, big integers)
Best result obtained on this benchmarkUNSAT
Best value of the objective obtained on this benchmark
Best CPU time to get the best result obtained on this benchmark1.48177
Has Objective FunctionYES
SatisfiableNO
(Un)Satisfiability was provedYES
Best value of the objective function
Optimality of the best value was proved
Number of variables104670
Total number of constraints2262
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 constraints2262
Minimum length of a constraint30
Maximum length of a constraint2460
Number of terms in the objective function 50550
Biggest coefficient in the objective function 322444669747200
Number of bits for the biggest coefficient in the objective function 49
Sum of the numbers in the objective function 11314136774293353
Number of bits of the sum of numbers in the objective function 54
Biggest number in a constraint 322444669747200
Number of bits of the biggest number in a constraint 49
Biggest sum of numbers in a constraint 11314136774293353
Number of bits of the biggest sum of numbers54
Number of products (including duplicates)0
Sum of products size (including duplicates)0
Number of different products0
Sum of products size0

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/433291-1177957381/instance-433291-1177957381.opb
0.00/0.00	c File size is 7385739 bytes.
0.09/0.12	c Coefficients are big enough for not using lower bounding.
1.19/1.20	c Highest Coefficient sum: 1.13141e+16
1.19/1.20	c Parsing was ok!!
1.19/1.20	c Total parsing time: 1.205 s
1.19/1.26	c Var: 104670 Constr: 3589 2/0/3587 Lit: 621000 Watch. Lit: 147874
1.19/1.26	c Obj. Vars: 50550 (48.2946 % of total variables)
1.39/1.47	c  Rst    Confl    NCB      Dec     Ctrs     Lits Learnt Conf/s Time
1.39/1.47	c    0        0      0        0     3589   621000      0      0 1.47
1.39/1.47	s UNSATISFIABLE
1.39/1.47	c Total time: 1.471 s

Verifier Data (download as text)

ERROR: no interpretation found !

Watcher Data (download as text)

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

command line: runsolver --timestamp -w ROOT/results/node60/watcher-433291-1177957381 -o ROOT/results/node60/solver-433291-1177957381 -C 1800 -W 3600 -M 1800 --output-limit 1,15 bsolo3.0.17 -m1800 /tmp/evaluation/433291-1177957381/instance-433291-1177957381.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.88 0.94 0.94 3/64 938
/proc/meminfo: memFree=1814808/2055920 swapFree=4183304/4192956
[pid=938] ppid=936 vsize=18952 CPUtime=0
/proc/938/stat : 938 (bsolo3.0.17) R 936 938 387 0 -1 4194304 361 0 0 0 0 0 0 0 18 0 1 0 243648136 19406848 331 18446744073709551615 134512640 135840783 4294956688 18446744073709551615 4294960144 0 0 4096 16384 0 0 0 17 1 0 0
/proc/938/statm: 4738 332 279 324 0 2004 0

[startup+0.083185 s]
/proc/loadavg: 0.88 0.94 0.94 3/64 938
/proc/meminfo: memFree=1814808/2055920 swapFree=4183304/4192956
[pid=938] ppid=936 vsize=21324 CPUtime=0.07
/proc/938/stat : 938 (bsolo3.0.17) R 936 938 387 0 -1 4194304 1147 0 0 0 7 0 0 0 18 0 1 0 243648136 21835776 1077 18446744073709551615 134512640 135840783 4294956688 18446744073709551615 134525286 0 0 4096 16384 0 0 0 17 1 0 0
/proc/938/statm: 5331 1078 429 324 0 2597 0
Current children cumulated CPU time (s) 0.07
Current children cumulated vsize (KiB) 21324

[startup+0.101187 s]
/proc/loadavg: 0.88 0.94 0.94 3/64 938
/proc/meminfo: memFree=1814808/2055920 swapFree=4183304/4192956
[pid=938] ppid=936 vsize=22200 CPUtime=0.09
/proc/938/stat : 938 (bsolo3.0.17) R 936 938 387 0 -1 4194304 1398 0 0 0 9 0 0 0 18 0 1 0 243648136 22732800 1249 18446744073709551615 134512640 135840783 4294956688 18446744073709551615 4294960144 0 0 4096 16384 0 0 0 17 1 0 0
/proc/938/statm: 5550 1250 463 324 0 2816 0
Current children cumulated CPU time (s) 0.09
Current children cumulated vsize (KiB) 22200

[startup+0.301207 s]
/proc/loadavg: 0.88 0.94 0.94 3/64 938
/proc/meminfo: memFree=1814808/2055920 swapFree=4183304/4192956
[pid=938] ppid=936 vsize=17760 CPUtime=0.29
/proc/938/stat : 938 (bsolo3.0.17) R 936 938 387 0 -1 4194304 2701 0 0 0 28 1 0 0 19 0 1 0 243648136 18186240 2503 18446744073709551615 134512640 135840783 4294956688 18446744073709551615 134525286 0 0 4096 16384 0 0 0 17 1 0 0
/proc/938/statm: 4440 2503 800 324 0 1706 0
Current children cumulated CPU time (s) 0.29
Current children cumulated vsize (KiB) 17760

[startup+0.701246 s]
/proc/loadavg: 0.88 0.94 0.94 3/64 938
/proc/meminfo: memFree=1814808/2055920 swapFree=4183304/4192956
[pid=938] ppid=936 vsize=23272 CPUtime=0.69
/proc/938/stat : 938 (bsolo3.0.17) R 936 938 387 0 -1 4194304 4795 0 0 0 67 2 0 0 22 0 1 0 243648136 23830528 4343 18446744073709551615 134512640 135840783 4294956688 18446744073709551615 134525046 0 0 4096 16384 0 0 0 17 1 0 0
/proc/938/statm: 5818 4343 1369 324 0 3084 0
Current children cumulated CPU time (s) 0.69
Current children cumulated vsize (KiB) 23272

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

[startup+1.10529 s]
/proc/loadavg: 0.88 0.94 0.94 2/65 939
/proc/meminfo: memFree=1800400/2055920 swapFree=4183304/4192956
[pid=938] ppid=936 vsize=26648 CPUtime=1.09
/proc/938/stat : 938 (bsolo3.0.17) R 936 938 387 0 -1 4194304 6201 0 0 0 106 3 0 0 25 0 1 0 243648136 27287552 5749 18446744073709551615 134512640 135840783 4294956688 18446744073709551615 134525286 0 0 4096 16384 0 0 0 17 1 0 0
/proc/938/statm: 6662 5749 1937 324 0 3928 0
Current children cumulated CPU time (s) 1.09
Current children cumulated vsize (KiB) 26648

[startup+1.3013 s]
/proc/loadavg: 0.88 0.94 0.94 2/65 939
/proc/meminfo: memFree=1800400/2055920 swapFree=4183304/4192956
[pid=938] ppid=936 vsize=34124 CPUtime=1.29
/proc/938/stat : 938 (bsolo3.0.17) R 936 938 387 0 -1 4194304 9945 0 0 0 124 5 0 0 25 0 1 0 243648136 34942976 7590 18446744073709551615 134512640 135840783 4294956688 18446744073709551615 5969531 0 0 4096 16384 0 0 0 17 1 0 0
/proc/938/statm: 8531 7590 303 324 0 7601 0
Current children cumulated CPU time (s) 1.29
Current children cumulated vsize (KiB) 34124

[startup+1.40131 s]
/proc/loadavg: 0.88 0.94 0.94 2/65 939
/proc/meminfo: memFree=1800400/2055920 swapFree=4183304/4192956
[pid=938] ppid=936 vsize=36632 CPUtime=1.39
/proc/938/stat : 938 (bsolo3.0.17) R 936 938 387 0 -1 4194304 10567 0 0 0 134 5 0 0 25 0 1 0 243648136 37511168 8212 18446744073709551615 134512640 135840783 4294956688 18446744073709551615 5969531 0 0 4096 16384 0 0 0 17 1 0 0
/proc/938/statm: 9158 8212 303 324 0 8228 0
Current children cumulated CPU time (s) 1.39
Current children cumulated vsize (KiB) 36632

Child status: 0
Real time (s): 1.48365
CPU time (s): 1.48177
CPU user time (s): 1.41978
CPU system time (s): 0.06199
CPU usage (%): 99.8734
Max. virtual memory (cumulated for all children) (KiB): 36632

getrusage(RUSAGE_CHILDREN,...) data:
user time used= 1.41978
system time used= 0.06199
maximum resident set size= 0
integral shared memory size= 0
integral unshared data size= 0
integral unshared stack size= 0
page reclaims= 11033
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= 2

runsolver used 0.003999 second user time and 0.008998 second system time

The end

Launcher Data (download as text)

Begin job on node60 on Mon Apr 30 18:23:02 UTC 2007

IDJOB= 433291
IDBENCH= 2445
IDSOLVER= 199
FILE ID= node60/433291-1177957381

PBS_JOBID= 4727708

Free space on /tmp= 66551 MiB

SOLVER NAME= bsolo 3.0.17
BENCH NAME= HOME/pub/bench/PB06//final/normalized-PB06/OPT-BIGINT/mps-v2-20-10/ftp.netlib.org/lp/data/normalized-mps-v2-20-10-bnl2.opb
COMMAND LINE= bsolo3.0.17 -m1800 /tmp/evaluation/433291-1177957381/instance-433291-1177957381.opb            
RUNSOLVER COMMAND LINE= runsolver  --timestamp  -w ROOT/results/node60/watcher-433291-1177957381 -o ROOT/results/node60/solver-433291-1177957381 -C 1800 -W 3600 -M 1800 --output-limit 1,15  bsolo3.0.17 -m1800 /tmp/evaluation/433291-1177957381/instance-433291-1177957381.opb            

META MD5SUM SOLVER= c9b15312c639dd71a11a1e3ca1b27020
MD5SUM BENCH=  1aac4473a72704481ef90ef3ff1598a7

RANDOM SEED= 484121738

TIME LIMIT= 1800 seconds
MEMORY LIMIT= 1800 MiB

Linux node60.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.214
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.214
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:       1815408 kB
Buffers:         19080 kB
Cached:         145956 kB
SwapCached:       3672 kB
Active:          38980 kB
Inactive:       135864 kB
HighTotal:           0 kB
HighFree:            0 kB
LowTotal:      2055920 kB
LowFree:       1815408 kB
SwapTotal:     4192956 kB
SwapFree:      4183304 kB
Dirty:           13804 kB
Writeback:           0 kB
Mapped:          15848 kB
Slab:            51684 kB
Committed_AS:  2709048 kB
PageTables:       1464 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= 66551 MiB

End job on node60 on Mon Apr 30 18:23:03 UTC 2007