Trace number 429192

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
Pueblo 1.4OPT3 0.18797 0.191446

General information on the benchmark

Namenormalized-PB07/OPT-SMALLINT-NLC/submittedPB07/
roussel/factor-mod-B/factor-mod-size=6-P0=19-P1=53-P2=37-B.opb
MD5SUMfe9afe61a3128dc2392b842924791b6c
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.024995
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 variables36
Total number of constraints5
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 constraints5
Minimum length of a constraint6
Maximum length of a constraint48
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 8064
Number of bits of the biggest sum of numbers13
Number of products (including duplicates)72
Sum of products size (including duplicates)144
Number of different products72
Sum of products size144

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 Pueblo version 1.4 (September 2005)
0.00/0.00	c Developed @ University of Michigan, Ann Arbor, MI
0.00/0.00	c  by Hossein Sheini
0.00/0.00	c starting to Solve
0.00/0.00	c #variables read: 108 - #constraints read: 152
0.00/0.02	o 33
0.00/0.06	o 5
0.00/0.06	o 3
0.09/0.19	c optimum objective found = 3
0.09/0.19	c total time              : 0.18 s
0.09/0.19	s OPTIMUM FOUND
0.09/0.19	v x1 x2 -x3 -x4 -x5 -x6 x7 -x8 x9 -x10 -x11 -x12 x13 -x14 x15 -x16 -x17 -x18 x37 x38 -x39 -x40 -x41 -x42 -x43 -x44 -x45 -x46 -x47 -x48
0.09/0.19	v x49 x50 -x51 -x52 -x53 -x54 -x55 -x56 -x57 -x58 -x59 -x60 -x61 -x62 -x63 -x64 -x65 -x66 -x67 -x68 -x69 -x70 -x71 -x72 x19 x20 x21
0.09/0.19	v x22 -x23 -x24 -x25 -x26 -x27 -x28 -x29 -x30 x73 x74 x75 x76 -x77 -x78 -x79 -x80 -x81 -x82 -x83 -x84 x85 x86 x87 x88 -x89 -x90 -x91
0.09/0.19	v -x92 -x93 -x94 -x95 -x96 -x97 -x98 -x99 -x100 -x101 -x102 -x103 -x104 -x105 -x106 -x107 -x108 x31 -x32 -x33 -x34 -x35 -x36

Verifier Data (download as text)

OK	3

Conversion Script Data (download as text)

Linearizing /tmp/evaluation/429192-1177981552/instance-429192-1177981552.opb

Watcher Data (download as text)

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

command line: runsolver --timestamp -w ROOT/results/node70/watcher-429192-1177981552 -o ROOT/results/node70/solver-429192-1177981552 -C 1800 -W 3600 -M 1800 --output-limit 1,15 Pueblo /tmp/evaluation/429192-1177981552/instance-429192-1177981552.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: 0.83 1.03 0.98 3/64 30805
/proc/meminfo: memFree=1804416/2055920 swapFree=4183764/4192956
[pid=30805] ppid=30803 vsize=2552 CPUtime=0
/proc/30805/stat : 30805 (Pueblo) R 30803 30805 19703 0 -1 4194304 263 0 0 0 0 0 0 0 18 0 1 0 237692578 2613248 234 18446744073709551615 134512640 134579096 4294956704 18446744073709551615 8879831 0 0 4096 0 0 0 0 17 1 0 0
/proc/30805/statm: 638 234 199 16 0 77 0

[startup+0.0118271 s]
/proc/loadavg: 0.83 1.03 0.98 3/64 30805
/proc/meminfo: memFree=1804416/2055920 swapFree=4183764/4192956
[pid=30805] ppid=30803 vsize=2556 CPUtime=0
/proc/30805/stat : 30805 (Pueblo) R 30803 30805 19703 0 -1 4194304 282 0 0 0 0 0 0 0 18 0 1 0 237692578 2617344 253 18446744073709551615 134512640 134579096 4294956704 18446744073709551615 134528719 0 0 4096 0 0 0 0 17 1 0 0
/proc/30805/statm: 639 253 205 16 0 78 0
Current children cumulated CPU time (s) 0
Current children cumulated vsize (KiB) 2556

[startup+0.101835 s]
/proc/loadavg: 0.83 1.03 0.98 3/64 30805
/proc/meminfo: memFree=1804416/2055920 swapFree=4183764/4192956
[pid=30805] ppid=30803 vsize=2556 CPUtime=0.09
/proc/30805/stat : 30805 (Pueblo) R 30803 30805 19703 0 -1 4194304 292 0 0 0 9 0 0 0 18 0 1 0 237692578 2617344 263 18446744073709551615 134512640 134579096 4294956704 18446744073709551615 4294960144 0 0 4096 0 0 0 0 17 1 0 0
/proc/30805/statm: 639 263 205 16 0 78 0
Current children cumulated CPU time (s) 0.09
Current children cumulated vsize (KiB) 2556

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

Child status: 30
Real time (s): 0.191446
CPU time (s): 0.18797
CPU user time (s): 0.186971
CPU system time (s): 0.000999
CPU usage (%): 98.1843
Max. virtual memory (cumulated for all children) (KiB): 2556

getrusage(RUSAGE_CHILDREN,...) data:
user time used= 0.186971
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= 301
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= 13
involuntary context switches= 1

runsolver used 0.003999 second user time and 0.002999 second system time

The end

Launcher Data (download as text)

Begin job on node70 on Tue May  1 01:05:52 UTC 2007

IDJOB= 429192
IDBENCH= 47891
IDSOLVER= 165
FILE ID= node70/429192-1177981552

PBS_JOBID= 4728169

Free space on /tmp= 66562 MiB

SOLVER NAME= Pueblo 1.4
BENCH NAME= HOME/pub/bench/PB07/normalized-PB07/OPT-SMALLINT-NLC/submittedPB07/roussel/factor-mod-B/factor-mod-size=6-P0=19-P1=53-P2=37-B.opb
COMMAND LINE= Pueblo /tmp/evaluation/429192-1177981552/instance-429192-1177981552.opb
CONVERSION COMMAND LINE= runsolver -w ROOT/results/node70/convwatcher-429192-1177981552 -o ROOT/results/node70/conversion-429192-1177981552 -C 600 -M 1800 PBconversionToLinear /tmp/evaluation/429192-1177981552/instance-429192-1177981552.opb
CONVERSION RUNSOLVER STATUS CODE= 0
CONVERSION STATUS CODE= 0

RUNSOLVER COMMAND LINE= runsolver  --timestamp  -w ROOT/results/node70/watcher-429192-1177981552 -o ROOT/results/node70/solver-429192-1177981552 -C 1800 -W 3600 -M 1800 --output-limit 1,15  Pueblo /tmp/evaluation/429192-1177981552/instance-429192-1177981552.opb

META MD5SUM SOLVER= 9ebec3e8d890fdeefad01654ad9b68b7
MD5SUM BENCH=  fe9afe61a3128dc2392b842924791b6c

RANDOM SEED= 971665577

TIME LIMIT= 1800 seconds
MEMORY LIMIT= 1800 MiB

Linux node70.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.218
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.218
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:       1804824 kB
Buffers:         13580 kB
Cached:         176064 kB
SwapCached:       2660 kB
Active:          56956 kB
Inactive:       142084 kB
HighTotal:           0 kB
HighFree:            0 kB
LowTotal:      2055920 kB
LowFree:       1804824 kB
SwapTotal:     4192956 kB
SwapFree:      4183764 kB
Dirty:            2484 kB
Writeback:           0 kB
Mapped:          15456 kB
Slab:            38080 kB
Committed_AS:  4258428 kB
PageTables:       1396 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= 66562 MiB

End job on node70 on Tue May  1 01:05:53 UTC 2007