Trace number 430245

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.546916 0.549595

General information on the benchmark

Namenormalized-PB07/OPT-SMALLINT-NLC/submittedPB07/roussel/
factor-mod-B/factor-mod-size=6-P0=59-P1=37-B.opb
MD5SUMecd8e533e3641a4c2c49e9e1d3d0ce44
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.013997
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 variables18
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 constraint6
Maximum length of a constraint42
Number of terms in the objective function 6
Biggest coefficient in the objective function 32
Number of bits for the biggest coefficient in the objective function 6
Sum of the numbers in the objective function 63
Number of bits of the sum of numbers in the objective function 6
Biggest number in a constraint 2048
Number of bits of the biggest number in a constraint 12
Biggest sum of numbers in a constraint 8008
Number of bits of the biggest sum of numbers13
Number of products (including duplicates)36
Sum of products size (including duplicates)72
Number of different products36
Sum of products size72

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=54 #constraints=77 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.19/0.28	c restart after 401 decisions
0.29/0.38	c nbDecision=500 #constraints=563
0.49/0.51	c nbDecision=599 #constraints=661
0.49/0.51	c linear search for optimum
0.49/0.51	o 33
0.49/0.53	c nbDecision=616 #constraints=673
0.49/0.53	o 17
0.49/0.54	c nbDecision=622 #constraints=677
0.49/0.54	o 5
0.49/0.54	c nbDecision=624 #constraints=679
0.49/0.54	o 3
0.49/0.54	c nbDecision=624 #constraints=681
0.49/0.54	
0.49/0.54	s OPTIMUM FOUND
0.49/0.54	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.49/0.54	v x31 x32 -x33 -x34 -x35 -x36 x37 x38 -x39 -x40 -x41 -x42 -x43 -x44 -x45 -x46 -x47 -x48 x49 x50 -x51 -x52 -x53 -x54
0.49/0.54	
0.49/0.54	c user time= 0.542917 s
0.49/0.54	c system time= 0.002999 s
0.49/0.54	c wall clock time=0.546119

Verifier Data (download as text)

OK	3

Conversion Script Data (download as text)

sed -e s/sizeproduct=/#sizeproduct=/ /tmp/evaluation/430245-1177993319/instance-430245-1177993319.opb
mv /tmp/evaluation/430245-1177993319/instance-430245-1177993319.opb.tmp /tmp/evaluation/430245-1177993319/instance-430245-1177993319.opb

Watcher Data (download as text)

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

command line: runsolver --timestamp -w ROOT/results/node61/watcher-430245-1177993319 -o ROOT/results/node61/solver-430245-1177993319 -C 1800 -W 3600 -M 1800 --output-limit 1,15 oree /tmp/evaluation/430245-1177993319/instance-430245-1177993319.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.65 0.87 0.94 3/64 8141
/proc/meminfo: memFree=1833808/2055920 swapFree=4184156/4192956
[pid=8141] ppid=8139 vsize=1468 CPUtime=0
/proc/8141/stat : 8141 (oree) R 8139 8141 7265 0 -1 4194304 188 0 0 0 0 0 0 0 19 0 1 0 211295547 1503232 171 18446744073709551615 134512640 135812674 4294956704 18446744073709551615 135274709 0 0 4096 17474 0 0 0 17 0 0 0
/proc/8141/statm: 367 171 139 317 0 46 0

[startup+0.0723841 s]
/proc/loadavg: 0.65 0.87 0.94 3/64 8141
/proc/meminfo: memFree=1833808/2055920 swapFree=4184156/4192956
[pid=8141] ppid=8139 vsize=1864 CPUtime=0.07
/proc/8141/stat : 8141 (oree) R 8139 8141 7265 0 -1 4194304 268 0 0 0 7 0 0 0 19 0 1 0 211295547 1908736 251 18446744073709551615 134512640 135812674 4294956704 18446744073709551615 135272624 0 0 4096 17474 0 0 0 17 0 0 0
/proc/8141/statm: 466 251 139 317 0 145 0
Current children cumulated CPU time (s) 0.07
Current children cumulated vsize (KiB) 1864

[startup+0.101388 s]
/proc/loadavg: 0.65 0.87 0.94 3/64 8141
/proc/meminfo: memFree=1833808/2055920 swapFree=4184156/4192956
[pid=8141] ppid=8139 vsize=1864 CPUtime=0.09
/proc/8141/stat : 8141 (oree) R 8139 8141 7265 0 -1 4194304 290 0 0 0 9 0 0 0 20 0 1 0 211295547 1908736 273 18446744073709551615 134512640 135812674 4294956704 18446744073709551615 135284625 0 0 4096 17474 0 0 0 17 0 0 0
/proc/8141/statm: 466 273 139 317 0 145 0
Current children cumulated CPU time (s) 0.09
Current children cumulated vsize (KiB) 1864

[startup+0.301405 s]
/proc/loadavg: 0.65 0.87 0.94 3/64 8141
/proc/meminfo: memFree=1833808/2055920 swapFree=4184156/4192956
[pid=8141] ppid=8139 vsize=2384 CPUtime=0.29
/proc/8141/stat : 8141 (oree) R 8139 8141 7265 0 -1 4194304 405 0 0 0 29 0 0 0 21 0 1 0 211295547 2441216 388 18446744073709551615 134512640 135812674 4294956704 18446744073709551615 134713847 0 0 4096 17474 0 0 0 17 0 0 0
/proc/8141/statm: 596 388 139 317 0 275 0
Current children cumulated CPU time (s) 0.29
Current children cumulated vsize (KiB) 2384

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

[startup+0.501424 s]
/proc/loadavg: 0.65 0.87 0.94 3/64 8141
/proc/meminfo: memFree=1833808/2055920 swapFree=4184156/4192956
[pid=8141] ppid=8139 vsize=2648 CPUtime=0.49
/proc/8141/stat : 8141 (oree) R 8139 8141 7265 0 -1 4194304 492 0 0 0 49 0 0 0 23 0 1 0 211295547 2711552 475 18446744073709551615 134512640 135812674 4294956704 18446744073709551615 134592832 0 0 4096 17474 0 0 0 17 0 0 0
/proc/8141/statm: 662 475 139 317 0 341 0
Current children cumulated CPU time (s) 0.49
Current children cumulated vsize (KiB) 2648

Child status: 0
Real time (s): 0.549595
CPU time (s): 0.546916
CPU user time (s): 0.542917
CPU system time (s): 0.003999
CPU usage (%): 99.5126
Max. virtual memory (cumulated for all children) (KiB): 2648

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

runsolver used 0.002999 second user time and 0.004999 second system time

The end

Launcher Data (download as text)

Begin job on node61 on Tue May  1 04:21:59 UTC 2007

IDJOB= 430245
IDBENCH= 47966
IDSOLVER= 172
FILE ID= node61/430245-1177993319

PBS_JOBID= 4728256

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=6-P0=59-P1=37-B.opb
COMMAND LINE= oree /tmp/evaluation/430245-1177993319/instance-430245-1177993319.opb mod           
CONVERSION COMMAND LINE= runsolver -w ROOT/results/node61/convwatcher-430245-1177993319 -o ROOT/results/node61/conversion-430245-1177993319 -C 600 -M 1800 /tmp/evaluation/430245-1177993319/substituteSizeProductKeyword /tmp/evaluation/430245-1177993319/instance-430245-1177993319.opb
CONVERSION RUNSOLVER STATUS CODE= 0
CONVERSION STATUS CODE= 0

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

META MD5SUM SOLVER= 51f0e1a06bbb15374571c5c5129b7f5e
MD5SUM BENCH=  ecd8e533e3641a4c2c49e9e1d3d0ce44

RANDOM SEED= 813230211

TIME LIMIT= 1800 seconds
MEMORY LIMIT= 1800 MiB

Linux node61.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.240
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.240
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:       1834216 kB
Buffers:         24064 kB
Cached:         135008 kB
SwapCached:       2904 kB
Active:          83984 kB
Inactive:        84764 kB
HighTotal:           0 kB
HighFree:            0 kB
LowTotal:      2055920 kB
LowFree:       1834216 kB
SwapTotal:     4192956 kB
SwapFree:      4184156 kB
Dirty:            1500 kB
Writeback:           0 kB
Mapped:          15664 kB
Slab:            39116 kB
Committed_AS:  1167144 kB
PageTables:       1388 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 node61 on Tue May  1 04:22:00 UTC 2007