Trace number 350101

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.005998 0.00618398

General information on the benchmark

Namenormalized-PB06/OPT-BIGINT/submitted-PB06/roussel/factor/
normalized-factor-sizeN=240-sizeP=121-sizeQ=240-330229238-max.opb
MD5SUM7371465ba0e0d5bc10bb1d033f8bcd56
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 variables29401
Total number of constraints87121
Number of constraints which are clauses87120
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 constraint29040
Number of terms in the objective function 121
Biggest coefficient in the objective function 1329227995784915872903807060280344576
Number of bits for the biggest coefficient in the objective function 121
Sum of the numbers in the objective function 2658455991569831745807614120560689151
Number of bits of the sum of numbers in the objective function 121
Biggest number in a constraint 1174271291386916613944740298394668513687841274454159935353645485766104512557304221731849499192384351515967488
Number of bits of the biggest number in a constraint 360
Biggest sum of numbers in a constraint 4697085165547666455778961193578674053759190090835006449104283878090284482579702915208197909390404088540790263
Number of bits of the biggest sum of numbers361
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/350101-1176793036/instance-350101-1176793036.opb
0.00/0.00	c File size is 4194763 bytes.
0.00/0.00	c Integer values too big to handle... 
0.00/0.00	c Parse Error 9
0.00/0.00	c Line: 7
0.00/0.00	c Unable to parse file /tmp/evaluation/350101-1176793036/instance-350101-1176793036.opb
0.00/0.00	c Caught signal: 1
0.00/0.00	c  Rst    Confl    NCB      Dec     Ctrs     Lits Learnt Conf/s Time
0.00/0.00	c    0        0      0        0        0        0      0      0 0.00
0.00/0.00	s UNKNOWN
0.00/0.00	c Total time: 0.001 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/node1/watcher-350101-1176793036 -o ROOT/results/node1/solver-350101-1176793036 -C 1800 -W 3600 -M 1800 --output-limit 1,15 bsolo3.0.16 -t1800 -m1800 /tmp/evaluation/350101-1176793036/instance-350101-1176793036.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/77 15925
/proc/meminfo: memFree=1561096/2055920 swapFree=4145916/4192956
[pid=15925] ppid=15923 vsize=0 CPUtime=0
/proc/15925/stat : 15925 (bsolo3.0.16) D 15923 15925 15118 0 -1 4194308 387 0 0 0 0 0 0 0 18 0 1 0 155341417 0 0 18446744073709551615 0 0 0 0 0 0 0 4096 16384 18446744072100051646 0 0 17 1 0 0
/proc/15925/statm: 0 0 0 0 0 0 0

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

Child status: 1
Real time (s): 0.00618398
CPU time (s): 0.005998
CPU user time (s): 0.003999
CPU system time (s): 0.001999
CPU usage (%): 96.9925
Max. virtual memory (cumulated for all children) (KiB): 0

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

runsolver used 0.004999 second user time and 0.002999 second system time

The end

Launcher Data (download as text)

Begin job on node1 on Tue Apr 17 06:57:16 UTC 2007

IDJOB= 350101
IDBENCH= 2973
IDSOLVER= 163
FILE ID= node1/350101-1176793036

PBS_JOBID= 4580841

Free space on /tmp= 66393 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=240-sizeP=121-sizeQ=240-330229238-max.opb
COMMAND LINE= bsolo3.0.16 -t1800 -m1800 /tmp/evaluation/350101-1176793036/instance-350101-1176793036.opb            
RUNSOLVER COMMAND LINE= runsolver  --timestamp  -w ROOT/results/node1/watcher-350101-1176793036 -o ROOT/results/node1/solver-350101-1176793036 -C 1800 -W 3600 -M 1800 --output-limit 1,15  bsolo3.0.16 -t1800 -m1800 /tmp/evaluation/350101-1176793036/instance-350101-1176793036.opb            

META MD5SUM SOLVER= b11bf0769a124f73ad50b0fdfcd50482
MD5SUM BENCH=  7371465ba0e0d5bc10bb1d033f8bcd56

RANDOM SEED= 798640928

TIME LIMIT= 1800 seconds
MEMORY LIMIT= 1800 MiB

Linux node1.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.234
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.234
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:       1561504 kB
Buffers:         36984 kB
Cached:         377472 kB
SwapCached:      14828 kB
Active:         268476 kB
Inactive:       180948 kB
HighTotal:           0 kB
HighFree:            0 kB
LowTotal:      2055920 kB
LowFree:       1561504 kB
SwapTotal:     4192956 kB
SwapFree:      4145916 kB
Dirty:            8584 kB
Writeback:           0 kB
Mapped:          41688 kB
Slab:            30404 kB
Committed_AS:  4924256 kB
PageTables:       1868 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= 66393 MiB

End job on node1 on Tue Apr 17 06:57:16 UTC 2007