Trace number 49888

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.4OPT8 50.2344 50.2587

General information on the benchmark

Namenormalized-PB06/OPT-SMALLINT/submitted-PB06/manquiho/
logic_synthesis/normalized-m100_100_10_30.r.opb
MD5SUM80d844acb755df30f8eb4d34a1c5fb81
Bench CategoryOPT-SMALLINT (optimisation, small integers)
Best result obtained on this benchmarkOPT
Best value of the objective obtained on this benchmark8
Best CPU time to get the best result obtained on this benchmark0.378942
Has Objective FunctionYES
SatisfiableYES
(Un)Satisfiability was provedYES
Best value of the objective function 8
Optimality of the best value was proved YES
Number of variables100
Total number of constraints100
Number of constraints which are clauses100
Number of constraints which are cardinality constraints (but not clauses)0
Number of constraints which are nor clauses,nor cardinality constraints0
Minimum length of a constraint10
Maximum length of a constraint30
Number of terms in the objective function 100
Biggest coefficient in the objective function 1
Number of bits for the biggest coefficient in the objective function 1
Sum of the numbers in the objective function 100
Number of bits of the sum of numbers in the objective function 7
Biggest number in a constraint 1
Number of bits of the biggest number in a constraint 1
Biggest sum of numbers in a constraint 100
Number of bits of the biggest sum of numbers7
Number of products (including duplicates)0
Sum of products size (including duplicates)0
Number of different products0
Sum of products size0

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	c Pueblo version 1.4 (September 2005)
0.00	c Developed @ University of Michigan, Ann Arbor, MI
0.00	c  by Hossein Sheini
0.01	c starting to Solve
0.01	c #variables read: 100 - #constraints read: 101
0.01	o 13
0.01	o 12
0.01	o 11
0.02	o 10
7.74	o 9
42.73	o 8
50.25	c optimum objective found = 8
50.25	c total time              : 50.23 s
50.25	s OPTIMUM FOUND
50.25	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
50.25	v -x30 -x31 -x32 x33 -x34 -x35 -x36 -x37 x38 -x39 -x40 -x41 -x42 -x43 -x44 -x45 -x46 -x47 -x48 -x49 -x50 -x51 -x52 -x53 -x54 -x55
50.25	v -x56 -x57 -x58 -x59 -x60 -x61 -x62 -x63 -x64 x65 -x66 -x67 -x68 -x69 -x70 -x71 -x72 -x73 -x74 -x75 -x76 -x77 -x78 -x79 -x80 -x81
50.25	v -x82 -x83 -x84 x85 -x86 -x87 -x88 -x89 -x90 -x91 x92 -x93 -x94 -x95 -x96 -x97 -x98 -x99 -x100

Verifier Data (download as text)

OK	8

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/node82/watcher-49888-1149878237 -o ROOT/results/node82/solver-49888-1149878237 -C 1800 -M 1800 -S 64 ROOT/solvers/PB/PB06final/user8/Pueblo ROOT/tmp/node82/49888-1149878237/instance-49888-1149878237.opb 

Current StackSize limit: 67108864 bytes

/proc/loadavg: 1.03 1.03 0.97 2/68 20566
/proc/meminfo: memFree=1330752/2055892 swapFree=4087448/4096564
[pid=20566] ppid=20564 vsize=172 CPUtime=0
/proc/20566/stat : 20566 (Pueblo) D 20564 20566 20520 0 -1 4194304 37 0 0 0 0 0 0 0 19 0 1 0 245012947 176128 23 18446744073709551615 134512640 134579096 4294956688 18446744073709551615 7713716 0 2147483391 4096 0 18446744072100015398 0 0 17 1 0 0
/proc/20566/statm: 43 23 18 16 0 2 0

[startup+10.0029 s]
/proc/loadavg: 1.03 1.03 0.97 2/68 20566
/proc/meminfo: memFree=1330048/2055892 swapFree=4087448/4096564
[pid=20566] ppid=20564 vsize=3096 CPUtime=9.98
/proc/20566/stat : 20566 (Pueblo) R 20564 20566 20520 0 -1 4194304 401 0 0 0 996 2 0 0 25 0 1 0 245012947 3170304 373 18446744073709551615 134512640 134579096 4294956688 18446744073709551615 4294960144 0 0 4096 0 0 0 0 17 1 0 0
/proc/20566/statm: 774 373 205 16 0 214 0
Current children cumulated CPU time (s) 9.98
Current children cumulated vsize (Kb) 3096

[startup+20.0087 s]
/proc/loadavg: 1.02 1.03 0.97 2/68 20566
/proc/meminfo: memFree=1329920/2055892 swapFree=4087448/4096564
[pid=20566] ppid=20564 vsize=3196 CPUtime=19.99
/proc/20566/stat : 20566 (Pueblo) R 20564 20566 20520 0 -1 4194304 440 0 0 0 1993 6 0 0 25 0 1 0 245012947 3272704 412 18446744073709551615 134512640 134579096 4294956688 18446744073709551615 4294960144 0 0 4096 0 0 0 0 17 1 0 0
/proc/20566/statm: 799 412 205 16 0 239 0
Current children cumulated CPU time (s) 19.99
Current children cumulated vsize (Kb) 3196

[startup+30.0146 s]
/proc/loadavg: 1.02 1.03 0.97 2/68 20566
/proc/meminfo: memFree=1329984/2055892 swapFree=4087448/4096564
[pid=20566] ppid=20564 vsize=3288 CPUtime=29.99
/proc/20566/stat : 20566 (Pueblo) R 20564 20566 20520 0 -1 4194304 452 0 0 0 2989 10 0 0 25 0 1 0 245012947 3366912 424 18446744073709551615 134512640 134579096 4294956688 18446744073709551615 4294960144 0 0 4096 0 0 0 0 17 1 0 0
/proc/20566/statm: 822 424 205 16 0 262 0
Current children cumulated CPU time (s) 29.99
Current children cumulated vsize (Kb) 3288

[startup+40.0205 s]
/proc/loadavg: 1.02 1.03 0.97 2/68 20566
/proc/meminfo: memFree=1329920/2055892 swapFree=4087448/4096564
[pid=20566] ppid=20564 vsize=3384 CPUtime=40
/proc/20566/stat : 20566 (Pueblo) R 20564 20566 20520 0 -1 4194304 474 0 0 0 3984 16 0 0 25 0 1 0 245012947 3465216 446 18446744073709551615 134512640 134579096 4294956688 18446744073709551615 134527833 0 0 4096 0 0 0 0 17 1 0 0
/proc/20566/statm: 846 446 205 16 0 286 0
Current children cumulated CPU time (s) 40
Current children cumulated vsize (Kb) 3384

[startup+50.0274 s]
/proc/loadavg: 1.01 1.03 0.97 2/68 20566
/proc/meminfo: memFree=1329920/2055892 swapFree=4087448/4096564
[pid=20566] ppid=20564 vsize=3380 CPUtime=50
/proc/20566/stat : 20566 (Pueblo) R 20564 20566 20520 0 -1 4194304 481 0 0 0 4979 21 0 0 25 0 1 0 245012947 3461120 453 18446744073709551615 134512640 134579096 4294956688 18446744073709551615 134527726 0 0 4096 0 0 0 0 17 1 0 0
/proc/20566/statm: 845 453 205 16 0 285 0
Current children cumulated CPU time (s) 50
Current children cumulated vsize (Kb) 3380

Child status: 30
Real time (s): 50.2587
CPU time (s): 50.2344
CPU user time (s): 50.0194
CPU system time (s): 0.214967
CPU usage (%): 99.9515
Max. virtual memory (cumulated for all children) (Kb): 3384
The end

Launcher Data (download as text)

Begin job on node82 on Fri Jun  9 18:37:17 UTC 2006


FILE ID= 49888-1149878237

PBS_JOBID= 384548

BENCH NAME= HOME/pub/bench/PB06/final/normalized-PB06/OPT-SMALLINT/submitted-PB06/manquiho/logic_synthesis/normalized-m100_100_10_30.r.opb
COMMAND LINE= ROOT/solvers/PB/PB06final/user8/Pueblo ROOT/tmp/node82/49888-1149878237/instance-49888-1149878237.opb
RUNSOLVER COMMAND LINE= runsolver  --timestamp  -w ROOT/results/node82/watcher-49888-1149878237 -o ROOT/results/node82/solver-49888-1149878237 -C 1800 -M 1800 -S 64  ROOT/solvers/PB/PB06final/user8/Pueblo ROOT/tmp/node82/49888-1149878237/instance-49888-1149878237.opb

MD5SUM SOLVER= 80c24de60e85bc4a9ec18ca4764e7dff
MD5SUM BENCH=  80d844acb755df30f8eb4d34a1c5fb81

RANDOM SEED= 94277014


/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.265
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	: 6006.17
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.265
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	: 5999.43
clflush size	: 64
cache_alignment	: 128
address sizes	: 36 bits physical, 48 bits virtual
power management:


/proc/meminfo:
MemTotal:      2055892 kB
MemFree:       1330960 kB
Buffers:         36648 kB
Cached:         624652 kB
SwapCached:       2788 kB
Active:          98776 kB
Inactive:       571240 kB
HighTotal:           0 kB
HighFree:            0 kB
LowTotal:      2055892 kB
LowFree:       1330960 kB
SwapTotal:     4096564 kB
SwapFree:      4087448 kB
Dirty:             188 kB
Writeback:           0 kB
Mapped:          14560 kB
Slab:            41276 kB
Committed_AS:   612476 kB
PageTables:       1472 kB
VmallocTotal: 536870911 kB
VmallocUsed:    264388 kB
VmallocChunk: 536606243 kB
HugePages_Total:     0
HugePages_Free:      0
Hugepagesize:     2048 kB


End job on node82 on Fri Jun  9 18:38:07 UTC 2006