Trace number 430036

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 102OPT3 0.448931 0.374972

General information on the benchmark

Namenormalized-PB07/OPT-SMALLINT-NLC/submittedPB07/roussel/
factor-mod-B/factor-mod-size=5-P0=13-P1=13-B.opb
MD5SUM7e1a1d048dc92de7feed905686f8ac31
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.004999
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 variables15
Total number of constraints3
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 constraints3
Minimum length of a constraint5
Maximum length of a constraint30
Number of terms in the objective function 5
Biggest coefficient in the objective function 16
Number of bits for the biggest coefficient in the objective function 5
Sum of the numbers in the objective function 31
Number of bits of the sum of numbers in the objective function 5
Biggest number in a constraint 512
Number of bits of the biggest number in a constraint 10
Biggest sum of numbers in a constraint 1962
Number of bits of the biggest sum of numbers11
Number of products (including duplicates)25
Sum of products size (including duplicates)50
Number of different products25
Sum of products size50

Solver Data (download as text)

0.34/0.36	o 3
0.34/0.36	s OPTIMUM FOUND
0.34/0.36	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
0.34/0.36	v -x31 -x32 -x33 -x34 -x35 -x36 -x37 -x38 -x39 -x40
0.34/0.36	c nb removed universal constraints = 0
0.34/0.36	c nb removed unary constraints = 0
0.34/0.36	c cputime = 170.0ms

Verifier Data (download as text)

OK	3

Conversion Script Data (download as text)

Linearizing /tmp/evaluation/430036-1177990979/instance-430036-1177990979.opb

Watcher Data (download as text)

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

command line: runsolver --timestamp -w ROOT/results/node62/watcher-430036-1177990979 -o ROOT/results/node62/solver-430036-1177990979 -C 1800 -W 3600 -M 1800 --output-limit 1,15 java -Xms1600M -Xmx1600M -jar absconPseudo1.jar configuration.xml 1 pseudo /tmp/evaluation/430036-1177990979/instance-430036-1177990979.opb 

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): 3600 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
Solver output will be limited to a maximum of 15728640 bytes. The first 1048576 bytes and the last 14680064 bytes will be preserved
Current StackSize limit: 10240 KiB


[startup+0 s]
/proc/loadavg: 1.10 1.08 1.00 2/64 30613
/proc/meminfo: memFree=1831728/2055920 swapFree=4184544/4192956
[pid=30613] ppid=30611 vsize=1504 CPUtime=0
/proc/30613/stat : 30613 (java) R 30611 30613 28043 0 -1 0 60 0 0 0 0 0 0 0 18 0 1 0 117673957 1540096 45 18446744073709551615 134512640 134550740 4294956608 18446744073709551615 8108685 0 0 4096 0 0 0 0 17 1 0 0
/proc/30613/statm: 379 51 38 9 0 9 0

[startup+0.050898 s]
/proc/loadavg: 1.10 1.08 1.00 2/64 30613
/proc/meminfo: memFree=1831728/2055920 swapFree=4184544/4192956
[pid=30613] ppid=30611 vsize=1786852 CPUtime=0.03
/proc/30613/stat : 30613 (java) S 30611 30613 28043 0 -1 0 2884 0 1 0 2 1 0 0 18 0 9 0 117673957 1829736448 2465 18446744073709551615 134512640 134550740 4294956464 18446744073709551615 4294960144 0 0 0 23759 18446744073709551615 0 0 17 1 0 0
/proc/30613/statm: 446713 2465 946 9 0 441715 0
Current children cumulated CPU time (s) 0.03
Current children cumulated vsize (KiB) 1786852

[startup+0.105077 s]
/proc/loadavg: 1.10 1.08 1.00 2/64 30613
/proc/meminfo: memFree=1831728/2055920 swapFree=4184544/4192956
[pid=30613] ppid=30611 vsize=1790276 CPUtime=0.1
/proc/30613/stat : 30613 (java) S 30611 30613 28043 0 -1 0 4413 0 1 0 8 2 0 0 18 0 9 0 117673957 1833242624 3853 18446744073709551615 134512640 134550740 4294956464 18446744073709551615 4294960144 0 0 0 23759 18446744073709551615 0 0 17 1 0 0
/proc/30613/statm: 447569 3853 1735 9 0 442161 0
Current children cumulated CPU time (s) 0.1
Current children cumulated vsize (KiB) 1790276

[startup+0.301102 s]
/proc/loadavg: 1.10 1.08 1.00 2/64 30613
/proc/meminfo: memFree=1831728/2055920 swapFree=4184544/4192956
[pid=30613] ppid=30611 vsize=1790304 CPUtime=0.34
/proc/30613/stat : 30613 (java) S 30611 30613 28043 0 -1 0 7462 0 1 0 30 4 0 0 18 0 9 0 117673957 1833271296 6861 18446744073709551615 134512640 134550740 4294956464 18446744073709551615 4294960144 0 0 0 23759 18446744073709551615 0 0 17 1 0 0
/proc/30613/statm: 447576 6861 1862 9 0 442161 0
Current children cumulated CPU time (s) 0.34
Current children cumulated vsize (KiB) 1790304

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

Child status: 0
Real time (s): 0.374972
CPU time (s): 0.448931
CPU user time (s): 0.385941
CPU system time (s): 0.06299
CPU usage (%): 119.724
Max. virtual memory (cumulated for all children) (KiB): 1790304

getrusage(RUSAGE_CHILDREN,...) data:
user time used= 0.385941
system time used= 0.06299
maximum resident set size= 0
integral shared memory size= 0
integral unshared data size= 0
integral unshared stack size= 0
page reclaims= 9000
page faults= 1
swaps= 0
block input operations= 0
block output operations= 0
messages sent= 0
messages received= 0
signals received= 0
voluntary context switches= 192
involuntary context switches= 27

runsolver used 0.001999 second user time and 0.005999 second system time

The end

Launcher Data (download as text)

Begin job on node62 on Tue May  1 03:42:59 UTC 2007

IDJOB= 430036
IDBENCH= 47952
IDSOLVER= 155
FILE ID= node62/430036-1177990979

PBS_JOBID= 4728136

Free space on /tmp= 66563 MiB

SOLVER NAME= absconPseudo 102
BENCH NAME= HOME/pub/bench/PB07/normalized-PB07/OPT-SMALLINT-NLC/submittedPB07/roussel/factor-mod-B/factor-mod-size=5-P0=13-P1=13-B.opb
COMMAND LINE= java -Xms1600M -Xmx1600M  -jar absconPseudo1.jar configuration.xml 1 pseudo /tmp/evaluation/430036-1177990979/instance-430036-1177990979.opb            
CONVERSION COMMAND LINE= runsolver -w ROOT/results/node62/convwatcher-430036-1177990979 -o ROOT/results/node62/conversion-430036-1177990979 -C 600 -M 1800 PBconversionToLinear /tmp/evaluation/430036-1177990979/instance-430036-1177990979.opb
CONVERSION RUNSOLVER STATUS CODE= 0
CONVERSION STATUS CODE= 0

RUNSOLVER COMMAND LINE= runsolver  --timestamp  -w ROOT/results/node62/watcher-430036-1177990979 -o ROOT/results/node62/solver-430036-1177990979 -C 1800 -W 3600 -M 1800 --output-limit 1,15  java -Xms1600M -Xmx1600M  -jar absconPseudo1.jar configuration.xml 1 pseudo /tmp/evaluation/430036-1177990979/instance-430036-1177990979.opb            

META MD5SUM SOLVER= af6648fa1ac31d79961ee160b5e03dc5
MD5SUM BENCH=  7e1a1d048dc92de7feed905686f8ac31

RANDOM SEED= 287454029

TIME LIMIT= 1800 seconds
MEMORY LIMIT= 1800 MiB

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

/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.216
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.216
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:       1832136 kB
Buffers:          8668 kB
Cached:         142168 kB
SwapCached:       2232 kB
Active:          66472 kB
Inactive:        94796 kB
HighTotal:           0 kB
HighFree:            0 kB
LowTotal:      2055920 kB
LowFree:       1832136 kB
SwapTotal:     4192956 kB
SwapFree:      4184544 kB
Dirty:            1872 kB
Writeback:           0 kB
Mapped:          16892 kB
Slab:            48404 kB
Committed_AS:  1327952 kB
PageTables:       1464 kB
VmallocTotal: 536870911 kB
VmallocUsed:    264952 kB
VmallocChunk: 536605679 kB
HugePages_Total:     0
HugePages_Free:      0
Hugepagesize:     2048 kB

Free space on /tmp at the end= 66563 MiB

End job on node62 on Tue May  1 03:43:00 UTC 2007