Trace number 354175

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.113982 0.220658

General information on the benchmark

Namenormalized-PB06/OPT-BIGINT/mps-v2-20-10/plato.asu.edu/
pub/unibo/normalized-mps-v2-20-10-dc1l.opb
MD5SUMb626c8307376f19de1f1e51bf91eca4f
Bench CategoryOPT-BIGINT (optimisation, big integers)
Best result obtained on this benchmarkSAT
Best value of the objective obtained on this benchmark322124995065185536000
Best CPU time to get the best result obtained on this benchmark1804.19
Has Objective FunctionYES
SatisfiableYES
(Un)Satisfiability was provedYES
Best value of the objective function 17540679175205888
Optimality of the best value was proved NO
Number of variables85198
Total number of constraints1652
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 constraints1652
Minimum length of a constraint31
Maximum length of a constraint35129
Number of terms in the objective function 85198
Biggest coefficient in the objective function 536870912000000000000
Number of bits for the biggest coefficient in the objective function 69
Sum of the numbers in the objective function 6796468271401867858547
Number of bits of the sum of numbers in the objective function 73
Biggest number in a constraint 536870912000000000000
Number of bits of the biggest number in a constraint 69
Biggest sum of numbers in a constraint 6796468271401867858547
Number of bits of the biggest sum of numbers73
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.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/354175-1176697734/instance-354175-1176697734.opb
0.00/0.00	c File size is 8370124 bytes.
0.09/0.10	c Integer values too big to handle... 
0.09/0.10	c Parse Error 9
0.09/0.10	c Line: 7
0.09/0.10	c Unable to parse file /tmp/evaluation/354175-1176697734/instance-354175-1176697734.opb
0.09/0.10	c Caught signal: 1
0.10/0.21	c  Rst    Confl    NCB      Dec     Ctrs     Lits Learnt Conf/s Time
0.10/0.21	c    0        0      0        0        0        0      0      0 0.11
0.10/0.21	s UNKNOWN
0.10/0.21	c Total time: 0.106 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/node23/watcher-354175-1176697734 -o ROOT/results/node23/solver-354175-1176697734 -C 1800 -W 3600 -M 1800 --output-limit 1,15 bsolo3.0.16 -t1800 -m1800 /tmp/evaluation/354175-1176697734/instance-354175-1176697734.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.99 0.98 0.99 3/77 16959
/proc/meminfo: memFree=1818104/2055920 swapFree=4169188/4192956
[pid=16959] ppid=16957 vsize=19912 CPUtime=0
/proc/16959/stat : 16959 (bsolo3.0.16) R 16957 16959 16270 0 -1 4194304 368 0 0 0 0 0 0 0 18 0 1 0 117690600 20389888 336 18446744073709551615 134512640 135841103 4294956688 18446744073709551615 4294960144 0 0 4096 16384 0 0 0 17 1 0 0
/proc/16959/statm: 4978 336 282 324 0 2003 0

[startup+0.096607 s]
/proc/loadavg: 0.99 0.98 0.99 3/77 16959
/proc/meminfo: memFree=1818104/2055920 swapFree=4169188/4192956
[pid=16959] ppid=16957 vsize=22428 CPUtime=0.08
/proc/16959/stat : 16959 (bsolo3.0.16) R 16957 16959 16270 0 -1 4194304 1234 0 0 0 8 0 0 0 18 0 1 0 117690600 22966272 1162 18446744073709551615 134512640 135841103 4294956688 18446744073709551615 134525286 0 0 4096 16384 0 0 0 17 1 0 0
/proc/16959/statm: 5607 1163 483 324 0 2632 0
Current children cumulated CPU time (s) 0.08
Current children cumulated vsize (KiB) 22428

[startup+0.101606 s]
/proc/loadavg: 0.99 0.98 0.99 3/77 16959
/proc/meminfo: memFree=1818104/2055920 swapFree=4169188/4192956
[pid=16959] ppid=16957 vsize=22880 CPUtime=0.09
/proc/16959/stat : 16959 (bsolo3.0.16) R 16957 16959 16270 0 -1 4194304 1370 0 0 0 9 0 0 0 18 0 1 0 117690600 23429120 1219 18446744073709551615 134512640 135841103 4294956688 18446744073709551615 4294960144 0 0 4096 16384 0 0 0 17 1 0 0
/proc/16959/statm: 5720 1219 493 324 0 2745 0
Current children cumulated CPU time (s) 0.09
Current children cumulated vsize (KiB) 22880

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

[startup+0.201628 s]
/proc/loadavg: 0.99 0.98 0.99 3/77 16959
/proc/meminfo: memFree=1818104/2055920 swapFree=4169188/4192956
[pid=16959] ppid=16957 vsize=23024 CPUtime=0.1
/proc/16959/stat : 16959 (bsolo3.0.16) D 16957 16959 16270 0 -1 4194304 1453 0 0 0 10 0 0 0 18 0 1 0 117690600 23576576 1302 18446744073709551615 134512640 135841103 4294956688 18446744073709551615 2789486 0 0 4096 16384 18446744071563479169 0 0 17 0 0 0
/proc/16959/statm: 5756 1302 528 324 0 2781 0
Current children cumulated CPU time (s) 0.1
Current children cumulated vsize (KiB) 23024

Child status: 1
Real time (s): 0.220658
CPU time (s): 0.113982
CPU user time (s): 0.104984
CPU system time (s): 0.008998
CPU usage (%): 51.6555
Max. virtual memory (cumulated for all children) (KiB): 23024

getrusage(RUSAGE_CHILDREN,...) data:
user time used= 0.104984
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= 1458
page faults= 1
swaps= 0
block input operations= 0
block output operations= 0
messages sent= 0
messages received= 0
signals received= 0
voluntary context switches= 14
involuntary context switches= 3

runsolver used 0.002999 second user time and 0.005999 second system time

The end

Launcher Data (download as text)

Begin job on node23 on Mon Apr 16 04:28:55 UTC 2007

IDJOB= 354175
IDBENCH= 2370
IDSOLVER= 163
FILE ID= node23/354175-1176697734

PBS_JOBID= 4560026

Free space on /tmp= 66545 MiB

SOLVER NAME= bsolo 3.0.16
BENCH NAME= HOME/pub/bench/PB06//final/normalized-PB06/OPT-BIGINT/mps-v2-20-10/plato.asu.edu/pub/unibo/normalized-mps-v2-20-10-dc1l.opb
COMMAND LINE= bsolo3.0.16 -t1800 -m1800 /tmp/evaluation/354175-1176697734/instance-354175-1176697734.opb            
RUNSOLVER COMMAND LINE= runsolver  --timestamp  -w ROOT/results/node23/watcher-354175-1176697734 -o ROOT/results/node23/solver-354175-1176697734 -C 1800 -W 3600 -M 1800 --output-limit 1,15  bsolo3.0.16 -t1800 -m1800 /tmp/evaluation/354175-1176697734/instance-354175-1176697734.opb            

META MD5SUM SOLVER= b11bf0769a124f73ad50b0fdfcd50482
MD5SUM BENCH=  b626c8307376f19de1f1e51bf91eca4f

RANDOM SEED= 533020322

TIME LIMIT= 1800 seconds
MEMORY LIMIT= 1800 MiB

Linux node23.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.276
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.276
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:       1818832 kB
Buffers:         33060 kB
Cached:         108220 kB
SwapCached:       2268 kB
Active:          73544 kB
Inactive:        93476 kB
HighTotal:           0 kB
HighFree:            0 kB
LowTotal:      2055920 kB
LowFree:       1818832 kB
SwapTotal:     4192956 kB
SwapFree:      4169188 kB
Dirty:           12576 kB
Writeback:           0 kB
Mapped:          32932 kB
Slab:            55564 kB
Committed_AS:  2367792 kB
PageTables:       1804 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= 66545 MiB

End job on node23 on Mon Apr 16 04:28:55 UTC 2007