Trace number 2696347

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 NameAnswerCPU timeWall clock time
pb_cplex 2010-06-29SAT 0.041993 0.0435999

General information on the benchmark

Namenormalized-PB06/SATUNSAT-SMALLINT/submitted-PB05/aloul/
FPGA_SAT05/normalized-fpga11_10_sat_pb.cnf.cr.opb
MD5SUMad8c96101fa1b2a172901cb81285d15c
Bench CategoryDEC-SMALLINT (no optimisation, small integers)
Best result obtained on this benchmarkSAT
Best value of the objective obtained on this benchmark0
Best CPU time to get the best result obtained on this benchmark0.002998
Has Objective FunctionNO
SatisfiableYES
(Un)Satisfiability was provedYES
Best value of the objective function
Optimality of the best value was proved NO
Number of variables165
Total number of constraints141
Number of constraints which are clauses120
Number of constraints which are cardinality constraints (but not clauses)21
Number of constraints which are nor clauses,nor cardinality constraints0
Minimum length of a constraint5
Maximum length of a constraint11
Number of terms in the objective function 0
Biggest coefficient in the objective function 0
Number of bits for the biggest coefficient in the objective function 0
Sum of the numbers in the objective function 0
Number of bits of the sum of numbers in the objective function 0
Biggest number in a constraint 1
Number of bits of the biggest number in a constraint 1
Biggest sum of numbers in a constraint 12
Number of bits of the biggest sum of numbers4
Number of products (including duplicates)0
Sum of products size (including duplicates)0
Number of different products0
Sum of products size0

Solver Data 

0.00/0.00	c pb_cplex 1.0 - 20100701
0.00/0.00	c Parsing opb file format. File HOME/instance-2696347-1278016135.opb.
0.00/0.00	c Instance file HOME/instance-2696347-1278016135.opb
0.00/0.00	c File size is 8365 bytes.
0.00/0.00	c Highest Coefficient sum: 12
0.00/0.00	c  IBM ILOG License Manager: "IBM ILOG Optimization Suite for Academic Initiative" is accessing CPLEX 12 with option(s): "e m b q ".
0.00/0.01	c ============================[ Problem Statistics ]=============================
0.00/0.01	c |                                                                             |
0.00/0.01	c |  Parsing time:          0.01         s                                      |
0.00/0.01	c |  Number Variables:      165                                                 |
0.00/0.01	c |  Number Constraints:    141                                                 |
0.00/0.01	c ===============================================================================
0.00/0.04	c Remaining time 1799.99 sec.
0.00/0.04	s SATISFIABLE
0.00/0.04	c Solution value = 0.00
0.00/0.04	v x108 -x151 -x152 x153 -x154 -x155 x27 -x131 -x132 x133 -x134 -x135 -x75 -x72 -x136 x137 -x138 -x139 -x140 -x1 -x2 -x3 -x4 -x5 x6 -x7 -x8 -x9 -x10 -x11 -x69 -x121 -x122 -x123 x124 -x125 x66 -x161 -x162 -x163 x164 -x165 -x18 -x141 -x142 -x143 -x144 -x145 -x58 x78 -x79 -x80 -x81 -x82 -x83 -x84 -x85 -x86 -x87 -x88 -x59 -x126 -x127 -x128 -x129 x130 -x40 -x51 -x15 x14 -x19 -x146 -x147 -x148 -x149 x150 x70 -x50 -x62 -x63 -x23 -x111 x112 -x113 -x114 -x115 -x102 -x95 -x101 x116 -x117 -x118 -x119 -x120 -x46 -x71 -x76 x156 -x157 -x158 -x159 -x160 -x74 -x34 -x105 -x67 -x68 -x73 -x77 -x21 -x24 -x89 -x45 -x91 -x41 -x104 -x25 x90 -x92 -x93 -x94 -x96 -x97 -x98 -x99 -x35 -x28 -x26 -x29 -x30 -x31 -x32 -x33 -x107 -x17 -x61 x52 -x38 -x109 -x13 -x103 -x49 -x22 -x110 -x100 -x106 -x53 -x65 -x42 -x12 -x16 -x20 x43 -x57 -x39 -x56 -x60 -x64 -x44 -x48 -x54 -x47 -x55 -x37 -x36
0.00/0.04	c Total CPU time              : 0.034994 s

Verifier Data 

OK	0

Watcher Data 

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

command line: BIN/runsolver --timestamp -w /tmp/evaluation-result-2696347-1278016135/watcher-2696347-1278016135 -o /tmp/evaluation-result-2696347-1278016135/solver-2696347-1278016135 -C 1800 -W 2000 -M 1800 run HOME/instance-2696347-1278016135.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.97 1.91 1.27 3/106 2237
/proc/meminfo: memFree=1402752/2059040 swapFree=4135680/4192956
[pid=2237] ppid=2235 vsize=8700 CPUtime=0
/proc/2237/stat : 2237 (run) S 2235 2237 1862 0 -1 4202496 364 0 0 0 0 0 0 0 18 0 1 0 177217523 8908800 248 1992294400 4194304 4922060 140737433055248 18446744073709551615 248552987781 0 65536 4100 65538 18446744071562232103 0 0 17 1 0 0 0
/proc/2237/statm: 2175 248 208 178 0 68 0

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

Child status: 0
Real time (s): 0.0435999
CPU time (s): 0.041993
CPU user time (s): 0.035994
CPU system time (s): 0.005999
CPU usage (%): 96.3144
Max. virtual memory (cumulated for all children) (KiB): 0

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

runsolver used 0.003999 second user time and 0.007998 second system time

The end

Launcher Data 

Begin job on node001 at 2010-07-01 22:28:55
IDJOB=2696347
IDBENCH=1441
IDSOLVER=1209
FILE ID=node001/2696347-1278016135
PBS_JOBID= 11198753
Free space on /tmp= 62328 MiB

SOLVER NAME= pb_cplex 2010-06-29
BENCH NAME= PB06//final/normalized-PB06/SATUNSAT-SMALLINT/submitted-PB05/aloul/FPGA_SAT05/normalized-fpga11_10_sat_pb.cnf.cr.opb
COMMAND LINE= run BENCHNAME
RUNSOLVER COMMAND LINE= BIN/runsolver --timestamp -w /tmp/evaluation-result-2696347-1278016135/watcher-2696347-1278016135 -o /tmp/evaluation-result-2696347-1278016135/solver-2696347-1278016135 -C 1800 -W 2000 -M 1800  run HOME/instance-2696347-1278016135.opb

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

MD5SUM BENCH= ad8c96101fa1b2a172901cb81285d15c
RANDOM SEED=528239405

node001.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.202
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.40
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.202
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.46
clflush size	: 64
cache_alignment	: 128
address sizes	: 36 bits physical, 48 bits virtual
power management:


/proc/meminfo:
MemTotal:      2059040 kB
MemFree:       1403280 kB
Buffers:        151412 kB
Cached:         391368 kB
SwapCached:      10036 kB
Active:         237780 kB
Inactive:       318432 kB
HighTotal:           0 kB
HighFree:            0 kB
LowTotal:      2059040 kB
LowFree:       1403280 kB
SwapTotal:     4192956 kB
SwapFree:      4135680 kB
Dirty:           16964 kB
Writeback:           0 kB
AnonPages:       11812 kB
Mapped:           8340 kB
Slab:            77584 kB
PageTables:       4168 kB
NFS_Unstable:        0 kB
Bounce:              0 kB
CommitLimit:   5222476 kB
Committed_AS:   182868 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= 62312 MiB
End job on node001 at 2010-07-01 22:28:55