Trace number 2669501

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.1OPT46877 0.027995 0.0281879

General information on the benchmark

Name/OPT-BIGINT-LIN/aries-da_nrp/
normalized-aries-da_network_20_2__17_12.opb
MD5SUMea761b6b937db07d13aa1ca1725d4f7c
Bench CategoryOPT-BIGINT-LIN (optimisation, big integers, linear constraints)
Best result obtained on this benchmarkOPT
Best value of the objective obtained on this benchmark46877
Best CPU time to get the best result obtained on this benchmark0.025995
Has Objective FunctionYES
Satisfiable
(Un)Satisfiability was proved
Best value of the objective function
Optimality of the best value was proved
Number of variables58
Total number of constraints20
Number of constraints which are clauses0
Number of constraints which are cardinality constraints (but not clauses)2
Number of constraints which are nor clauses,nor cardinality constraints18
Minimum length of a constraint2
Maximum length of a constraint9
Number of terms in the objective function 40
Biggest coefficient in the objective function 94409
Number of bits for the biggest coefficient in the objective function 17
Sum of the numbers in the objective function 1744562
Number of bits of the sum of numbers in the objective function 21
Biggest number in a constraint 94409
Number of bits of the biggest number in a constraint 17
Biggest sum of numbers in a constraint 1744562
Number of bits of the biggest sum of numbers21
Number of products (including duplicates)0
Sum of products size (including duplicates)0
Number of different products0
Sum of products size0

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 20/0 clauses 0/0 units 0
0.00/0.00	c vars 58
0.00/0.00	c objective 40 + 0
0.00/0.01	c 0.011998 3.82422 33 341
0.00/0.01	o 585188
0.00/0.01	c 0.011998 3.82422 48 403
0.00/0.01	o 566029
0.00/0.01	c 0.012998 3.82422 64 531
0.00/0.01	o 453400
0.00/0.01	c 0.013997 3.82422 68 574
0.00/0.01	o 427360
0.00/0.01	c 0.014997 3.82422 74 622
0.00/0.01	o 410169
0.00/0.01	c 0.014997 3.82422 76 652
0.00/0.01	o 371238
0.00/0.02	c 0.016997 3.82422 118 775
0.00/0.02	o 369090
0.00/0.02	c 0.018997 3.82422 134 858
0.00/0.02	o 338219
0.00/0.02	c 0.018997 3.82422 135 890
0.00/0.02	o 227463
0.00/0.02	c 0.019996 3.82422 135 919
0.00/0.02	o 196245
0.00/0.02	c 0.019996 3.82422 140 956
0.00/0.02	o 78095
0.00/0.02	c 0.020996 3.82422 148 990
0.00/0.02	o 46877
0.00/0.02	c 0.021996 3.82422 148 990
0.00/0.02	s OPTIMUM FOUND
0.00/0.02	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

Verifier Data 

OK	46877

Watcher Data 

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

command line: BIN/runsolver --timestamp -w /tmp/evaluation-result-2669501-1276690795/watcher-2669501-1276690795 -o /tmp/evaluation-result-2669501-1276690795/solver-2669501-1276690795 -C 1800 -W 2000 -M 1800 HOME/pbct --model HOME/instance-2669501-1276690795.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.87 1.94 1.59 3/106 16396
/proc/meminfo: memFree=1779632/2059040 swapFree=4168596/4192956
[pid=16396] ppid=16394 vsize=3516 CPUtime=0
/proc/16396/stat : 16396 (pbct) R 16394 16396 15910 0 -1 4202496 560 0 0 0 0 0 0 0 25 0 1 0 10370438 3600384 482 1992294400 134512640 136485738 4289728528 18446744073709551615 135850441 0 0 4096 16387 0 0 0 17 1 0 0 0
/proc/16396/statm: 879 484 195 482 0 395 0

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

Child status: 0
Real time (s): 0.0281879
CPU time (s): 0.027995
CPU user time (s): 0.022996
CPU system time (s): 0.004999
CPU usage (%): 99.3155
Max. virtual memory (cumulated for all children) (KiB): 0

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

runsolver used 0.004999 second user time and 0.007998 second system time

The end

Launcher Data 

Begin job on node055 at 2010-06-16 14:19:55
IDJOB=2669501
IDBENCH=71869
IDSOLVER=1170
FILE ID=node055/2669501-1276690795
PBS_JOBID= 11172597
Free space on /tmp= 62480 MiB

SOLVER NAME= PB/CT 0.1
BENCH NAME= PB09/normalized-PB09/OPT-BIGINT-LIN/aries-da_nrp/normalized-aries-da_network_20_2__17_12.opb
COMMAND LINE= HOME/pbct --model BENCHNAME
RUNSOLVER COMMAND LINE= BIN/runsolver --timestamp -w /tmp/evaluation-result-2669501-1276690795/watcher-2669501-1276690795 -o /tmp/evaluation-result-2669501-1276690795/solver-2669501-1276690795 -C 1800 -W 2000 -M 1800  HOME/pbct --model HOME/instance-2669501-1276690795.opb

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

MD5SUM BENCH= ea761b6b937db07d13aa1ca1725d4f7c
RANDOM SEED=1456302980

node055.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.258
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.51
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.258
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:       1780152 kB
Buffers:         65684 kB
Cached:         110576 kB
SwapCached:       1504 kB
Active:          93936 kB
Inactive:       119040 kB
HighTotal:           0 kB
HighFree:            0 kB
LowTotal:      2059040 kB
LowFree:       1780152 kB
SwapTotal:     4192956 kB
SwapFree:      4168596 kB
Dirty:            2088 kB
Writeback:           0 kB
AnonPages:       35160 kB
Mapped:          15080 kB
Slab:            44204 kB
PageTables:       4008 kB
NFS_Unstable:        0 kB
Bounce:              0 kB
CommitLimit:   5222476 kB
Committed_AS:   181416 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= 62476 MiB
End job on node055 at 2010-06-16 14:19:55