Trace number 433663

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.17? 0.002998 0.0923269

General information on the benchmark

Namenormalized-PB06/OPT-BIGINT/submitted-PB06/roussel/factor/
normalized-factor-sizeN=120-sizeP=61-sizeQ=120-883133839-max.opb
MD5SUM0073f65f5c50ef8f4ebea5bdb58f4e26
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 variables7501
Total number of constraints21961
Number of constraints which are clauses21960
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 constraint7320
Number of terms in the objective function 61
Biggest coefficient in the objective function 1152921504606846976
Number of bits for the biggest coefficient in the objective function 61
Sum of the numbers in the objective function 2305843009213693951
Number of bits of the sum of numbers in the objective function 61
Biggest number in a constraint 766247770432944429179173513575154591809369561091801088
Number of bits of the biggest number in a constraint 180
Biggest sum of numbers in a constraint 3064991081731777715595715329186976003635521247756299664
Number of bits of the biggest sum of numbers181
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.17 - 27/04/2007 : 1600 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 Memory Limit set to 1800 MB
0.00/0.00	c Instance file /tmp/evaluation/433663-1177961890/instance-433663-1177961890.opb
0.00/0.00	c File size is 828838 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/433663-1177961890/instance-433663-1177961890.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 -2147483648 0.00
0.00/0.00	s UNKNOWN
0.00/0.00	c Total time: 0 s

Verifier Data (download as text)

ERROR: no interpretation found !

Watcher Data (download as text)

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

command line: runsolver --timestamp -w ROOT/results/node30/watcher-433663-1177961890 -o ROOT/results/node30/solver-433663-1177961890 -C 1800 -W 3600 -M 1800 --output-limit 1,15 bsolo3.0.17 -m1800 /tmp/evaluation/433663-1177961890/instance-433663-1177961890.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.67 0.91 0.89 3/77 18436
/proc/meminfo: memFree=1799792/2055920 swapFree=4157096/4192956
[pid=18436] ppid=18434 vsize=0 CPUtime=0
/proc/18436/stat : 18436 (bsolo3.0.17) R 18434 18436 17394 0 -1 4194308 384 0 0 0 0 0 0 0 18 0 1 0 244104718 0 0 18446744073709551615 0 0 0 0 0 0 0 4096 16384 0 0 0 17 1 0 0
/proc/18436/statm: 0 0 0 0 0 0 0

[startup+0.0577909 s]
/proc/loadavg: 0.67 0.91 0.89 3/77 18436
/proc/meminfo: memFree=1799792/2055920 swapFree=4157096/4192956
[pid=18436] ppid=18434 vsize=0 CPUtime=0
/proc/18436/stat : 18436 (bsolo3.0.17) D 18434 18436 17394 0 -1 4194308 384 0 0 0 0 0 0 0 15 0 1 0 244104718 0 0 18446744073709551615 0 0 0 0 0 0 0 4096 16384 18446744072100051646 0 0 17 1 0 0
/proc/18436/statm: 0 0 0 0 0 0 0
Current children cumulated CPU time (s) 0
Current children cumulated vsize (KiB) 0

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

[startup+0.0577909 s]
/proc/loadavg: 0.67 0.91 0.89 3/77 18436
/proc/meminfo: memFree=1799792/2055920 swapFree=4157096/4192956
[pid=18436] ppid=18434 vsize=0 CPUtime=0
/proc/18436/stat : 18436 (bsolo3.0.17) D 18434 18436 17394 0 -1 4194308 384 0 0 0 0 0 0 0 15 0 1 0 244104718 0 0 18446744073709551615 0 0 0 0 0 0 0 4096 16384 18446744072100051646 0 0 17 1 0 0
/proc/18436/statm: 0 0 0 0 0 0 0
Current children cumulated CPU time (s) 0
Current children cumulated vsize (KiB) 0

Child status: 1
Real time (s): 0.0923269
CPU time (s): 0.002998
CPU user time (s): 0.000999
CPU system time (s): 0.001999
CPU usage (%): 3.24716
Max. virtual memory (cumulated for all children) (KiB): 0

getrusage(RUSAGE_CHILDREN,...) data:
user time used= 0.000999
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= 384
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.000999 second user time and 0.008998 second system time

The end

Launcher Data (download as text)

Begin job on node30 on Mon Apr 30 19:38:10 UTC 2007

IDJOB= 433663
IDBENCH= 3050
IDSOLVER= 199
FILE ID= node30/433663-1177961890

PBS_JOBID= 4727709

Free space on /tmp= 66557 MiB

SOLVER NAME= bsolo 3.0.17
BENCH NAME= HOME/pub/bench/PB06/final/normalized-PB06/OPT-BIGINT/submitted-PB06/roussel/factor/normalized-factor-sizeN=120-sizeP=61-sizeQ=120-883133839-max.opb
COMMAND LINE= bsolo3.0.17 -m1800 /tmp/evaluation/433663-1177961890/instance-433663-1177961890.opb            
RUNSOLVER COMMAND LINE= runsolver  --timestamp  -w ROOT/results/node30/watcher-433663-1177961890 -o ROOT/results/node30/solver-433663-1177961890 -C 1800 -W 3600 -M 1800 --output-limit 1,15  bsolo3.0.17 -m1800 /tmp/evaluation/433663-1177961890/instance-433663-1177961890.opb            

META MD5SUM SOLVER= c9b15312c639dd71a11a1e3ca1b27020
MD5SUM BENCH=  0073f65f5c50ef8f4ebea5bdb58f4e26

RANDOM SEED= 219169320

TIME LIMIT= 1800 seconds
MEMORY LIMIT= 1800 MiB

Linux node30.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.218
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.218
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:       1800200 kB
Buffers:         31400 kB
Cached:         133340 kB
SwapCached:      15324 kB
Active:          47940 kB
Inactive:       145428 kB
HighTotal:           0 kB
HighFree:            0 kB
LowTotal:      2055920 kB
LowFree:       1800200 kB
SwapTotal:     4192956 kB
SwapFree:      4157096 kB
Dirty:            7556 kB
Writeback:           0 kB
Mapped:          35632 kB
Slab:            47916 kB
Committed_AS:  3669120 kB
PageTables:       1788 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= 66557 MiB

End job on node30 on Mon Apr 30 19:38:11 UTC 2007