Trace number 50365

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 2006/05? 0.012997 0.0231411

General information on the benchmark

Namenormalized-PB06/OPT-BIGINT/submitted-PB06/roussel/factor/
normalized-factor-sizeN=460-sizeP=231-sizeQ=460-367423129-max.opb
MD5SUM74dac00a4979a8cd5d3f4292ad3ec004
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 -1
Optimality of the best value was proved NO
Number of variables106951
Total number of constraints318781
Number of constraints which are clauses318780
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 constraint106260
Number of terms in the objective function 231
Biggest coefficient in the objective function 1725436586697640946858688965569256363112777243042596638790631055949824
Number of bits for the biggest coefficient in the objective function 231
Sum of the numbers in the objective function 3450873173395281893717377931138512726225554486085193277581262111899647
Number of bits of the sum of numbers in the objective function 231
Biggest number in a constraint 2568425733177916751582514591250062824975751856847252861083144972201529372215371495172688738416791235950675277761805770367685269653410060480042878305982363696267199058168185838960773319279454451792623658074112
Number of bits of the biggest number in a constraint 690
Biggest sum of numbers in a constraint 10273702932711667006330058365000251299903007427389011444332579888806117119150450980598364387789362806715159761636352224959479775105866707576248572053899244884258622387609641105402680464792324232304944082188954
Number of bits of the biggest sum of numbers691
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	c Time Limit set via PBTIMEOUT to 1800
0.02	c INFO: OSL Context initialized.
0.02	c Integer values too big to handle...
0.02	c Parse Error 8
0.02	c Problem opening input file name: ROOT/tmp/node86/50365-1149960416/instance-50365-1149960416.opb
0.02	s UNKNOWN
0.02	c Exit Code: 0

Verifier Data (download as text)

ERROR: no interpretation found !

Watcher Data (download as text)

Enforcing CPU limit (will send SIGTERM then SIGKILL): 1800 seconds
Enforcing CPUTime (will send SIGXCPU) limit: 1830 seconds
Enforcing Stack size limit: 67108864 bytes

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

Enforcing memory limit (will send SIGKILL): 1843200 Kb
Enforcing VSIZE limit: 1887436800 bytes
command line: runsolver --timestamp -w ROOT/results/node86/watcher-50365-1149960416 -o ROOT/results/node86/solver-50365-1149960416 -C 1800 -M 1800 -S 64 ROOT/solvers/PB/PB06final/user10/bsolo ROOT/tmp/node86/50365-1149960416/instance-50365-1149960416.opb 

Current StackSize limit: 67108864 bytes

/proc/loadavg: 0.81 0.37 0.20 2/68 13194
/proc/meminfo: memFree=1253344/2055892 swapFree=4084792/4096564
[pid=13194] ppid=13192 vsize=18548 CPUtime=0
/proc/13194/stat : 13194 (runsolver) R 13192 13194 13148 0 -1 4194368 15 0 0 0 0 0 0 0 18 0 1 0 261680974 18993152 278 18446744073709551615 4194304 4264532 548682069056 18446744073709551615 208476369943 0 2147483391 4096 24578 0 0 0 17 0 0 0
/proc/13194/statm: 4637 278 242 17 0 2626 0

Child status: 0
Real time (s): 0.0231411
CPU time (s): 0.012997
CPU user time (s): 0.002999
CPU system time (s): 0.009998
CPU usage (%): 56.1642
Max. virtual memory (cumulated for all children) (Kb): 0
The end

Launcher Data (download as text)

Begin job on node86 on Sat Jun 10 17:26:57 UTC 2006


FILE ID= 50365-1149960416

PBS_JOBID= 385969

BENCH NAME= HOME/pub/bench/PB06/final/normalized-PB06/OPT-BIGINT/submitted-PB06/roussel/factor/normalized-factor-sizeN=460-sizeP=231-sizeQ=460-367423129-max.opb
COMMAND LINE= ROOT/solvers/PB/PB06final/user10/bsolo ROOT/tmp/node86/50365-1149960416/instance-50365-1149960416.opb
RUNSOLVER COMMAND LINE= runsolver  --timestamp  -w ROOT/results/node86/watcher-50365-1149960416 -o ROOT/results/node86/solver-50365-1149960416 -C 1800 -M 1800 -S 64  ROOT/solvers/PB/PB06final/user10/bsolo ROOT/tmp/node86/50365-1149960416/instance-50365-1149960416.opb

MD5SUM SOLVER= 05cada221eb1efaaae980ebc7509e7e8
MD5SUM BENCH=  74dac00a4979a8cd5d3f4292ad3ec004

RANDOM SEED= 695140099


/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.214
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	: 6006.19
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.214
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	: 5999.42
clflush size	: 64
cache_alignment	: 128
address sizes	: 36 bits physical, 48 bits virtual
power management:


/proc/meminfo:
MemTotal:      2055892 kB
MemFree:       1253680 kB
Buffers:         44164 kB
Cached:         680100 kB
SwapCached:       2928 kB
Active:         102312 kB
Inactive:       630632 kB
HighTotal:           0 kB
HighFree:            0 kB
LowTotal:      2055892 kB
LowFree:       1253680 kB
SwapTotal:     4096564 kB
SwapFree:      4084792 kB
Dirty:             164 kB
Writeback:           0 kB
Mapped:          15160 kB
Slab:            55828 kB
Committed_AS:   662052 kB
PageTables:       1300 kB
VmallocTotal: 536870911 kB
VmallocUsed:    264388 kB
VmallocChunk: 536606243 kB
HugePages_Total:     0
HugePages_Free:      0
Hugepagesize:     2048 kB


End job on node86 on Sat Jun 10 17:26:58 UTC 2006