Trace number 46724

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 1OPT263 2.29265 1.894

General information on the benchmark

Namenormalized-PB06/OPT-SMALLINT/submitted-PB06/roussel/
factor/normalized-factor-size=9-P=263-Q=307.opb
MD5SUM53a15ed4efb5238584040600b2fccc57
Bench CategoryOPT-SMALLINT (optimisation, small integers)
Best result obtained on this benchmarkOPT
Best value of the objective obtained on this benchmark263
Best CPU time to get the best result obtained on this benchmark0.014997
Has Objective FunctionYES
SatisfiableYES
(Un)Satisfiability was provedYES
Best value of the objective function 263
Optimality of the best value was proved YES
Number of variables99
Total number of constraints244
Number of constraints which are clauses243
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 constraint81
Number of terms in the objective function 9
Biggest coefficient in the objective function 256
Number of bits for the biggest coefficient in the objective function 9
Sum of the numbers in the objective function 511
Number of bits of the sum of numbers in the objective function 9
Biggest number in a constraint 80741
Number of bits of the biggest number in a constraint 17
Biggest sum of numbers in a constraint 341862
Number of bits of the biggest sum of numbers19
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)

1.86	o 263
1.86	s OPTIMUM FOUND
1.86	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.86	v 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
1.86	v -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
1.86	v -x86 -x87 -x88 -x89 -x90 x91 x92 -x93 -x94 x95 x96 -x97 -x98 x99
1.86	c nb removed universal constraints = 0
1.86	c nb removed unary constraints = 0
1.86	c cputime = 1478.0ms

Verifier Data (download as text)

OK	263

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/node60/watcher-46724-1149845121 -o ROOT/results/node60/solver-46724-1149845121 -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/node60/46724-1149845121/instance-46724-1149845121.opb 

Current StackSize limit: 67108864 bytes

/proc/loadavg: 0.60 0.88 0.88 2/64 4963
/proc/meminfo: memFree=1327440/2055920 swapFree=4181460/4192956
[pid=4963] ppid=4961 vsize=1452 CPUtime=0
/proc/4963/stat : 4963 (java) R 4961 4963 4917 0 -1 0 108 0 0 0 0 0 0 0 19 0 1 0 250179906 1486848 81 18446744073709551615 134512640 134570276 4294956512 18446744073709551615 134517360 0 0 4096 0 0 0 0 17 1 0 0
/proc/4963/statm: 365 93 73 14 0 10 0

Child status: 0
Real time (s): 1.894
CPU time (s): 2.29265
CPU user time (s): 2.23266
CPU system time (s): 0.05999
CPU usage (%): 121.048
Max. virtual memory (cumulated for all children) (Kb): 0
The end

Launcher Data (download as text)

Begin job on node60 on Fri Jun  9 09:25:21 UTC 2006


FILE ID= 46724-1149845121

PBS_JOBID= 382372

BENCH NAME= HOME/pub/bench/PB06/final/normalized-PB06/OPT-SMALLINT/submitted-PB06/roussel/factor/normalized-factor-size=9-P=263-Q=307.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/node60/46724-1149845121/instance-46724-1149845121.opb
RUNSOLVER COMMAND LINE= runsolver  --timestamp  -w ROOT/results/node60/watcher-46724-1149845121 -o ROOT/results/node60/solver-46724-1149845121 -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/node60/46724-1149845121/instance-46724-1149845121.opb

MD5SUM SOLVER= 4ca9ffbd6a9584cc3ed948681986e0cb 7445d5e2b836dfb8cfc1479ab819c771
MD5SUM BENCH=  53a15ed4efb5238584040600b2fccc57

RANDOM SEED= 406438279


/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.257
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.257
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:       1327712 kB
Buffers:         42108 kB
Cached:         608728 kB
SwapCached:       3188 kB
Active:         130868 kB
Inactive:       528680 kB
HighTotal:           0 kB
HighFree:            0 kB
LowTotal:      2055920 kB
LowFree:       1327712 kB
SwapTotal:     4192956 kB
SwapFree:      4181460 kB
Dirty:             164 kB
Writeback:           0 kB
Mapped:          14752 kB
Slab:            54672 kB
Committed_AS:   514936 kB
PageTables:       1484 kB
VmallocTotal: 536870911 kB
VmallocUsed:    264952 kB
VmallocChunk: 536605679 kB
HugePages_Total:     0
HugePages_Free:      0
Hugepagesize:     2048 kB


End job on node60 on Fri Jun  9 09:25:23 UTC 2006