Trace number 354395

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.16? 0.269958 0.306631

General information on the benchmark

Namenormalized-PB06/OPT-BIGINT/mps-v2-20-10/
MIPLIB/miplib2003/normalized-mps-v2-20-10-mod011.opb
MD5SUM7946286f4c1a7ac44cf771db2f48f590
Bench CategoryOPT-BIGINT (optimisation, big integers)
Best result obtained on this benchmark
Best value of the objective obtained on this benchmark
Best CPU time to get the best result obtained on this benchmark
Has Objective FunctionYES
SatisfiableYES
(Un)Satisfiability was provedYES
Best value of the objective function 0
Optimality of the best value was proved NO
Number of variables309773
Total number of constraints5980
Number of constraints which are clauses0
Number of constraints which are cardinality constraints (but not clauses)16
Number of constraints which are nor clauses,nor cardinality constraints5964
Minimum length of a constraint6
Maximum length of a constraint24690
Number of terms in the objective function 212680
Biggest coefficient in the objective function 38252041742581760
Number of bits for the biggest coefficient in the objective function 56
Sum of the numbers in the objective function 82366741301042726133
Number of bits of the sum of numbers in the objective function 67
Biggest number in a constraint 38252041742581760
Number of bits of the biggest number in a constraint 56
Biggest sum of numbers in a constraint 82366741301042726133
Number of bits of the biggest sum of numbers67
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.04	c bsolo beta version 3.0.16 - 04/04/2007 : 1458 GMT
0.00/0.04	c Developed by Vasco Manquinho IST/UTL - INESC-ID
0.00/0.04	c type "bsolo -h" for help
0.00/0.04	c Time Limit set via environment variable PBTIMEOUT to 1800
0.00/0.04	c Time Limit set to 1800
0.00/0.04	c Memory Limit set to 1800 MB
0.00/0.04	c Instance file /tmp/evaluation/354395-1176707498/instance-354395-1176707498.opb
0.00/0.04	c File size is 14706008 bytes.
0.16/0.29	c Risky overflow due to sum of coefficients at cost function.
0.16/0.29	c Parse Error 9
0.16/0.29	c Line: 7
0.16/0.29	c Unable to parse file /tmp/evaluation/354395-1176707498/instance-354395-1176707498.opb
0.16/0.29	c Caught signal: 1
0.16/0.29	c  Rst    Confl    NCB      Dec     Ctrs     Lits Learnt Conf/s Time
0.16/0.29	c    0        0      0        0        0        0      0      0 0.26
0.16/0.29	s UNKNOWN
0.16/0.29	c Total time: 0.256 s

Verifier Data (download as text)

ERROR: no interpretation found !

Watcher Data (download as text)

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

command line: runsolver --timestamp -w ROOT/results/node59/watcher-354395-1176707498 -o ROOT/results/node59/solver-354395-1176707498 -C 1800 -W 3600 -M 1800 --output-limit 1,15 bsolo3.0.16 -t1800 -m1800 /tmp/evaluation/354395-1176707498/instance-354395-1176707498.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.97 0.98 3/64 18470
/proc/meminfo: memFree=1923144/2055920 swapFree=4184740/4192956
[pid=18470] ppid=18468 vsize=18568 CPUtime=0
/proc/18470/stat : 18470 (runsolver) D 18468 18470 18410 0 -1 4194368 17 0 0 0 0 0 0 0 18 0 1 0 118659416 19013632 292 18446744073709551615 4194304 4296420 548682068976 18446744073709551615 217051622695 0 0 4096 24578 18446744071563608240 0 0 17 1 0 0
/proc/18470/statm: 4642 292 257 24 0 2626 0

[startup+0.09783 s]
/proc/loadavg: 0.78 0.97 0.98 3/64 18470
/proc/meminfo: memFree=1923144/2055920 swapFree=4184740/4192956
[pid=18470] ppid=18468 vsize=28044 CPUtime=0.05
/proc/18470/stat : 18470 (bsolo3.0.16) R 18468 18470 18410 0 -1 4194304 999 0 3 0 5 0 0 0 18 0 1 0 118659416 28717056 930 18446744073709551615 134512640 135841103 4294956688 18446744073709551615 134524175 0 0 4096 16384 0 0 0 17 0 0 0
/proc/18470/statm: 7011 930 417 324 0 2489 0
Current children cumulated CPU time (s) 0.05
Current children cumulated vsize (KiB) 28044

[startup+0.101823 s]
/proc/loadavg: 0.78 0.97 0.98 3/64 18470
/proc/meminfo: memFree=1923144/2055920 swapFree=4184740/4192956
[pid=18470] ppid=18468 vsize=28184 CPUtime=0.06
/proc/18470/stat : 18470 (bsolo3.0.16) R 18468 18470 18410 0 -1 4194304 1034 0 3 0 6 0 0 0 18 0 1 0 118659416 28860416 965 18446744073709551615 134512640 135841103 4294956688 18446744073709551615 9755757 0 0 4096 16384 0 0 0 17 0 0 0
/proc/18470/statm: 7046 965 426 324 0 2524 0
Current children cumulated CPU time (s) 0.06
Current children cumulated vsize (KiB) 28184

[startup+0.301874 s]
/proc/loadavg: 0.78 0.97 0.98 3/64 18470
/proc/meminfo: memFree=1923144/2055920 swapFree=4184740/4192956
[pid=18470] ppid=18468 vsize=34108 CPUtime=0.25
/proc/18470/stat : 18470 (bsolo3.0.16) R 18468 18470 18410 0 -1 4194304 3302 0 3 0 24 1 0 0 19 0 1 0 118659416 34926592 2851 18446744073709551615 134512640 135841103 4294956688 18446744073709551615 9719316 0 0 4096 16384 0 0 0 17 0 0 0
/proc/18470/statm: 8527 2851 875 324 0 4005 0
Current children cumulated CPU time (s) 0.25
Current children cumulated vsize (KiB) 34108

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

Child status: 1
Real time (s): 0.306631
CPU time (s): 0.269958
CPU user time (s): 0.248962
CPU system time (s): 0.020996
CPU usage (%): 88.04
Max. virtual memory (cumulated for all children) (KiB): 34108

getrusage(RUSAGE_CHILDREN,...) data:
user time used= 0.248962
system time used= 0.020996
maximum resident set size= 0
integral shared memory size= 0
integral unshared data size= 0
integral unshared stack size= 0
page reclaims= 3303
page faults= 3
swaps= 0
block input operations= 0
block output operations= 0
messages sent= 0
messages received= 0
signals received= 0
voluntary context switches= 20
involuntary context switches= 6

runsolver used 0.004999 second user time and 0.004999 second system time

The end

Launcher Data (download as text)

Begin job on node59 on Mon Apr 16 07:11:38 UTC 2007

IDJOB= 354395
IDBENCH= 2509
IDSOLVER= 163
FILE ID= node59/354395-1176707498

PBS_JOBID= 4560089

Free space on /tmp= 66352 MiB

SOLVER NAME= bsolo 3.0.16
BENCH NAME= HOME/pub/bench/PB06//final/normalized-PB06/OPT-BIGINT/mps-v2-20-10/MIPLIB/miplib2003/normalized-mps-v2-20-10-mod011.opb
COMMAND LINE= bsolo3.0.16 -t1800 -m1800 /tmp/evaluation/354395-1176707498/instance-354395-1176707498.opb            
RUNSOLVER COMMAND LINE= runsolver  --timestamp  -w ROOT/results/node59/watcher-354395-1176707498 -o ROOT/results/node59/solver-354395-1176707498 -C 1800 -W 3600 -M 1800 --output-limit 1,15  bsolo3.0.16 -t1800 -m1800 /tmp/evaluation/354395-1176707498/instance-354395-1176707498.opb            

META MD5SUM SOLVER= b11bf0769a124f73ad50b0fdfcd50482
MD5SUM BENCH=  7946286f4c1a7ac44cf771db2f48f590

RANDOM SEED= 155687947

TIME LIMIT= 1800 seconds
MEMORY LIMIT= 1800 MiB

Linux node59.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.268
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.268
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:       1923808 kB
Buffers:          1708 kB
Cached:          70660 kB
SwapCached:       2160 kB
Active:          49544 kB
Inactive:        32248 kB
HighTotal:           0 kB
HighFree:            0 kB
LowTotal:      2055920 kB
LowFree:       1923808 kB
SwapTotal:     4192956 kB
SwapFree:      4184740 kB
Dirty:           18976 kB
Writeback:           0 kB
Mapped:          16436 kB
Slab:            36344 kB
Committed_AS:  1542884 kB
PageTables:       1472 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= 66352 MiB

End job on node59 on Mon Apr 16 07:11:39 UTC 2007