Trace number 429646

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
PBS4 2007-03-23OPT3 0.067988 0.067984

General information on the benchmark

Namenormalized-PB07/OPT-SMALLINT-NLC/submittedPB07/roussel/
factor-mod-B/factor-mod-size=8-P0=157-P1=47-B.opb
MD5SUM65e30a452de5692ad7673801cf6b385e
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.023995
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 variables24
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 constraint8
Maximum length of a constraint72
Number of terms in the objective function 8
Biggest coefficient in the objective function 128
Number of bits for the biggest coefficient in the objective function 8
Sum of the numbers in the objective function 255
Number of bits of the sum of numbers in the objective function 8
Biggest number in a constraint 32768
Number of bits of the biggest number in a constraint 16
Biggest sum of numbers in a constraint 130516
Number of bits of the biggest sum of numbers17
Number of products (including duplicates)64
Sum of products size (including duplicates)128
Number of different products64
Sum of products size128

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 PBS v4 by Bashar Al-Rawi & Fadi Aloul
0.00/0.00	c Solving /tmp/evaluation/429646-1177987102/instance-429646-1177987102.opb ......
0.00/0.00	c done parsing opb.
0.00/0.00	o 45
0.04/0.04	o 31
0.04/0.05	o 29
0.04/0.06	o 11
0.04/0.06	o 9
0.04/0.06	o 5
0.04/0.06	o 3
0.04/0.06	o 3
0.04/0.06	s OPTIMUM FOUND
0.04/0.06	c Total Run Time					0.063991
0.04/0.06	v x1 -x10 -x11 -x12 x13 x14 x15 x16 -x17 x18 -x19 x2 -x20 -x21 -x22 -x23 -x24 x25 x26 -x27 -x28 -x29 -x3 -x30 -x31 -x32 -x33 -x34 -x35
0.04/0.06	v -x36 -x37 -x38 -x39 -x4 -x40 -x41 -x42 -x43 -x44 -x45 -x46 -x47 -x48 -x49 -x5 -x50 -x51 -x52 -x53 -x54 -x55 -x56 x57 x58 -x59 -x6
0.04/0.06	v -x60 -x61 -x62 -x63 -x64 x65 x66 -x67 -x68 -x69 -x7 -x70 -x71 -x72 x73 x74 -x75 -x76 -x77 -x78 -x79 -x8 -x80 x81 x82 -x83 -x84 -x85
0.04/0.06	v -x86 -x87 -x88 x9

Verifier Data (download as text)

OK	3

Conversion Script Data (download as text)

Linearizing /tmp/evaluation/429646-1177987102/instance-429646-1177987102.opb

Watcher Data (download as text)

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

command line: runsolver --timestamp -w ROOT/results/node7/watcher-429646-1177987102 -o ROOT/results/node7/solver-429646-1177987102 -C 1800 -W 3600 -M 1800 --output-limit 1,15 /tmp/evaluation/429646-1177987102/PBS4 /tmp/evaluation/429646-1177987102/instance-429646-1177987102.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.85 0.97 0.99 3/77 32103
/proc/meminfo: memFree=1758712/2055920 swapFree=4157088/4192956
[pid=32103] ppid=32101 vsize=1320 CPUtime=0
/proc/32103/stat : 32103 (PBS4) R 32101 32103 29441 0 -1 4194304 150 0 0 0 0 0 0 0 18 0 1 0 274747840 1351680 133 18446744073709551615 134512640 135410514 4294956672 18446744073709551615 135059249 0 0 4096 16384 0 0 0 17 1 0 0
/proc/32103/statm: 330 133 102 219 0 107 0

[startup+0.046255 s]
/proc/loadavg: 0.85 0.97 0.99 3/77 32103
/proc/meminfo: memFree=1758712/2055920 swapFree=4157088/4192956
[pid=32103] ppid=32101 vsize=1576 CPUtime=0.04
/proc/32103/stat : 32103 (PBS4) R 32101 32103 29441 0 -1 4194304 246 0 0 0 4 0 0 0 18 0 1 0 274747840 1613824 229 18446744073709551615 134512640 135410514 4294956672 18446744073709551615 135059249 0 0 4096 16384 0 0 0 17 1 0 0
/proc/32103/statm: 394 229 103 219 0 171 0
Current children cumulated CPU time (s) 0.04
Current children cumulated vsize (KiB) 1576

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

[startup+0.046255 s]
/proc/loadavg: 0.85 0.97 0.99 3/77 32103
/proc/meminfo: memFree=1758712/2055920 swapFree=4157088/4192956
[pid=32103] ppid=32101 vsize=1576 CPUtime=0.04
/proc/32103/stat : 32103 (PBS4) R 32101 32103 29441 0 -1 4194304 246 0 0 0 4 0 0 0 18 0 1 0 274747840 1613824 229 18446744073709551615 134512640 135410514 4294956672 18446744073709551615 135059249 0 0 4096 16384 0 0 0 17 1 0 0
/proc/32103/statm: 394 229 103 219 0 171 0
Current children cumulated CPU time (s) 0.04
Current children cumulated vsize (KiB) 1576

Child status: 0
Real time (s): 0.067984
CPU time (s): 0.067988
CPU user time (s): 0.065989
CPU system time (s): 0.001999
CPU usage (%): 100.006
Max. virtual memory (cumulated for all children) (KiB): 1576

getrusage(RUSAGE_CHILDREN,...) data:
user time used= 0.065989
system time used= 0.001999
maximum resident set size= 0
integral shared memory size= 0
integral unshared data size= 0
integral unshared stack size= 0
page reclaims= 295
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= 0

runsolver used 0.000999 second user time and 0.007998 second system time

The end

Launcher Data (download as text)

Begin job on node7 on Tue May  1 02:38:22 UTC 2007

IDJOB= 429646
IDBENCH= 47924
IDSOLVER= 157
FILE ID= node7/429646-1177987102

PBS_JOBID= 4728030

Free space on /tmp= 66563 MiB

SOLVER NAME= PBS4 2007-03-23
BENCH NAME= HOME/pub/bench/PB07/normalized-PB07/OPT-SMALLINT-NLC/submittedPB07/roussel/factor-mod-B/factor-mod-size=8-P0=157-P1=47-B.opb
COMMAND LINE= /tmp/evaluation/429646-1177987102/PBS4 /tmp/evaluation/429646-1177987102/instance-429646-1177987102.opb            
CONVERSION COMMAND LINE= runsolver -w ROOT/results/node7/convwatcher-429646-1177987102 -o ROOT/results/node7/conversion-429646-1177987102 -C 600 -M 1800 PBconversionToLinear /tmp/evaluation/429646-1177987102/instance-429646-1177987102.opb
CONVERSION RUNSOLVER STATUS CODE= 0
CONVERSION STATUS CODE= 0

RUNSOLVER COMMAND LINE= runsolver  --timestamp  -w ROOT/results/node7/watcher-429646-1177987102 -o ROOT/results/node7/solver-429646-1177987102 -C 1800 -W 3600 -M 1800 --output-limit 1,15  /tmp/evaluation/429646-1177987102/PBS4 /tmp/evaluation/429646-1177987102/instance-429646-1177987102.opb            

META MD5SUM SOLVER= b6c24e28fef9e1efa7891be58ea9e46f
MD5SUM BENCH=  65e30a452de5692ad7673801cf6b385e

RANDOM SEED= 938499531

TIME LIMIT= 1800 seconds
MEMORY LIMIT= 1800 MiB

Linux node7.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.231
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.231
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:       1759184 kB
Buffers:         42328 kB
Cached:         165364 kB
SwapCached:      15824 kB
Active:          76580 kB
Inactive:       154972 kB
HighTotal:           0 kB
HighFree:            0 kB
LowTotal:      2055920 kB
LowFree:       1759184 kB
SwapTotal:     4192956 kB
SwapFree:      4157088 kB
Dirty:            1328 kB
Writeback:           0 kB
Mapped:          30812 kB
Slab:            50664 kB
Committed_AS:  9014596 kB
PageTables:       1860 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 node7 on Tue May  1 02:38:22 UTC 2007