Trace number 1522048

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
iPAWS 2009-03-22SAT 0.014997 0.0153331

General information on the benchmark

NameRANDOM/MEDIUM/5SAT/SATISFIABLE/100/
unif-k5-r21.3-v100-c2130-S308012126-046.cnf
MD5SUM8824df59c7b60dfa0748d28bf56c7110
Bench CategoryRANDOM (random instances)
Best result obtained on this benchmarkSAT
Best CPU time to get the best result obtained on this benchmark0.014996
Satisfiable
(Un)Satisfiability was proved
Number of variables100
Number of clauses2130
Sum of the clauses size10650
Maximum clause length5
Minimum clause length5
Number of clauses of size 10
Number of clauses of size 20
Number of clauses of size 30
Number of clauses of size 40
Number of clauses of size 52130
Number of clauses of size over 50

Solver Data 

0.00/0.01	s SATISFIABLE
0.00/0.01	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 0
0.00/0.01	c input file instance-1522048-1238457104.cnf, flips 1452

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-1522048-1238457104/watcher-1522048-1238457104 -o /tmp/evaluation-result-1522048-1238457104/solver-1522048-1238457104 -C 1200 -W 1800 -M 1800 --output-limit 1,15 HOME/iPAWS HOME/instance-1522048-1238457104.cnf 1193069146 

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: 0.91 0.97 0.99 3/73 25785
/proc/meminfo: memFree=1636224/2055920 swapFree=4177652/4192956
[pid=25785] ppid=25783 vsize=335916 CPUtime=0
/proc/25785/stat : 25785 (iPAWS) R 25783 25785 25483 0 -1 4194304 489 0 0 0 0 0 0 0 20 0 1 0 1118374339 343977984 473 1992294400 134512640 135114423 4294956208 18446744073709551615 134575464 0 0 4096 0 0 0 0 17 1 0 0
/proc/25785/statm: 83979 473 54 146 0 83831 0

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

Child status: 0
Real time (s): 0.0153331
CPU time (s): 0.014997
CPU user time (s): 0.011998
CPU system time (s): 0.002999
CPU usage (%): 97.8081
Max. virtual memory (cumulated for all children) (KiB): 0

getrusage(RUSAGE_CHILDREN,...) data:
user time used= 0.011998
system time used= 0.002999
maximum resident set size= 0
integral shared memory size= 0
integral unshared data size= 0
integral unshared stack size= 0
page reclaims= 950
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.004999 second user time and 0.004999 second system time

The end

Launcher Data 

Begin job on node84 at 2009-03-31 01:51:44
IDJOB=1522048
IDBENCH=70443
IDSOLVER=516
FILE ID=node84/1522048-1238457104
PBS_JOBID= 9061702
Free space on /tmp= 66312 MiB

SOLVER NAME= iPAWS 2009-03-22
BENCH NAME= SAT09/RANDOM/MEDIUM/5SAT/SATISFIABLE/100/unif-k5-r21.3-v100-c2130-S308012126-046.cnf
COMMAND LINE= HOME/iPAWS BENCHNAME RANDOMSEED
RUNSOLVER COMMAND LINE= BIN/runsolver --timestamp -w /tmp/evaluation-result-1522048-1238457104/watcher-1522048-1238457104 -o /tmp/evaluation-result-1522048-1238457104/solver-1522048-1238457104 -C 1200 -W 1800 -M 1800 --output-limit 1,15  HOME/iPAWS HOME/instance-1522048-1238457104.cnf 1193069146

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

MD5SUM BENCH= 8824df59c7b60dfa0748d28bf56c7110
RANDOM SEED=1193069146

node84.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.231
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.231
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	: 5996.54
clflush size	: 64
cache_alignment	: 128
address sizes	: 36 bits physical, 48 bits virtual
power management:


/proc/meminfo:
MemTotal:      2055920 kB
MemFree:       1636640 kB
Buffers:         70544 kB
Cached:         261628 kB
SwapCached:       6944 kB
Active:         142948 kB
Inactive:       198480 kB
HighTotal:           0 kB
HighFree:            0 kB
LowTotal:      2055920 kB
LowFree:       1636640 kB
SwapTotal:     4192956 kB
SwapFree:      4177652 kB
Dirty:             716 kB
Writeback:           0 kB
Mapped:          14856 kB
Slab:            62984 kB
Committed_AS:  2904148 kB
PageTables:       1980 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= 66312 MiB
End job on node84 at 2009-03-31 01:51:44