Trace number 2667858

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.1OPT3 0.133979 0.133423

General information on the benchmark

Namenormalized-PB07/OPT-SMALLINT-NLC/submittedPB07/roussel/
factor-mod-B/factor-mod-size=7-P0=37-P1=43-B.opb
MD5SUM2fc96c84e9a32377eb9e70bf4047222f
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.038993
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 variables21
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 constraint7
Maximum length of a constraint56
Number of terms in the objective function 7
Biggest coefficient in the objective function 64
Number of bits for the biggest coefficient in the objective function 7
Sum of the numbers in the objective function 127
Number of bits of the sum of numbers in the objective function 7
Biggest number in a constraint 8192
Number of bits of the biggest number in a constraint 14
Biggest sum of numbers in a constraint 32440
Number of bits of the biggest sum of numbers15
Number of products (including duplicates)49
Sum of products size (including duplicates)98
Number of different products49
Sum of products size98

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 50/0 clauses 51/0 units 0
0.00/0.00	c vars 21
0.00/0.00	c objective 7 + 0
0.02/0.03	c 0.028995 4.35156 168 496
0.02/0.03	o 83
0.09/0.11	c 0.091986 4.48047 299 2374
0.09/0.11	o 11
0.09/0.12	c 0.102984 4.48047 259 2637
0.09/0.12	o 5
0.09/0.13	c 0.106983 4.48047 239 2766
0.09/0.13	o 3
0.09/0.13	c 0.107983 4.48047 239 2766
0.09/0.13	s OPTIMUM FOUND
0.09/0.13	v x1 x2 -x3 -x4 -x5 -x6 -x7 x8 -x9 x10 x11 x12 x13 -x14 x15 -x16 -x17 -x18 -x19 -x20 -x21

Verifier Data 

OK	3

Watcher Data 

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

command line: BIN/runsolver --timestamp -w /tmp/evaluation-result-2667858-1276647432/watcher-2667858-1276647432 -o /tmp/evaluation-result-2667858-1276647432/solver-2667858-1276647432 -C 1800 -W 2000 -M 1800 HOME/pbct --model HOME/instance-2667858-1276647432.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: 0.93 1.10 1.07 3/106 7940
/proc/meminfo: memFree=1836188/2059040 swapFree=4140132/4192956
[pid=7940] ppid=7938 vsize=3512 CPUtime=0
/proc/7940/stat : 7940 (pbct) R 7938 7940 6618 0 -1 4202496 571 0 0 0 0 0 0 0 20 0 1 0 40346642 3596288 494 1992294400 134512640 136485738 4289372064 18446744073709551615 135850441 0 0 4096 16387 0 0 0 17 1 0 0 0
/proc/7940/statm: 878 495 198 482 0 394 0

[startup+0.0344939 s]
/proc/loadavg: 0.93 1.10 1.07 3/106 7940
/proc/meminfo: memFree=1836188/2059040 swapFree=4140132/4192956
[pid=7940] ppid=7938 vsize=4452 CPUtime=0.02
/proc/7940/stat : 7940 (pbct) R 7938 7940 6618 0 -1 4202496 838 0 0 0 2 0 0 0 20 0 1 0 40346642 4558848 761 1992294400 134512640 136485738 4289372064 18446744073709551615 135913329 0 0 4096 16387 0 0 0 17 1 0 0 0
/proc/7940/statm: 1113 761 226 482 0 629 0
Current children cumulated CPU time (s) 0.02
Current children cumulated vsize (KiB) 4452

[startup+0.100506 s]
/proc/loadavg: 0.93 1.10 1.07 3/106 7940
/proc/meminfo: memFree=1836188/2059040 swapFree=4140132/4192956
[pid=7940] ppid=7938 vsize=4584 CPUtime=0.09
/proc/7940/stat : 7940 (pbct) R 7938 7940 6618 0 -1 4202496 873 0 0 0 7 2 0 0 20 0 1 0 40346642 4694016 795 1992294400 134512640 136485738 4289372064 18446744073709551615 135913329 0 0 4096 16387 0 0 0 17 1 0 0 0
/proc/7940/statm: 1146 795 244 482 0 662 0
Current children cumulated CPU time (s) 0.09
Current children cumulated vsize (KiB) 4584

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

Child status: 0
Real time (s): 0.133423
CPU time (s): 0.133979
CPU user time (s): 0.109983
CPU system time (s): 0.023996
CPU usage (%): 100.417
Max. virtual memory (cumulated for all children) (KiB): 4584

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

runsolver used 0.004999 second user time and 0.006998 second system time

The end

Launcher Data 

Begin job on node007 at 2010-06-16 02:17:12
IDJOB=2667858
IDBENCH=47941
IDSOLVER=1170
FILE ID=node007/2667858-1276647432
PBS_JOBID= 11172398
Free space on /tmp= 62488 MiB

SOLVER NAME= PB/CT 0.1
BENCH NAME= PB07/normalized-PB07/OPT-SMALLINT-NLC/submittedPB07/roussel/factor-mod-B/factor-mod-size=7-P0=37-P1=43-B.opb
COMMAND LINE= HOME/pbct --model BENCHNAME
RUNSOLVER COMMAND LINE= BIN/runsolver --timestamp -w /tmp/evaluation-result-2667858-1276647432/watcher-2667858-1276647432 -o /tmp/evaluation-result-2667858-1276647432/solver-2667858-1276647432 -C 1800 -W 2000 -M 1800  HOME/pbct --model HOME/instance-2667858-1276647432.opb

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

MD5SUM BENCH= 2fc96c84e9a32377eb9e70bf4047222f
RANDOM SEED=279798177

node007.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.264
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.52
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.264
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.44
clflush size	: 64
cache_alignment	: 128
address sizes	: 36 bits physical, 48 bits virtual
power management:


/proc/meminfo:
MemTotal:      2059040 kB
MemFree:       1836716 kB
Buffers:         31372 kB
Cached:         102612 kB
SwapCached:       6752 kB
Active:         102652 kB
Inactive:        45192 kB
HighTotal:           0 kB
HighFree:            0 kB
LowTotal:      2059040 kB
LowFree:       1836716 kB
SwapTotal:     4192956 kB
SwapFree:      4140132 kB
Dirty:            1988 kB
Writeback:           0 kB
AnonPages:       12000 kB
Mapped:          12956 kB
Slab:            52776 kB
PageTables:       4028 kB
NFS_Unstable:        0 kB
Bounce:              0 kB
CommitLimit:   5222476 kB
Committed_AS:   181604 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= 62484 MiB
End job on node007 at 2010-06-16 02:17:12