Trace number 1858993

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-24OPT3951 0.023996 0.024262

General information on the benchmark

Namenormalized-PB07/OPT-SMALLINT-LIN/submittedPB07/
poldner/PB/testset/normalized-5_10.opb
MD5SUMba69a176dcc33e2f7eda6b169d4d1c84
Bench CategoryOPT-SMALLINT-LIN (optimisation, small integers, linear constraints)
Best result obtained on this benchmarkOPT
Best value of the objective obtained on this benchmark3951
Best CPU time to get the best result obtained on this benchmark0.007997
Has Objective FunctionYES
SatisfiableYES
(Un)Satisfiability was provedYES
Best value of the objective function 3951
Optimality of the best value was proved YES
Number of variables55
Total number of constraints60
Number of constraints which are clauses50
Number of constraints which are cardinality constraints (but not clauses)10
Number of constraints which are nor clauses,nor cardinality constraints0
Minimum length of a constraint2
Maximum length of a constraint5
Number of terms in the objective function 55
Biggest coefficient in the objective function 1772
Number of bits for the biggest coefficient in the objective function 11
Sum of the numbers in the objective function 25669
Number of bits of the sum of numbers in the objective function 15
Biggest number in a constraint 1772
Number of bits of the biggest number in a constraint 11
Biggest sum of numbers in a constraint 25669
Number of bits of the biggest sum of numbers15
Number of products (including duplicates)0
Sum of products size (including duplicates)0
Number of different products0
Sum of products size0

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.01	o 5048
0.00/0.01	o 4959
0.00/0.01	o 4847
0.00/0.01	o 4818
0.00/0.01	o 4066
0.00/0.01	o 4063
0.00/0.01	o 3996
0.00/0.02	o 3951
0.00/0.02	s OPTIMUM FOUND
0.00/0.02	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

Verifier Data 

OK	3951

Watcher Data 

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

command line: BIN/runsolver --timestamp -w /tmp/evaluation-result-1858993-1244929781/watcher-1858993-1244929781 -o /tmp/evaluation-result-1858993-1244929781/solver-1858993-1244929781 -C 1800 -W 2000 -M 1800 perl HOME/pbclasp HOME/instance-1858993-1244929781.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 1.00 3/64 17298
/proc/meminfo: memFree=1392600/2055920 swapFree=4191900/4192956
[pid=17298] ppid=17296 vsize=12268 CPUtime=0
/proc/17298/stat : 17298 (perl) R 17296 17298 16544 0 -1 4194304 443 0 0 0 0 0 0 0 18 0 1 0 160575309 12562432 410 1992294400 4194304 4206940 548682068784 18446744073709551615 266890439327 0 0 4224 16386 0 0 0 17 0 0 0
/proc/17298/statm: 3067 410 319 3 0 167 0

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

Child status: 0
Real time (s): 0.024262
CPU time (s): 0.023996
CPU user time (s): 0.018997
CPU system time (s): 0.004999
CPU usage (%): 98.9036
Max. virtual memory (cumulated for all children) (KiB): 0

getrusage(RUSAGE_CHILDREN,...) data:
user time used= 0.018997
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= 1598
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= 12

runsolver used 0.003999 second user time and 0.003999 second system time

The end

Launcher Data 

Begin job on node38 at 2009-06-13 23:49:41
IDJOB=1858993
IDBENCH=24968
IDSOLVER=687
FILE ID=node38/1858993-1244929781
PBS_JOBID= 9354654
Free space on /tmp= 66280 MiB

SOLVER NAME= pbclasp 2009-04-24
BENCH NAME= PB07/normalized-PB07/OPT-SMALLINT-LIN/submittedPB07/poldner/PB/testset/normalized-5_10.opb
COMMAND LINE= perl HOME/pbclasp BENCHNAME HOME TMPDIR
CONVERSION SCRIPT= PBconversionToLinear BENCHNAME
RUNSOLVER COMMAND LINE= BIN/runsolver --timestamp -w /tmp/evaluation-result-1858993-1244929781/watcher-1858993-1244929781 -o /tmp/evaluation-result-1858993-1244929781/solver-1858993-1244929781 -C 1800 -W 2000 -M 1800  perl HOME/pbclasp HOME/instance-1858993-1244929781.opb HOME HOME

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

MD5SUM BENCH= ba69a176dcc33e2f7eda6b169d4d1c84
RANDOM SEED=1323566269

node38.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.232
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.232
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:       1393208 kB
Buffers:         65872 kB
Cached:         502492 kB
SwapCached:        592 kB
Active:          46068 kB
Inactive:       535936 kB
HighTotal:           0 kB
HighFree:            0 kB
LowTotal:      2055920 kB
LowFree:       1393208 kB
SwapTotal:     4192956 kB
SwapFree:      4191900 kB
Dirty:            4688 kB
Writeback:           0 kB
Mapped:          22516 kB
Slab:            66684 kB
Committed_AS:   118680 kB
PageTables:       1464 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-1858993-1244929781.opb

Free space on /tmp at the end= 66276 MiB
End job on node38 at 2009-06-13 23:49:41