Trace number 366670

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 alphaOPT2 0.364944 0.365549

General information on the benchmark

Namenormalized-PB06/OPT-SMALLINT/submitted-PB06/manquiho/
logic_synthesis/normalized-m50_100_90_90.r.opb
MD5SUM4da887ca4bb57adc53b30ca1ea0acd93
Bench CategoryOPT-SMALLINT (optimisation, small integers)
Best result obtained on this benchmarkOPT
Best value of the objective obtained on this benchmark2
Best CPU time to get the best result obtained on this benchmark0.020996
Has Objective FunctionYES
SatisfiableYES
(Un)Satisfiability was provedYES
Best value of the objective function 2
Optimality of the best value was proved YES
Number of variables100
Total number of constraints50
Number of constraints which are clauses50
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 constraint90
Maximum length of a constraint90
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

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.01	c ...done
0.00/0.01	c #vars=100 #constraints=51 hasObjective=yes
0.00/0.02	c res. mode=mod
0.00/0.02	c VSIDS like heuristics
0.00/0.02	c complete search running
0.00/0.02	c nbDecision=98 #constraints=51
0.00/0.02	c linear search for optimum
0.00/0.02	o 2
0.29/0.36	c nbDecision=98 #constraints=141
0.29/0.36	
0.29/0.36	s OPTIMUM FOUND
0.29/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
0.29/0.36	v -x29 -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
0.29/0.36	v -x55 -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
0.29/0.36	v -x81 -x82 -x83 -x84 -x85 -x86 -x87 -x88 -x89 x90 -x91 -x92 -x93 -x94 -x95 -x96 -x97 -x98 -x99 x100
0.29/0.36	
0.29/0.36	c user time= 0.360945 s
0.29/0.36	c system time= 0.003999 s
0.29/0.36	c wall clock time=0.362961

Verifier Data (download as text)

OK	2

Watcher Data (download as text)

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

command line: runsolver --timestamp -w ROOT/results/node62/watcher-366670-1177000056 -o ROOT/results/node62/solver-366670-1177000056 -C 1800 -W 3600 -M 1800 --output-limit 1,15 oree /tmp/evaluation/366670-1177000056/instance-366670-1177000056.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.91 0.95 0.90 3/64 21721
/proc/meminfo: memFree=1683496/2055920 swapFree=4184556/4192956
[pid=21721] ppid=21719 vsize=1468 CPUtime=0
/proc/21721/stat : 21721 (oree) R 21719 21721 20721 0 -1 4194304 182 0 0 0 0 0 0 0 18 0 1 0 18581587 1503232 164 18446744073709551615 134512640 135812674 4294956704 18446744073709551615 135274709 0 0 4096 17474 0 0 0 17 1 0 0
/proc/21721/statm: 367 165 130 317 0 46 0

[startup+0.0552669 s]
/proc/loadavg: 0.91 0.95 0.90 3/64 21721
/proc/meminfo: memFree=1683496/2055920 swapFree=4184556/4192956
[pid=21721] ppid=21719 vsize=1732 CPUtime=0.05
/proc/21721/stat : 21721 (oree) R 21719 21721 20721 0 -1 4194304 298 0 0 0 5 0 0 0 18 0 1 0 18581587 1773568 280 18446744073709551615 134512640 135812674 4294956704 18446744073709551615 135274709 0 0 4096 17474 0 0 0 17 1 0 0
/proc/21721/statm: 433 281 170 317 0 112 0
Current children cumulated CPU time (s) 0.05
Current children cumulated vsize (KiB) 1732

[startup+0.101273 s]
/proc/loadavg: 0.91 0.95 0.90 3/64 21721
/proc/meminfo: memFree=1683496/2055920 swapFree=4184556/4192956
[pid=21721] ppid=21719 vsize=1864 CPUtime=0.09
/proc/21721/stat : 21721 (oree) R 21719 21721 20721 0 -1 4194304 317 0 0 0 9 0 0 0 18 0 1 0 18581587 1908736 299 18446744073709551615 134512640 135812674 4294956704 18446744073709551615 134602694 0 0 4096 17474 0 0 0 17 1 0 0
/proc/21721/statm: 466 299 170 317 0 145 0
Current children cumulated CPU time (s) 0.09
Current children cumulated vsize (KiB) 1864

[startup+0.301296 s]
/proc/loadavg: 0.91 0.95 0.90 3/64 21721
/proc/meminfo: memFree=1683496/2055920 swapFree=4184556/4192956
[pid=21721] ppid=21719 vsize=1996 CPUtime=0.29
/proc/21721/stat : 21721 (oree) R 21719 21721 20721 0 -1 4194304 348 0 0 0 29 0 0 0 19 0 1 0 18581587 2043904 330 18446744073709551615 134512640 135812674 4294956704 18446744073709551615 134554602 0 0 4096 17474 0 0 0 17 1 0 0
/proc/21721/statm: 499 330 170 317 0 178 0
Current children cumulated CPU time (s) 0.29
Current children cumulated vsize (KiB) 1996

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

Child status: 0
Real time (s): 0.365549
CPU time (s): 0.364944
CPU user time (s): 0.360945
CPU system time (s): 0.003999
CPU usage (%): 99.8345
Max. virtual memory (cumulated for all children) (KiB): 1996

getrusage(RUSAGE_CHILDREN,...) data:
user time used= 0.360945
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= 371
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 node62 on Thu Apr 19 16:27:36 UTC 2007

IDJOB= 366670
IDBENCH= 2877
IDSOLVER= 172
FILE ID= node62/366670-1177000056

PBS_JOBID= 4630437

Free space on /tmp= 66497 MiB

SOLVER NAME= oree 0.1.2 alpha
BENCH NAME= HOME/pub/bench/PB06/final/normalized-PB06/OPT-SMALLINT/submitted-PB06/manquiho/logic_synthesis/normalized-m50_100_90_90.r.opb
COMMAND LINE= oree /tmp/evaluation/366670-1177000056/instance-366670-1177000056.opb mod           
RUNSOLVER COMMAND LINE= runsolver  --timestamp  -w ROOT/results/node62/watcher-366670-1177000056 -o ROOT/results/node62/solver-366670-1177000056 -C 1800 -W 3600 -M 1800 --output-limit 1,15  oree /tmp/evaluation/366670-1177000056/instance-366670-1177000056.opb mod           

META MD5SUM SOLVER= 4e41df0f0543e325f03c5155f85b9e9b
MD5SUM BENCH=  4da887ca4bb57adc53b30ca1ea0acd93

RANDOM SEED= 830285739

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:       1683968 kB
Buffers:          7428 kB
Cached:         294316 kB
SwapCached:       2148 kB
Active:          28376 kB
Inactive:       283496 kB
HighTotal:           0 kB
HighFree:            0 kB
LowTotal:      2055920 kB
LowFree:       1683968 kB
SwapTotal:     4192956 kB
SwapFree:      4184556 kB
Dirty:            1336 kB
Writeback:           0 kB
Mapped:          16652 kB
Slab:            46080 kB
Committed_AS:   173604 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= 66497 MiB

End job on node62 on Thu Apr 19 16:27:36 UTC 2007