Trace number 431505

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
oree 0.1.2 alphaOPT3 0.039993 0.0401301

General information on the benchmark

Namenormalized-PB07/OPT-SMALLINT-NLC/submittedPB07/roussel/
factor-mod-B/factor-mod-size=5-P0=23-P1=11-B.opb
MD5SUM5cb8810690d9b87ecb9ebe5488675e03
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.001999
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 1982
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

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.00/0.00	c This is oree version 0.1.2 alpha
0.00/0.00	c (c) roussel@cril.univ-artois.fr
0.00/0.00	c using __gmp_expr<__gmpz_value, __gmpz_value>
0.00/0.00	c parsing...
0.00/0.00	c ...done
0.00/0.00	c #vars=40 #constraints=55 hasObjective=yes
0.00/0.00	c res. mode=mod
0.00/0.00	c VSIDS like heuristics
0.00/0.00	c complete search running
0.02/0.03	c nbDecision=94 #constraints=144
0.02/0.03	c linear search for optimum
0.02/0.03	o 17
0.02/0.03	c nbDecision=97 #constraints=145
0.02/0.03	o 3
0.02/0.03	c nbDecision=97 #constraints=147
0.02/0.03	
0.02/0.03	s OPTIMUM FOUND
0.02/0.03	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
0.02/0.03	v -x33 -x34 -x35 x36 x37 -x38 -x39 -x40
0.02/0.03	
0.02/0.03	c user time= 0.038994 s
0.02/0.03	c system time= 0.000999 s
0.02/0.03	c wall clock time=0.037744

Verifier Data (download as text)

OK	3

Conversion Script Data (download as text)

sed -e s/sizeproduct=/#sizeproduct=/ /tmp/evaluation/431505-1178006869/instance-431505-1178006869.opb
mv /tmp/evaluation/431505-1178006869/instance-431505-1178006869.opb.tmp /tmp/evaluation/431505-1178006869/instance-431505-1178006869.opb

Watcher Data (download as text)

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

command line: runsolver --timestamp -w ROOT/results/node14/watcher-431505-1178006869 -o ROOT/results/node14/solver-431505-1178006869 -C 1800 -W 3600 -M 1800 --output-limit 1,15 oree /tmp/evaluation/431505-1178006869/instance-431505-1178006869.opb mod 

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: 0.93 0.99 0.99 3/77 15561
/proc/meminfo: memFree=1772384/2055920 swapFree=4148856/4192956
[pid=15561] ppid=15559 vsize=1468 CPUtime=0
/proc/15561/stat : 15561 (oree) R 15559 15561 14920 0 -1 4194304 186 0 0 0 0 0 0 0 18 0 1 0 248604672 1503232 169 18446744073709551615 134512640 135812674 4294956704 18446744073709551615 135274709 0 0 4096 17474 0 0 0 17 1 0 0
/proc/15561/statm: 367 169 139 317 0 46 0

[startup+0.027305 s]
/proc/loadavg: 0.93 0.99 0.99 3/77 15561
/proc/meminfo: memFree=1772384/2055920 swapFree=4148856/4192956
[pid=15561] ppid=15559 vsize=1600 CPUtime=0.02
/proc/15561/stat : 15561 (oree) R 15559 15561 14920 0 -1 4194304 205 0 0 0 2 0 0 0 18 0 1 0 248604672 1638400 188 18446744073709551615 134512640 135812674 4294956704 18446744073709551615 135278909 0 0 4096 17474 0 0 0 17 1 0 0
/proc/15561/statm: 400 188 139 317 0 79 0
Current children cumulated CPU time (s) 0.02
Current children cumulated vsize (KiB) 1600

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

[startup+0.027305 s]
/proc/loadavg: 0.93 0.99 0.99 3/77 15561
/proc/meminfo: memFree=1772384/2055920 swapFree=4148856/4192956
[pid=15561] ppid=15559 vsize=1600 CPUtime=0.02
/proc/15561/stat : 15561 (oree) R 15559 15561 14920 0 -1 4194304 205 0 0 0 2 0 0 0 18 0 1 0 248604672 1638400 188 18446744073709551615 134512640 135812674 4294956704 18446744073709551615 135278909 0 0 4096 17474 0 0 0 17 1 0 0
/proc/15561/statm: 400 188 139 317 0 79 0
Current children cumulated CPU time (s) 0.02
Current children cumulated vsize (KiB) 1600

Child status: 0
Real time (s): 0.0401301
CPU time (s): 0.039993
CPU user time (s): 0.038994
CPU system time (s): 0.000999
CPU usage (%): 99.6583
Max. virtual memory (cumulated for all children) (KiB): 1600

getrusage(RUSAGE_CHILDREN,...) data:
user time used= 0.038994
system time used= 0.000999
maximum resident set size= 0
integral shared memory size= 0
integral unshared data size= 0
integral unshared stack size= 0
page reclaims= 263
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= 8
involuntary context switches= 1

runsolver used 0.001999 second user time and 0.005999 second system time

The end

Launcher Data (download as text)

Begin job on node14 on Tue May  1 08:07:49 UTC 2007

IDJOB= 431505
IDBENCH= 48056
IDSOLVER= 172
FILE ID= node14/431505-1178006869

PBS_JOBID= 4728270

Free space on /tmp= 66563 MiB

SOLVER NAME= oree 0.1.2 alpha
BENCH NAME= HOME/pub/bench/PB07/normalized-PB07/OPT-SMALLINT-NLC/submittedPB07/roussel/factor-mod-B/factor-mod-size=5-P0=23-P1=11-B.opb
COMMAND LINE= oree /tmp/evaluation/431505-1178006869/instance-431505-1178006869.opb mod           
CONVERSION COMMAND LINE= runsolver -w ROOT/results/node14/convwatcher-431505-1178006869 -o ROOT/results/node14/conversion-431505-1178006869 -C 600 -M 1800 /tmp/evaluation/431505-1178006869/substituteSizeProductKeyword /tmp/evaluation/431505-1178006869/instance-431505-1178006869.opb
CONVERSION RUNSOLVER STATUS CODE= 0
CONVERSION STATUS CODE= 0

RUNSOLVER COMMAND LINE= runsolver  --timestamp  -w ROOT/results/node14/watcher-431505-1178006869 -o ROOT/results/node14/solver-431505-1178006869 -C 1800 -W 3600 -M 1800 --output-limit 1,15  oree /tmp/evaluation/431505-1178006869/instance-431505-1178006869.opb mod           

META MD5SUM SOLVER= 51f0e1a06bbb15374571c5c5129b7f5e
MD5SUM BENCH=  5cb8810690d9b87ecb9ebe5488675e03

RANDOM SEED= 815600542

TIME LIMIT= 1800 seconds
MEMORY LIMIT= 1800 MiB

Linux node14.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.227
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.227
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:       1772856 kB
Buffers:         43808 kB
Cached:         146868 kB
SwapCached:      11556 kB
Active:          57976 kB
Inactive:       156436 kB
HighTotal:           0 kB
HighFree:            0 kB
LowTotal:      2055920 kB
LowFree:       1772856 kB
SwapTotal:     4192956 kB
SwapFree:      4148856 kB
Dirty:            1484 kB
Writeback:           0 kB
Mapped:          30796 kB
Slab:            54140 kB
Committed_AS:  7981592 kB
PageTables:       1784 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 node14 on Tue May  1 08:07:49 UTC 2007