Trace number 40676

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 2006/05? 25.0672 25.0928

General information on the benchmark

Namenormalized-PB06/OPT-BIGINT/mps-v2-20-10/ftp.netlib.org/
lp/data/normalized-mps-v2-20-10-d2q06c.opb
MD5SUM7b03b498d913dd1b306399e53ada7e6f
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 benchmark25.4491
Has Objective FunctionYES
SatisfiableNO
(Un)Satisfiability was provedYES
Best value of the objective function
Optimality of the best value was proved
Number of variables155010
Total number of constraints2171
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 constraints2171
Minimum length of a constraint30
Maximum length of a constraint3270
Number of terms in the objective function 89670
Biggest coefficient in the objective function 36281708852543488
Number of bits for the biggest coefficient in the objective function 56
Sum of the numbers in the objective function 17434532498669331507
Number of bits of the sum of numbers in the objective function 64
Biggest number in a constraint 1246989811751845888
Number of bits of the biggest number in a constraint 61
Biggest sum of numbers in a constraint 17434532498669331507
Number of bits of the biggest sum of numbers64
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	c Time Limit set via PBTIMEOUT to 1800
0.01	c INFO: OSL Context initialized.
0.02	c BIG Int formula...
25.08	c Parse Error 8
25.08	c Problem opening input file name: ROOT/tmp/node81/40676-1149311360/instance-40676-1149311360.opb
25.08	s UNKNOWN
25.08	c Exit Code: 0

Verifier Data (download as text)

ERROR: no interpretation found !

Watcher Data (download as text)

Enforcing CPU limit (will send SIGTERM then SIGKILL): 1800 seconds
Enforcing CPUTime (will send SIGXCPU) limit: 1830 seconds
Enforcing Stack size limit: 67108864 bytes
Enforcing memory limit (will send SIGKILL): 1843200 Kb
Enforcing VSIZE limit: 1887436800 bytes
runsolver version 3.0.0 (c) roussel@cril.univ-artois.fr

command line: runsolver --timestamp -w ROOT/results/node81/watcher-40676-1149311360 -o ROOT/results/node81/solver-40676-1149311360 -C 1800 -M 1800 -S 64 ROOT/solvers/PB/PB06final/user10/bsolo ROOT/tmp/node81/40676-1149311360/instance-40676-1149311360.opb 

Current StackSize limit: 67108864 bytes

/proc/loadavg: 0.85 0.97 0.99 2/68 30690
/proc/meminfo: memFree=1008720/2055892 swapFree=4085344/4096564
[pid=30690] ppid=30688 vsize=4632 CPUtime=0
/proc/30690/stat : 30690 (bsolo) R 30688 30690 30644 0 -1 0 72 0 0 0 0 0 0 0 18 0 1 0 196775532 4743168 55 18446744073709551615 134512640 134738892 4294956688 18446744073709551615 10101812 0 0 4096 0 0 0 0 17 1 0 0
/proc/30690/statm: 1167 59 43 55 0 45 0

[startup+10.003 s]
/proc/loadavg: 0.87 0.97 0.99 2/68 30690
/proc/meminfo: memFree=991120/2055892 swapFree=4085344/4096564
[pid=30690] ppid=30688 vsize=22620 CPUtime=9.98
/proc/30690/stat : 30690 (bsolo) R 30688 30690 30644 0 -1 0 2072969 0 0 0 462 536 0 0 25 0 1 0 196775532 23162880 4761 18446744073709551615 134512640 134738892 4294956688 18446744073709551615 4294960144 0 0 4096 16384 0 0 0 17 1 0 0
/proc/30690/statm: 5655 4643 274 55 0 4546 0
Current children cumulated CPU time (s) 9.98
Current children cumulated vsize (Kb) 22620

[startup+20.0101 s]
/proc/loadavg: 0.89 0.97 0.99 2/68 30690
/proc/meminfo: memFree=984080/2055892 swapFree=4085344/4096564
[pid=30690] ppid=30688 vsize=30416 CPUtime=19.98
/proc/30690/stat : 30690 (bsolo) R 30688 30690 30644 0 -1 0 4168692 0 0 0 893 1105 0 0 25 0 1 0 196775532 31145984 6543 18446744073709551615 134512640 134738892 4294956688 18446744073709551615 4294960144 0 0 4096 16384 0 0 0 17 1 0 0
/proc/30690/statm: 7604 6401 274 55 0 6495 0
Current children cumulated CPU time (s) 19.98
Current children cumulated vsize (Kb) 30416

Child status: 0
Real time (s): 25.0928
CPU time (s): 25.0672
CPU user time (s): 11.0723
CPU system time (s): 13.9949
CPU usage (%): 99.8979
Max. virtual memory (cumulated for all children) (Kb): 30416

Launcher Data (download as text)

Begin job on node81 on Sat Jun  3 05:09:21 UTC 2006


FILE ID= 40676-1149311360

PBS_JOBID= 308016

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-d2q06c.opb
COMMAND LINE= ROOT/solvers/PB/PB06final/user10/bsolo ROOT/tmp/node81/40676-1149311360/instance-40676-1149311360.opb
RUNSOLVER COMMAND LINE= runsolver  --timestamp  -w ROOT/results/node81/watcher-40676-1149311360 -o ROOT/results/node81/solver-40676-1149311360 -C 1800 -M 1800 -S 64  ROOT/solvers/PB/PB06final/user10/bsolo ROOT/tmp/node81/40676-1149311360/instance-40676-1149311360.opb

MD5SUM SOLVER= 05cada221eb1efaaae980ebc7509e7e8
MD5SUM BENCH=  7b03b498d913dd1b306399e53ada7e6f

RANDOM SEED= 896314622


/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.248
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	: 6006.19
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.248
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	: 5999.42
clflush size	: 64
cache_alignment	: 128
address sizes	: 36 bits physical, 48 bits virtual
power management:


/proc/meminfo:
MemTotal:      2055892 kB
MemFree:       1008992 kB
Buffers:         45216 kB
Cached:         921400 kB
SwapCached:       2656 kB
Active:         190776 kB
Inactive:       784776 kB
HighTotal:           0 kB
HighFree:            0 kB
LowTotal:      2055892 kB
LowFree:       1008992 kB
SwapTotal:     4096564 kB
SwapFree:      4085344 kB
Dirty:             192 kB
Writeback:           0 kB
Mapped:          16520 kB
Slab:            57956 kB
Committed_AS:   284984 kB
PageTables:       1288 kB
VmallocTotal: 536870911 kB
VmallocUsed:    264388 kB
VmallocChunk: 536606243 kB
HugePages_Total:     0
HugePages_Free:      0
Hugepagesize:     2048 kB


End job on node81 on Sat Jun  3 05:09:46 UTC 2006