Trace number 2681468

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.1 fixedOPT3 0.272957 0.272688

General information on the benchmark

Namenormalized-PB07/OPT-SMALLINT-NLC/submittedPB07/roussel/
factor-mod-B/factor-mod-size=9-P0=263-P1=269-B.opb
MD5SUMb613dc01eaf727bc9d40c6e07a29423b
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.076987
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 variables27
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 constraint9
Maximum length of a constraint90
Number of terms in the objective function 9
Biggest coefficient in the objective function 256
Number of bits for the biggest coefficient in the objective function 9
Sum of the numbers in the objective function 511
Number of bits of the sum of numbers in the objective function 9
Biggest number in a constraint 131072
Number of bits of the biggest number in a constraint 18
Biggest sum of numbers in a constraint 522844
Number of bits of the biggest sum of numbers19
Number of products (including duplicates)81
Sum of products size (including duplicates)162
Number of different products81
Sum of products size162

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.1 http://www.residual.se/pbct
0.00/0.00	c Based on OpenSMT/CT 20091015
0.00/0.00	c constraints 84/0 clauses 81/0 units 0
0.00/0.00	c vars 27
0.00/0.00	c objective 9 + 0
0.19/0.22	c 0.202969 5.55469 609 4506
0.19/0.22	o 7
0.19/0.25	c 0.235964 5.70312 427 5346
0.19/0.25	o 3
0.19/0.26	c 0.245962 5.70312 546 5685
0.19/0.26	s OPTIMUM FOUND
0.19/0.26	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

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-2681468-1277498569/watcher-2681468-1277498569 -o /tmp/evaluation-result-2681468-1277498569/solver-2681468-1277498569 -C 1800 -W 2000 -M 1800 HOME/pbct --model HOME/instance-2681468-1277498569.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.92 0.99 0.99 3/106 31435
/proc/meminfo: memFree=1813876/2059040 swapFree=4140112/4192956
[pid=31435] ppid=31433 vsize=3444 CPUtime=0
/proc/31435/stat : 31435 (pbct) R 31433 31435 30988 0 -1 4202496 576 0 0 0 0 0 0 0 24 0 1 0 91151340 3526656 496 1992294400 134512640 136421960 4292690960 18446744073709551615 135811817 0 0 4096 16387 0 0 0 17 1 0 0 0
/proc/31435/statm: 861 498 193 467 0 392 0

[startup+0.0371181 s]
/proc/loadavg: 0.92 0.99 0.99 3/106 31435
/proc/meminfo: memFree=1813876/2059040 swapFree=4140112/4192956
[pid=31435] ppid=31433 vsize=5424 CPUtime=0.03
/proc/31435/stat : 31435 (pbct) R 31433 31435 30988 0 -1 4202496 1067 0 0 0 3 0 0 0 24 0 1 0 91151340 5554176 987 1992294400 134512640 136421960 4292690960 18446744073709551615 135874657 0 0 4096 16387 0 0 0 17 1 0 0 0
/proc/31435/statm: 1356 987 214 467 0 887 0
Current children cumulated CPU time (s) 0.03
Current children cumulated vsize (KiB) 5424

[startup+0.101123 s]
/proc/loadavg: 0.92 0.99 0.99 3/106 31435
/proc/meminfo: memFree=1813876/2059040 swapFree=4140112/4192956
[pid=31435] ppid=31433 vsize=5556 CPUtime=0.1
/proc/31435/stat : 31435 (pbct) R 31433 31435 30988 0 -1 4202496 1113 0 0 0 9 1 0 0 24 0 1 0 91151340 5689344 1033 1992294400 134512640 136421960 4292690960 18446744073709551615 135874657 0 0 4096 16387 0 0 0 17 1 0 0 0
/proc/31435/statm: 1389 1033 214 467 0 920 0
Current children cumulated CPU time (s) 0.1
Current children cumulated vsize (KiB) 5556

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

[startup+0.201132 s]
/proc/loadavg: 0.92 0.99 0.99 3/106 31435
/proc/meminfo: memFree=1813876/2059040 swapFree=4140112/4192956
[pid=31435] ppid=31433 vsize=5684 CPUtime=0.19
/proc/31435/stat : 31435 (pbct) R 31433 31435 30988 0 -1 4202496 1126 0 0 0 18 1 0 0 24 0 1 0 91151340 5820416 1046 1992294400 134512640 136421960 4292690960 18446744073709551615 135874657 0 0 4096 16387 0 0 0 17 1 0 0 0
/proc/31435/statm: 1421 1046 214 467 0 952 0
Current children cumulated CPU time (s) 0.19
Current children cumulated vsize (KiB) 5684

Child status: 0
Real time (s): 0.272688
CPU time (s): 0.272957
CPU user time (s): 0.250961
CPU system time (s): 0.021996
CPU usage (%): 100.099
Max. virtual memory (cumulated for all children) (KiB): 5684

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

runsolver used 0.003999 second user time and 0.007998 second system time

The end

Launcher Data 

Begin job on node031 at 2010-06-25 22:42:49
IDJOB=2681468
IDBENCH=47957
IDSOLVER=1192
FILE ID=node031/2681468-1277498569
PBS_JOBID= 11190580
Free space on /tmp= 62420 MiB

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

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

MD5SUM BENCH= b613dc01eaf727bc9d40c6e07a29423b
RANDOM SEED=1722463631

node031.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.219
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.43
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.219
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.53
clflush size	: 64
cache_alignment	: 128
address sizes	: 36 bits physical, 48 bits virtual
power management:


/proc/meminfo:
MemTotal:      2059040 kB
MemFree:       1814404 kB
Buffers:         53180 kB
Cached:          85748 kB
SwapCached:       5356 kB
Active:          57148 kB
Inactive:        94788 kB
HighTotal:           0 kB
HighFree:            0 kB
LowTotal:      2059040 kB
LowFree:       1814404 kB
SwapTotal:     4192956 kB
SwapFree:      4140112 kB
Dirty:            1880 kB
Writeback:           0 kB
AnonPages:       11588 kB
Mapped:          11976 kB
Slab:            70492 kB
PageTables:       4180 kB
NFS_Unstable:        0 kB
Bounce:              0 kB
CommitLimit:   5222476 kB
Committed_AS:   181452 kB
VmallocTotal: 34359738367 kB
VmallocUsed:    264964 kB
VmallocChunk: 34359471699 kB
HugePages_Total:     0
HugePages_Free:      0
HugePages_Rsvd:      0
Hugepagesize:     2048 kB

Free space on /tmp at the end= 62420 MiB
End job on node031 at 2010-06-25 22:42:49