Trace number 350111

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.006998 0.117983

General information on the benchmark

Namenormalized-PB06/OPT-BIGINT/submitted-PB06/roussel/factor/
normalized-factor-sizeN=360-sizeP=181-sizeQ=360-885821403-max.opb
MD5SUMdaef519cc387cb4190b46c644ef26a75
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
Satisfiable
(Un)Satisfiability was proved
Best value of the objective function
Optimality of the best value was proved
Number of variables65701
Total number of constraints195481
Number of constraints which are clauses195480
Number of constraints which are cardinality constraints (but not clauses)0
Number of constraints which are nor clauses,nor cardinality constraints1
Minimum length of a constraint2
Maximum length of a constraint65160
Number of terms in the objective function 181
Biggest coefficient in the objective function 1532495540865888858358347027150309183618739122183602176
Number of bits for the biggest coefficient in the objective function 181
Sum of the numbers in the objective function 3064991081731777716716694054300618367237478244367204351
Number of bits of the sum of numbers in the objective function 181
Biggest number in a constraint 1799565517817278553124215403074392743547878847320766653240302229044735032268595148127616274441556342859968364253408358049283306422197719875603406072346065542053888
Number of bits of the biggest number in a constraint 540
Biggest sum of numbers in a constraint 7198262071269114212496861612297570974191515389283066611663944849260137495841993663922586015605314649454542626583271372705247225059695176544033188317685768654897628
Number of bits of the biggest sum of numbers541
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.11	c bsolo beta version 3.0.16 - 04/04/2007 : 1458 GMT
0.00/0.11	c Developed by Vasco Manquinho IST/UTL - INESC-ID
0.00/0.11	c type "bsolo -h" for help
0.00/0.11	c Time Limit set via environment variable PBTIMEOUT to 1800
0.00/0.11	c Time Limit set to 1800
0.00/0.11	c Memory Limit set to 1800 MB
0.00/0.11	c Instance file /tmp/evaluation/350111-1176794089/instance-350111-1176794089.opb
0.00/0.11	c File size is 11267768 bytes.
0.00/0.11	c Integer values too big to handle... 
0.00/0.11	c Parse Error 9
0.00/0.11	c Line: 7
0.00/0.11	c Unable to parse file /tmp/evaluation/350111-1176794089/instance-350111-1176794089.opb
0.00/0.11	c Caught signal: 1
0.00/0.11	c  Rst    Confl    NCB      Dec     Ctrs     Lits Learnt Conf/s Time
0.00/0.11	c    0        0      0        0        0        0      0      0 0.00
0.00/0.11	s UNKNOWN
0.00/0.11	c Total time: 0.002 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/node57/watcher-350111-1176794089 -o ROOT/results/node57/solver-350111-1176794089 -C 1800 -W 3600 -M 1800 --output-limit 1,15 bsolo3.0.16 -t1800 -m1800 /tmp/evaluation/350111-1176794089/instance-350111-1176794089.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: 1.00 1.00 1.00 3/64 901
/proc/meminfo: memFree=1804608/2055920 swapFree=4174176/4192956
[pid=901] ppid=899 vsize=18568 CPUtime=0
/proc/901/stat : 901 (runsolver) D 899 901 32670 0 -1 4194368 17 0 0 0 0 0 0 0 18 0 1 0 120544865 19013632 292 18446744073709551615 4194304 4296420 548682068928 18446744073709551615 218076081447 0 0 4096 24578 18446744071563608240 0 0 17 1 0 0
/proc/901/statm: 4642 292 257 24 0 2626 0

[startup+0.00809804 s]
/proc/loadavg: 1.00 1.00 1.00 3/64 901
/proc/meminfo: memFree=1804608/2055920 swapFree=4174176/4192956
[pid=901] ppid=899 vsize=18568 CPUtime=0
/proc/901/stat : 901 (runsolver) D 899 901 32670 0 -1 4194368 17 0 0 0 0 0 0 0 18 0 1 0 120544865 19013632 292 18446744073709551615 4194304 4296420 548682068928 18446744073709551615 218076081447 0 0 4096 24578 18446744071563608240 0 0 17 0 0 0
/proc/901/statm: 4642 292 257 24 0 2626 0
Current children cumulated CPU time (s) 0
Current children cumulated vsize (KiB) 18568

[startup+0.101109 s]
/proc/loadavg: 1.00 1.00 1.00 3/64 901
/proc/meminfo: memFree=1804608/2055920 swapFree=4174176/4192956
[pid=901] ppid=899 vsize=3780 CPUtime=0
/proc/901/stat : 901 (bsolo3.0.16) D 899 901 32670 0 -1 4194304 163 0 7 0 0 0 0 0 18 0 1 0 120544865 3870720 138 18446744073709551615 134512640 135841103 4294956640 18446744073709551615 8206656 0 0 4096 0 18446744071563479169 0 0 17 0 0 0
/proc/901/statm: 945 138 114 324 0 14 0
Current children cumulated CPU time (s) 0
Current children cumulated vsize (KiB) 3780

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

Child status: 1
Real time (s): 0.117983
CPU time (s): 0.006998
CPU user time (s): 0.001999
CPU system time (s): 0.004999
CPU usage (%): 5.93136
Max. virtual memory (cumulated for all children) (KiB): 18568

getrusage(RUSAGE_CHILDREN,...) data:
user time used= 0.001999
system time used= 0.004999
maximum resident set size= 0
integral shared memory size= 0
integral unshared data size= 0
integral unshared stack size= 0
page reclaims= 370
page faults= 17
swaps= 0
block input operations= 0
block output operations= 0
messages sent= 0
messages received= 0
signals received= 0
voluntary context switches= 44
involuntary context switches= 16

runsolver used 0.002999 second user time and 0.005999 second system time

The end

Launcher Data (download as text)

Begin job on node57 on Tue Apr 17 07:14:49 UTC 2007

IDJOB= 350111
IDBENCH= 2979
IDSOLVER= 163
FILE ID= node57/350111-1176794089

PBS_JOBID= 4580852

Free space on /tmp= 66502 MiB

SOLVER NAME= bsolo 3.0.16
BENCH NAME= HOME/pub/bench/PB06/final/normalized-PB06/OPT-BIGINT/submitted-PB06/roussel/factor/normalized-factor-sizeN=360-sizeP=181-sizeQ=360-885821403-max.opb
COMMAND LINE= bsolo3.0.16 -t1800 -m1800 /tmp/evaluation/350111-1176794089/instance-350111-1176794089.opb            
RUNSOLVER COMMAND LINE= runsolver  --timestamp  -w ROOT/results/node57/watcher-350111-1176794089 -o ROOT/results/node57/solver-350111-1176794089 -C 1800 -W 3600 -M 1800 --output-limit 1,15  bsolo3.0.16 -t1800 -m1800 /tmp/evaluation/350111-1176794089/instance-350111-1176794089.opb            

META MD5SUM SOLVER= b11bf0769a124f73ad50b0fdfcd50482
MD5SUM BENCH=  daef519cc387cb4190b46c644ef26a75

RANDOM SEED= 431984165

TIME LIMIT= 1800 seconds
MEMORY LIMIT= 1800 MiB

Linux node57.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.239
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.239
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:       1805016 kB
Buffers:         12052 kB
Cached:         178212 kB
SwapCached:      13056 kB
Active:         139272 kB
Inactive:        70320 kB
HighTotal:           0 kB
HighFree:            0 kB
LowTotal:      2055920 kB
LowFree:       1805016 kB
SwapTotal:     4192956 kB
SwapFree:      4174176 kB
Dirty:           15388 kB
Writeback:           0 kB
Mapped:          15796 kB
Slab:            27400 kB
Committed_AS:   827628 kB
PageTables:       1408 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= 66502 MiB

End job on node57 on Tue Apr 17 07:14:49 UTC 2007