Trace number 1859104

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. The first timestamp (if present) is estimated CPU time. The last timestamp is wall clock 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 NameAnswerobjCPU timeWall clock time
pbclasp 2009-04-24OPT3 0.222965 0.22213

General information on the benchmark

Namenormalized-PB07/OPT-SMALLINT-NLC/submittedPB07/
roussel/factor-mod-B/factor-mod-size=7-P0=89-P1=17-P2=37-B.opb
MD5SUMb8556c61a91d14749acba7836969b871
Bench CategoryOPT-SMALLINT-NLC (optimisation, small integers, non linear constraints)
Best result obtained on this benchmarkOPT
Best value of the objective obtained on this benchmark3
Best CPU time to get the best result obtained on this benchmark0.222965
Has Objective FunctionYES
SatisfiableYES
(Un)Satisfiability was provedYES
Best value of the objective function 3
Optimality of the best value was proved YES
Number of variables42
Total number of constraints5
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 constraints5
Minimum length of a constraint7
Maximum length of a constraint63
Number of terms in the objective function 7
Biggest coefficient in the objective function 64
Number of bits for the biggest coefficient in the objective function 7
Sum of the numbers in the objective function 127
Number of bits of the sum of numbers in the objective function 7
Biggest number in a constraint 8192
Number of bits of the biggest number in a constraint 14
Biggest sum of numbers in a constraint 32512
Number of bits of the biggest sum of numbers15
Number of products (including duplicates)98
Sum of products size (including duplicates)196
Number of different products98
Sum of products size196

Quality of the solution as a function of time


Download the above graph as a PDF file / as an EPS file

Solver Data 

0.00/0.00	c optimisation-statement found. OPT-category assumed.
0.00/0.05	o 63
0.00/0.07	o 47
0.00/0.07	o 31
0.00/0.07	o 3
0.00/0.21	s OPTIMUM FOUND
0.00/0.21	v x1 x2 -x3 -x4 -x5 -x6 -x7 x8 -x9 -x10 -x11 x12 x13 x14 x15 x16 x17 x18 x19 x20 x21 x22 x23 -x24 -x25 x26 -x27 x28 -x29 x30 -x31 -x32 -x33 -x34 -x35 -x36 x37 -x38 -x39 x40 -x41 x42 x43 x44 -x45 -x46 -x47 -x48 -x49 -x50 -x51 -x52 -x53 -x54 -x55 -x56 -x57 -x58 -x59 -x60 -x61 -x62 -x63 -x64 -x65 -x66 -x67 -x68 -x69 -x70 x71 x72 -x73 -x74 -x75 -x76 -x77 x78 x79 -x80 -x81 -x82 -x83 -x84 x85 x86 -x87 -x88 -x89 -x90 -x91 x92 x93 -x94 -x95 x96 -x97 x98 x99 x100 -x101 -x102 x103 -x104 x105 x106 x107 -x108 -x109 x110 -x111 x112 x113 x114 -x115 -x116 x117 -x118 x119 x120 x121 -x122 -x123 x124 -x125 x126 x127 x128 -x129 -x130 x131 -x132 x133 x134 x135 -x136 -x137 x138 -x139 x140

Verifier Data 

OK	3

Watcher Data 

runsolver version 3.2.9 (svn:492) (c) roussel@cril.univ-artois.fr

command line: BIN/runsolver --timestamp -w /tmp/evaluation-result-1859104-1245186662/watcher-1859104-1245186662 -o /tmp/evaluation-result-1859104-1245186662/solver-1859104-1245186662 -C 1800 -W 2000 -M 1800 perl HOME/pbclasp HOME/instance-1859104-1245186662.opb HOME HOME 

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): 2000 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
Current StackSize limit: 10240 KiB


[startup+0 s]
/proc/loadavg: 1.00 1.00 0.93 3/65 27569
/proc/meminfo: memFree=1834496/2055920 swapFree=4192812/4192956
[pid=27569] ppid=27567 vsize=12268 CPUtime=0
/proc/27569/stat : 27569 (perl) R 27567 27569 26968 0 -1 4194304 409 0 0 0 0 0 0 0 18 0 1 0 98088016 12562432 376 1992294400 4194304 4206940 548682068784 18446744073709551615 251279086305 0 0 4224 0 0 0 0 17 0 0 0
/proc/27569/statm: 3067 377 287 3 0 167 0

[startup+0.016956 s]
/proc/loadavg: 1.00 1.00 0.93 3/65 27569
/proc/meminfo: memFree=1834496/2055920 swapFree=4192812/4192956
[pid=27569] ppid=27567 vsize=12268 CPUtime=0
/proc/27569/stat : 27569 (perl) S 27567 27569 26968 0 -1 4194304 451 0 0 0 0 0 0 0 18 0 1 0 98088016 12562432 411 1992294400 4194304 4206940 548682068784 18446744073709551615 251288141716 0 0 4230 16384 18446744071563356171 0 0 17 1 0 0
/proc/27569/statm: 3067 411 319 3 0 167 0
Current children cumulated CPU time (s) 0
Current children cumulated vsize (KiB) 12268

[startup+0.101966 s]
/proc/loadavg: 1.00 1.00 0.93 3/65 27569
/proc/meminfo: memFree=1834496/2055920 swapFree=4192812/4192956
[pid=27569] ppid=27567 vsize=12268 CPUtime=0
/proc/27569/stat : 27569 (perl) S 27567 27569 26968 0 -1 4194304 451 0 0 0 0 0 0 0 18 0 1 0 98088016 12562432 411 1992294400 4194304 4206940 548682068784 18446744073709551615 251288141716 0 0 4230 16384 18446744071563356171 0 0 17 1 0 0
/proc/27569/statm: 3067 411 319 3 0 167 0
Current children cumulated CPU time (s) 0
Current children cumulated vsize (KiB) 12268

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

[startup+0.201978 s]
/proc/loadavg: 1.00 1.00 0.93 3/65 27569
/proc/meminfo: memFree=1834496/2055920 swapFree=4192812/4192956
[pid=27569] ppid=27567 vsize=12268 CPUtime=0
/proc/27569/stat : 27569 (perl) S 27567 27569 26968 0 -1 4194304 451 0 0 0 0 0 0 0 18 0 1 0 98088016 12562432 411 1992294400 4194304 4206940 548682068784 18446744073709551615 251288141716 0 0 4230 16384 18446744071563356171 0 0 17 1 0 0
/proc/27569/statm: 3067 411 319 3 0 167 0
Current children cumulated CPU time (s) 0
Current children cumulated vsize (KiB) 12268

Child status: 0
Real time (s): 0.22213
CPU time (s): 0.222965
CPU user time (s): 0.213967
CPU system time (s): 0.008998
CPU usage (%): 100.376
Max. virtual memory (cumulated for all children) (KiB): 12268

getrusage(RUSAGE_CHILDREN,...) data:
user time used= 0.213967
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= 1621
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= 26
involuntary context switches= 11

runsolver used 0.000999 second user time and 0.007998 second system time

The end

Launcher Data 

Begin job on node92 at 2009-06-16 23:11:02
IDJOB=1859104
IDBENCH=47915
IDSOLVER=687
FILE ID=node92/1859104-1245186662
PBS_JOBID= 9368275
Free space on /tmp= 66472 MiB

SOLVER NAME= pbclasp 2009-04-24
BENCH NAME= PB07/normalized-PB07/OPT-SMALLINT-NLC/submittedPB07/roussel/factor-mod-B/factor-mod-size=7-P0=89-P1=17-P2=37-B.opb
COMMAND LINE= perl HOME/pbclasp BENCHNAME HOME TMPDIR
CONVERSION SCRIPT= PBconversionToLinear BENCHNAME
RUNSOLVER COMMAND LINE= BIN/runsolver --timestamp -w /tmp/evaluation-result-1859104-1245186662/watcher-1859104-1245186662 -o /tmp/evaluation-result-1859104-1245186662/solver-1859104-1245186662 -C 1800 -W 2000 -M 1800  perl HOME/pbclasp HOME/instance-1859104-1245186662.opb HOME HOME

TIME LIMIT= 1800 seconds
MEMORY LIMIT= 1800 MiB
MAX NB THREAD= 0

MD5SUM BENCH= b8556c61a91d14749acba7836969b871
RANDOM SEED=642169853

node92.alineos.net Linux 2.6.9-22.EL.rootsmp #1 SMP Mon Oct 3 08:59:52 CEST 2005

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


/proc/meminfo:
MemTotal:      2055920 kB
MemFree:       1835040 kB
Buffers:         16392 kB
Cached:         140344 kB
SwapCached:        140 kB
Active:          51868 kB
Inactive:       118920 kB
HighTotal:           0 kB
HighFree:            0 kB
LowTotal:      2055920 kB
LowFree:       1835040 kB
SwapTotal:     4192956 kB
SwapFree:      4192812 kB
Dirty:            4476 kB
Writeback:           0 kB
Mapped:          23636 kB
Slab:            36012 kB
Committed_AS:    70104 kB
PageTables:       1472 kB
VmallocTotal: 536870911 kB
VmallocUsed:    264952 kB
VmallocChunk: 536605679 kB
HugePages_Total:     0
HugePages_Free:      0
Hugepagesize:     2048 kB

CONVERSION COMMAND LINE= PBconversionToLinear HOME/instance-1859104-1245186662.opb

Free space on /tmp at the end= 66468 MiB
End job on node92 at 2009-06-16 23:11:02