Trace number 30772

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
absconPseudo 1OPT3089 1.79373 1.31712

General information on the benchmark

Namenormalized-PB06/OPT-SMALLINT/mps-v2-20-10/
MIPLIB/miplib/normalized-mps-v2-20-10-p0033.opb
MD5SUMbdb886a987b9ca760f19a56a745e3c06
Bench CategoryOPT-SMALLINT (optimisation, small integers)
Best result obtained on this benchmarkOPT
Best value of the objective obtained on this benchmark3089
Best CPU time to get the best result obtained on this benchmark0.016996
Has Objective FunctionYES
SatisfiableYES
(Un)Satisfiability was provedYES
Best value of the objective function 3089
Optimality of the best value was proved YES
Number of variables33
Total number of constraints15
Number of constraints which are clauses1
Number of constraints which are cardinality constraints (but not clauses)3
Number of constraints which are nor clauses,nor cardinality constraints11
Minimum length of a constraint2
Maximum length of a constraint19
Number of terms in the objective function 33
Biggest coefficient in the objective function 517
Number of bits for the biggest coefficient in the objective function 10
Sum of the numbers in the objective function 7276
Number of bits of the sum of numbers in the objective function 13
Biggest number in a constraint 1656
Number of bits of the biggest number in a constraint 11
Biggest sum of numbers in a constraint 7276
Number of bits of the biggest sum of numbers13
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 (download as text)

0.66	o 3095
0.80	o 3089
1.29	s OPTIMUM FOUND
1.29	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
1.29	v -x33
1.29	c nb removed universal constraints = 0
1.29	c nb removed unary constraints = 0
1.29	c cputime = 1017.0ms

Verifier Data (download as text)

OK	3089

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
Enforcing memory limit (will send SIGKILL): 1843200 Kb
Enforcing VSIZE limit: 1887436800 bytes
runsolver version 3.0.0 (c) roussel@cril.univ-artois.fr

command line: runsolver --timestamp -w ROOT/results/node79/watcher-30772-1149368864 -o ROOT/results/node79/solver-30772-1149368864 -C 1800 -M 1800 -S 64 java -server -Xms256M -Xmx1500M -cp ROOT/solvers/PB/PB06final/user2/absconPseudo1.jar abscon.Resolution ROOT/solvers/PB/PB06final/user2/configuration.xml 1 pseudo ROOT/tmp/node79/30772-1149368864/instance-30772-1149368864.opb 

Current StackSize limit: 67108864 bytes

/proc/loadavg: 0.91 0.94 0.96 2/67 6772
/proc/meminfo: memFree=1746792/2055892 swapFree=4085416/4096564
[pid=6772] ppid=6770 vsize=296 CPUtime=0
/proc/6772/stat : 6772 (java) R 6770 6772 6726 0 -1 0 196 0 0 0 0 0 0 0 19 0 1 0 202525009 303104 35 18446744073709551615 134512640 134570276 4294956352 18446744073709551615 2597812 0 0 4096 0 0 0 0 17 1 0 0
/proc/6772/statm: 74 35 27 14 0 5 0

Child status: 0
Real time (s): 1.31712
CPU time (s): 1.79373
CPU user time (s): 1.74073
CPU system time (s): 0.052991
CPU usage (%): 136.185
Max. virtual memory (cumulated for all children) (Kb): 0

Launcher Data (download as text)

Begin job on node79 on Sat Jun  3 21:07:44 UTC 2006


FILE ID= 30772-1149368864

PBS_JOBID= 312055

BENCH NAME= HOME/pub/bench/PB06//final/normalized-PB06/OPT-SMALLINT/mps-v2-20-10/MIPLIB/miplib/normalized-mps-v2-20-10-p0033.opb
COMMAND LINE= java -server -Xms256M -Xmx1500M -cp ROOT/solvers/PB/PB06final/user2/absconPseudo1.jar abscon.Resolution ROOT/solvers/PB/PB06final/user2/configuration.xml 1 pseudo  ROOT/tmp/node79/30772-1149368864/instance-30772-1149368864.opb
RUNSOLVER COMMAND LINE= runsolver  --timestamp  -w ROOT/results/node79/watcher-30772-1149368864 -o ROOT/results/node79/solver-30772-1149368864 -C 1800 -M 1800 -S 64  java -server -Xms256M -Xmx1500M -cp ROOT/solvers/PB/PB06final/user2/absconPseudo1.jar abscon.Resolution ROOT/solvers/PB/PB06final/user2/configuration.xml 1 pseudo  ROOT/tmp/node79/30772-1149368864/instance-30772-1149368864.opb

MD5SUM SOLVER= 4ca9ffbd6a9584cc3ed948681986e0cb 7445d5e2b836dfb8cfc1479ab819c771
MD5SUM BENCH=  bdb886a987b9ca760f19a56a745e3c06

RANDOM SEED= 768730749


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


/proc/meminfo:
MemTotal:      2055892 kB
MemFree:       1747000 kB
Buffers:         30200 kB
Cached:         217164 kB
SwapCached:       2400 kB
Active:          49068 kB
Inactive:       207064 kB
HighTotal:           0 kB
HighFree:            0 kB
LowTotal:      2055892 kB
LowFree:       1747000 kB
SwapTotal:     4096564 kB
SwapFree:      4085416 kB
Dirty:             276 kB
Writeback:           0 kB
Mapped:          16668 kB
Slab:            39396 kB
Committed_AS:   337764 kB
PageTables:       1304 kB
VmallocTotal: 536870911 kB
VmallocUsed:    264388 kB
VmallocChunk: 536606243 kB
HugePages_Total:     0
HugePages_Free:      0
Hugepagesize:     2048 kB


End job on node79 on Sat Jun  3 21:07:45 UTC 2006