Trace number 1523805

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
Hybrid2 2009-03-22SAT 0.323949 0.324357

General information on the benchmark

NameRANDOM/MEDIUM/3SAT/SATISFIABLE/420/
unif-k3-r4.25-v420-c1785-S1940784272-089.cnf
MD5SUMbd1e8bac20c24526524d34ea2c494a05
Bench CategoryRANDOM (random instances)
Best result obtained on this benchmarkSAT
Best CPU time to get the best result obtained on this benchmark0.015996
Satisfiable
(Un)Satisfiability was proved
Number of variables420
Number of clauses1785
Sum of the clauses size5355
Maximum clause length3
Minimum clause length3
Number of clauses of size 10
Number of clauses of size 20
Number of clauses of size 31785
Number of clauses of size 40
Number of clauses of size 50
Number of clauses of size over 50

Solver Data 

0.29/0.32	c try 1 flip j 291237
0.29/0.32	c A solution is found
0.29/0.32	s SATISFIABLE
0.29/0.32	v -1 -2 3 4 5 -6 -7 8 9 -10 -11 -12 13 -14 15 -16 17 -18 19 -20 -21 22 23 -24 -25 26 -27 -28 29 30 31 32 -33 34 -35 -36 37 -38 39 -40 -41 -42 43 -44 45 46 -47 -48 49 -50 -51 -52 -53 54 -55 -56 -57 -58 59 -60 -61 62 63 -64 -65 -66 67 68 69 70 -71 -72 73 74 75 76 77 78 79 80 81 82 83 -84 -85 -86 87 88 89 -90 -91 92 93 94 95 96 -97 98 -99 100 101 102 103 104 -105 106 -107 108 109 110 111 -112 -113 -114 -115 116 117 118 -119 120 -121 122 -123 -124 -125 126 127 -128 -129 -130 131 132 -133 134 135 -136 -137 -138 139 140 141 142 143 144 -145 -146 147 -148 149 -150 -151 152 153 -154 -155 156 -157 -158 -159 -160 -161 -162 163 164 165 -166 -167 168 -169 -170 171 172 -173 174 -175 176 -177 178 179 -180 -181 -182 183 184 185 186 187 -188 -189 -190 191 192 -193 -194 195 196 -197 -198 199 200 -201 202 -203 -204 205 -206 207 208 -209 -210 -211 212 -213 -214 -215 216 -217 -218 219 -220 -221 222 -223 -224 -225 -226 -227 228 229 -230 231 -232 233 234 235 236 237 -238 -239 -240 241 242 -243 244 245 246 -247 -248 -249 250 -251 252 -253 254 -255 -256 -257 -258 -259 260 -261 262 263 -264 265 -266 267 268 269 270 271 272 273 -274 -275 276 277 278 -279 280 281 282 -283 284 -285 -286 287 -288 289 290 291 -292 -293 294 295 -296 -297 298 -299 300 -301 302 -303 304 -305 306 307 308 -309 -310 -311 312 313 314 -315 -316 -317 -318 319 320 -321 322 323 324 325 326 -327 -328 -329 -330 -331 -332 333 334 -335 -336 -337 338 339 -340 -341 342 -343 344 -345 346 347 -348 349 350 -351 -352 -353 -354 -355 356 -357 -358 359 360 361 -362 -363 364 365 366 367 -368 -369 370 371 372 -373 374 -375 376 377 -378 -379 380 381 382 -383 384 385 386 387 388 -389 -390 -391 392 -393 394 -395 -396 -397 -398 -399 400 -401 402 -403 -404 -405 -406 -407 -408 409 410 411 -412 -413 -414 415 -416 -417 418 -419 -420 
0.29/0.32	v 0 
0.29/0.32	c Done (mycputime is 0.320 seconds)

Verifier Data 

OK

Watcher Data 

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

command line: BIN/runsolver --timestamp -w /tmp/evaluation-result-1523805-1238574617/watcher-1523805-1238574617 -o /tmp/evaluation-result-1523805-1238574617/solver-1523805-1238574617 -C 1200 -W 1800 -M 1800 --output-limit 1,15 HOME/Hybrid2 HOME/instance-1523805-1238574617.cnf 584956811 

Enforcing CPUTime limit (soft limit, will send SIGTERM then SIGKILL): 1200 seconds
Enforcing CPUTime limit (hard limit, will send SIGXCPU): 1230 seconds
Enforcing wall clock limit (soft limit, will send SIGTERM then SIGKILL): 1800 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
Solver output will be limited to a maximum of 15728640 bytes. The first 1048576 bytes and the last 14680064 bytes will be preserved
Current StackSize limit: 10240 KiB


[startup+0 s]
/proc/loadavg: 1.00 1.00 1.00 3/69 20248
/proc/meminfo: memFree=1502176/2055920 swapFree=4171336/4192956
[pid=20248] ppid=20246 vsize=450940 CPUtime=0
/proc/20248/stat : 20248 (Hybrid2) R 20246 20248 19776 0 -1 4194304 135 0 0 0 0 0 0 0 18 0 1 0 1130124891 461762560 119 1992294400 134512640 135106774 4294956208 18446744073709551615 134524229 0 0 4096 0 0 0 0 17 1 0 0
/proc/20248/statm: 112735 119 53 145 0 111611 0

[startup+0.076779 s]
/proc/loadavg: 1.00 1.00 1.00 3/69 20248
/proc/meminfo: memFree=1502176/2055920 swapFree=4171336/4192956
[pid=20248] ppid=20246 vsize=455004 CPUtime=0.07
/proc/20248/stat : 20248 (Hybrid2) R 20246 20248 19776 0 -1 4194304 184 0 0 0 7 0 0 0 18 0 1 0 1130124891 465924096 168 1992294400 134512640 135106774 4294956208 18446744073709551615 134527355 0 0 4096 0 0 0 0 17 1 0 0
/proc/20248/statm: 113751 168 56 145 0 112627 0
Current children cumulated CPU time (s) 0.07
Current children cumulated vsize (KiB) 455004

[startup+0.101778 s]
/proc/loadavg: 1.00 1.00 1.00 3/69 20248
/proc/meminfo: memFree=1502176/2055920 swapFree=4171336/4192956
[pid=20248] ppid=20246 vsize=455004 CPUtime=0.09
/proc/20248/stat : 20248 (Hybrid2) R 20246 20248 19776 0 -1 4194304 184 0 0 0 9 0 0 0 18 0 1 0 1130124891 465924096 168 1992294400 134512640 135106774 4294956208 18446744073709551615 134528771 0 0 4096 0 0 0 0 17 1 0 0
/proc/20248/statm: 113751 168 56 145 0 112627 0
Current children cumulated CPU time (s) 0.09
Current children cumulated vsize (KiB) 455004

[startup+0.301798 s]
/proc/loadavg: 1.00 1.00 1.00 3/69 20248
/proc/meminfo: memFree=1502176/2055920 swapFree=4171336/4192956
[pid=20248] ppid=20246 vsize=455004 CPUtime=0.29
/proc/20248/stat : 20248 (Hybrid2) R 20246 20248 19776 0 -1 4194304 184 0 0 0 29 0 0 0 19 0 1 0 1130124891 465924096 168 1992294400 134512640 135106774 4294956208 18446744073709551615 134526807 0 0 4096 0 0 0 0 17 1 0 0
/proc/20248/statm: 113751 168 56 145 0 112627 0
Current children cumulated CPU time (s) 0.29
Current children cumulated vsize (KiB) 455004

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

Child status: 10
Real time (s): 0.324357
CPU time (s): 0.323949
CPU user time (s): 0.32295
CPU system time (s): 0.000999
CPU usage (%): 99.8742
Max. virtual memory (cumulated for all children) (KiB): 455004

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

runsolver used 0.003999 second user time and 0.005999 second system time

The end

Launcher Data 

Begin job on node44 at 2009-04-01 10:30:17
IDJOB=1523805
IDBENCH=70666
IDSOLVER=530
FILE ID=node44/1523805-1238574617
PBS_JOBID= 9062176
Free space on /tmp= 66400 MiB

SOLVER NAME= Hybrid2 2009-03-22
BENCH NAME= SAT09/RANDOM/MEDIUM/3SAT/SATISFIABLE/420/unif-k3-r4.25-v420-c1785-S1940784272-089.cnf
COMMAND LINE= HOME/Hybrid2 BENCHNAME RANDOMSEED
RUNSOLVER COMMAND LINE= BIN/runsolver --timestamp -w /tmp/evaluation-result-1523805-1238574617/watcher-1523805-1238574617 -o /tmp/evaluation-result-1523805-1238574617/solver-1523805-1238574617 -C 1200 -W 1800 -M 1800 --output-limit 1,15  HOME/Hybrid2 HOME/instance-1523805-1238574617.cnf 584956811

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

MD5SUM BENCH= bd1e8bac20c24526524d34ea2c494a05
RANDOM SEED=584956811

node44.alineos.net Linux 2.6.9-22.EL.rootsmp #1 SMP Mon Oct 3 08:59:52 CEST 2005

/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.241
cache size	: 2048 KB
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 pni monitor ds_cpl cid cx16 xtpr
bogomips	: 5914.62
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.241
cache size	: 2048 KB
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 pni monitor ds_cpl cid cx16 xtpr
bogomips	: 5586.94
clflush size	: 64
cache_alignment	: 128
address sizes	: 36 bits physical, 48 bits virtual
power management:


/proc/meminfo:
MemTotal:      2055920 kB
MemFree:       1502656 kB
Buffers:         93280 kB
Cached:         353292 kB
SwapCached:      11068 kB
Active:         212000 kB
Inactive:       247160 kB
HighTotal:           0 kB
HighFree:            0 kB
LowTotal:      2055920 kB
LowFree:       1502656 kB
SwapTotal:     4192956 kB
SwapFree:      4171336 kB
Dirty:            4632 kB
Writeback:           0 kB
Mapped:          18228 kB
Slab:            79428 kB
Committed_AS:  2793112 kB
PageTables:       1796 kB
VmallocTotal: 536870911 kB
VmallocUsed:    264952 kB
VmallocChunk: 536605679 kB
HugePages_Total:     0
HugePages_Free:      0
Hugepagesize:     2048 kB

Free space on /tmp at the end= 66396 MiB
End job on node44 at 2009-04-01 10:30:18