Trace number 2667987

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. The first timestamp (if present) is estimated CPU time. The last timestamp is wall clock 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
PB/CT 0.1OPT2 0.294954 0.294923

General information on the benchmark

Namenormalized-PB07/OPT-SMALLINT-NLC/submittedPB07/roussel/
factor-mod-B/factor-mod-size=5-P0=29-P1=17-P2=2-P3=19-P4=13-B.opb
MD5SUMad91a3f1eebbb2431180c5d6e6033f2b
Bench CategoryOPT-SMALLINT-NLC (optimisation, small integers, non linear constraints)
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.011997
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 variables60
Total number of constraints9
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 constraints9
Minimum length of a constraint5
Maximum length of a constraint35
Number of terms in the objective function 5
Biggest coefficient in the objective function 16
Number of bits for the biggest coefficient in the objective function 5
Sum of the numbers in the objective function 31
Number of bits of the sum of numbers in the objective function 5
Biggest number in a constraint 512
Number of bits of the biggest number in a constraint 10
Biggest sum of numbers in a constraint 1984
Number of bits of the biggest sum of numbers11
Number of products (including duplicates)100
Sum of products size (including duplicates)200
Number of different products100
Sum of products size200

Quality of the solution as a function of time


Download the above graph as a PDF file / as an EPS file

Solver Data 

0.00/0.00	c PB/CT 0.1 http://www.residual.se/pbct
0.00/0.00	c Based on OpenSMT/CT 20091015
0.00/0.00	c constraints 104/0 clauses 105/0 units 0
0.00/0.00	c vars 60
0.00/0.00	c objective 5 + 0
0.09/0.12	c 0.109983 5.87891 573 3131
0.09/0.12	o 18
0.19/0.22	c 0.19597 6.00781 433 6371
0.19/0.22	o 5
0.19/0.23	c 0.199969 6.00781 488 6615
0.19/0.23	o 3
0.19/0.28	c 0.249962 6.00781 533 8268
0.19/0.28	o 2
0.19/0.28	c 0.249962 6.00781 267 8268
0.19/0.28	s OPTIMUM FOUND
0.19/0.28	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 -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 -x56 x57 -x58 -x59 x60

Verifier Data 

OK	2

Watcher Data 

runsolver version 3.2.9 (svn:492) (c) roussel@cril.univ-artois.fr

command line: BIN/runsolver --timestamp -w /tmp/evaluation-result-2667987-1276650409/watcher-2667987-1276650409 -o /tmp/evaluation-result-2667987-1276650409/solver-2667987-1276650409 -C 1800 -W 2000 -M 1800 HOME/pbct --model HOME/instance-2667987-1276650409.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): 2000 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
Current StackSize limit: 10240 KiB


[startup+0 s]
/proc/loadavg: 1.10 1.04 1.01 3/106 13320
/proc/meminfo: memFree=1619544/2059040 swapFree=4192956/4192956
[pid=13320] ppid=13318 vsize=3516 CPUtime=0
/proc/13320/stat : 13320 (pbct) R 13318 13320 12809 0 -1 4202496 564 0 0 0 0 0 0 0 20 0 1 0 6333857 3600384 487 1992294400 134512640 136485738 4292930016 18446744073709551615 134741957 0 0 4096 16387 0 0 0 17 1 0 0 0
/proc/13320/statm: 879 489 198 482 0 395 0

[startup+0.077774 s]
/proc/loadavg: 1.10 1.04 1.01 3/106 13320
/proc/meminfo: memFree=1619544/2059040 swapFree=4192956/4192956
[pid=13320] ppid=13318 vsize=6016 CPUtime=0.06
/proc/13320/stat : 13320 (pbct) R 13318 13320 12809 0 -1 4202496 1198 0 0 0 6 0 0 0 20 0 1 0 6333857 6160384 1121 1992294400 134512640 136485738 4292930016 18446744073709551615 135913329 0 0 4096 16387 0 0 0 17 1 0 0 0
/proc/13320/statm: 1504 1121 226 482 0 1020 0
Current children cumulated CPU time (s) 0.06
Current children cumulated vsize (KiB) 6016

[startup+0.101776 s]
/proc/loadavg: 1.10 1.04 1.01 3/106 13320
/proc/meminfo: memFree=1619544/2059040 swapFree=4192956/4192956
[pid=13320] ppid=13318 vsize=6016 CPUtime=0.09
/proc/13320/stat : 13320 (pbct) R 13318 13320 12809 0 -1 4202496 1207 0 0 0 8 1 0 0 20 0 1 0 6333857 6160384 1130 1992294400 134512640 136485738 4292930016 18446744073709551615 135913329 0 0 4096 16387 0 0 0 17 1 0 0 0
/proc/13320/statm: 1504 1130 226 482 0 1020 0
Current children cumulated CPU time (s) 0.09
Current children cumulated vsize (KiB) 6016

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

[startup+0.201786 s]
/proc/loadavg: 1.10 1.04 1.01 3/106 13320
/proc/meminfo: memFree=1619544/2059040 swapFree=4192956/4192956
[pid=13320] ppid=13318 vsize=6148 CPUtime=0.19
/proc/13320/stat : 13320 (pbct) R 13318 13320 12809 0 -1 4202496 1241 0 0 0 17 2 0 0 20 0 1 0 6333857 6295552 1163 1992294400 134512640 136485738 4292930016 18446744073709551615 135725429 0 0 4096 16387 0 0 0 17 1 0 0 0
/proc/13320/statm: 1537 1163 244 482 0 1053 0
Current children cumulated CPU time (s) 0.19
Current children cumulated vsize (KiB) 6148

Child status: 0
Real time (s): 0.294923
CPU time (s): 0.294954
CPU user time (s): 0.25696
CPU system time (s): 0.037994
CPU usage (%): 100.011
Max. virtual memory (cumulated for all children) (KiB): 6148

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

runsolver used 0.003999 second user time and 0.008998 second system time

The end

Launcher Data 

Begin job on node036 at 2010-06-16 03:06:50
IDJOB=2667987
IDBENCH=48070
IDSOLVER=1170
FILE ID=node036/2667987-1276650409
PBS_JOBID= 11172433
Free space on /tmp= 62524 MiB

SOLVER NAME= PB/CT 0.1
BENCH NAME= PB07/normalized-PB07/OPT-SMALLINT-NLC/submittedPB07/roussel/factor-mod-B/factor-mod-size=5-P0=29-P1=17-P2=2-P3=19-P4=13-B.opb
COMMAND LINE= HOME/pbct --model BENCHNAME
RUNSOLVER COMMAND LINE= BIN/runsolver --timestamp -w /tmp/evaluation-result-2667987-1276650409/watcher-2667987-1276650409 -o /tmp/evaluation-result-2667987-1276650409/solver-2667987-1276650409 -C 1800 -W 2000 -M 1800  HOME/pbct --model HOME/instance-2667987-1276650409.opb

TIME LIMIT= 1800 seconds
MEMORY LIMIT= 1800 MiB
MAX NB THREAD= 0

MD5SUM BENCH= ad91a3f1eebbb2431180c5d6e6033f2b
RANDOM SEED=1497418947

node036.alineos.net Linux 2.6.18-164.el5 #1 SMP Thu Sep 3 03:28:30 EDT 2009

/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.251
cache size	: 2048 KB
physical id	: 0
siblings	: 1
core id		: 0
cpu cores	: 1
apicid		: 0
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 constant_tsc pni monitor ds_cpl cid cx16 xtpr
bogomips	: 6000.50
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.251
cache size	: 2048 KB
physical id	: 3
siblings	: 1
core id		: 0
cpu cores	: 1
apicid		: 6
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 constant_tsc pni monitor ds_cpl cid cx16 xtpr
bogomips	: 5599.45
clflush size	: 64
cache_alignment	: 128
address sizes	: 36 bits physical, 48 bits virtual
power management:


/proc/meminfo:
MemTotal:      2059040 kB
MemFree:       1619940 kB
Buffers:         81312 kB
Cached:         217000 kB
SwapCached:          0 kB
Active:         150032 kB
Inactive:       207780 kB
HighTotal:           0 kB
HighFree:            0 kB
LowTotal:      2059040 kB
LowFree:       1619940 kB
SwapTotal:     4192956 kB
SwapFree:      4192956 kB
Dirty:            1960 kB
Writeback:           0 kB
AnonPages:       59388 kB
Mapped:          15412 kB
Slab:            59384 kB
PageTables:       4072 kB
NFS_Unstable:        0 kB
Bounce:              0 kB
CommitLimit:   5222476 kB
Committed_AS:   181056 kB
VmallocTotal: 34359738367 kB
VmallocUsed:    264948 kB
VmallocChunk: 34359471699 kB
HugePages_Total:     0
HugePages_Free:      0
HugePages_Rsvd:      0
Hugepagesize:     2048 kB

Free space on /tmp at the end= 62524 MiB
End job on node036 at 2010-06-16 03:06:50