Trace number 330334

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, and are wall clock time (not CPU 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
minimarch 2007-02-08UNSAT 0.370943 0.372528

General information on the benchmark

Nameindustrial/IBM_FV_2004_30/
IBM_FV_2004_rule_batch_30_SAT_dat.k20.cnf
MD5SUM42009d0a86b074043b8da4b9e8720c85
Bench CategoryINDUST (industrial instances)
Best result obtained on this benchmark
Best CPU time to get the best result obtained on this benchmark
Satisfiable
(Un)Satisfiability was proved
Number of variables39544
Number of clauses163269
Sum of the clauses size415841
Maximum clause length12
Minimum clause length1
Number of clauses of size 12072
Number of clauses of size 2114940
Number of clauses of size 330226
Number of clauses of size 45754
Number of clauses of size 53259
Number of clauses of size over 57018

Solver Data (download as text)

0.00/0.00	This is MiniMarch, a modified version of MiniSat 2.0 beta
0.00/0.00	WARNING: for repeatability, setting FPU to use double precision
0.00/0.00	============================[ Problem Statistics ]=============================
0.00/0.00	|                                                                             |
0.00/0.00	|  Number of variables:  39544                                                |
0.00/0.00	|  Number of clauses:    163269                                               |
0.29/0.36	|  Parsing time:         0.35         s                                       |
0.29/0.36	Solved by unit propagation
0.29/0.36	s UNSATISFIABLE

Verifier Data (download as text)

No possible verification on an UNSAT instance

Watcher Data (download as text)

runsolver version 3.2.1 (c) roussel@cril.univ-artois.fr

command line: runsolver --timestamp -w ROOT/results/node17/watcher-330334-1173162588 -o ROOT/results/node17/solver-330334-1173162588 -C 1200 -W 2400 -M 1800 --output-limit 1,15 /tmp/evaluation/330334-1173162588/minimarch /tmp/evaluation/330334-1173162588/instance-330334-1173162588.cnf 

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): 2400 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.98 0.96 3/77 26107
/proc/meminfo: memFree=1822528/2055920 swapFree=4168576/4192956
[pid=26107] ppid=26105 vsize=1736 CPUtime=0
/proc/26107/stat : 26107 (minimarch) R 26105 26107 25994 0 -1 4194304 330 0 0 0 0 0 0 0 18 0 1 0 336213055 1777664 314 18446744073709551615 134512640 135054332 4294956704 18446744073709551615 134518464 0 0 4096 3 0 0 0 17 1 0 0
/proc/26107/statm: 434 314 45 132 0 299 0

[startup+0.053791 s]
/proc/loadavg: 0.91 0.98 0.96 3/77 26107
/proc/meminfo: memFree=1822528/2055920 swapFree=4168576/4192956
[pid=26107] ppid=26105 vsize=5740 CPUtime=0.04
/proc/26107/stat : 26107 (minimarch) R 26105 26107 25994 0 -1 4194304 1288 0 0 0 4 0 0 0 18 0 1 0 336213055 5877760 1272 18446744073709551615 134512640 135054332 4294956704 18446744073709551615 134691888 0 0 4096 3 0 0 0 17 1 0 0
/proc/26107/statm: 1471 1278 51 132 0 1336 0
Current children cumulated CPU time (s) 0.04
Current children cumulated vsize (KiB) 5740

[startup+0.102796 s]
/proc/loadavg: 0.91 0.98 0.96 3/77 26107
/proc/meminfo: memFree=1822528/2055920 swapFree=4168576/4192956
[pid=26107] ppid=26105 vsize=9492 CPUtime=0.09
/proc/26107/stat : 26107 (minimarch) R 26105 26107 25994 0 -1 4194304 2171 0 0 0 8 1 0 0 18 0 1 0 336213055 9719808 2155 18446744073709551615 134512640 135054332 4294956704 18446744073709551615 134688823 0 0 4096 3 0 0 0 17 1 0 0
/proc/26107/statm: 2373 2155 51 132 0 2238 0
Current children cumulated CPU time (s) 0.09
Current children cumulated vsize (KiB) 9492

[startup+0.302817 s]
/proc/loadavg: 0.91 0.98 0.96 3/77 26107
/proc/meminfo: memFree=1822528/2055920 swapFree=4168576/4192956
[pid=26107] ppid=26105 vsize=15604 CPUtime=0.29
/proc/26107/stat : 26107 (minimarch) R 26105 26107 25994 0 -1 4194304 3659 0 0 0 28 1 0 0 19 0 1 0 336213055 15978496 3643 18446744073709551615 134512640 135054332 4294956704 18446744073709551615 134523331 0 0 4096 3 0 0 0 17 1 0 0
/proc/26107/statm: 3901 3643 51 132 0 3766 0
Current children cumulated CPU time (s) 0.29
Current children cumulated vsize (KiB) 15604

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

Child status: 20
Real time (s): 0.372528
CPU time (s): 0.370943
CPU user time (s): 0.347947
CPU system time (s): 0.022996
CPU usage (%): 99.5745
Max. virtual memory (cumulated for all children) (KiB): 15604

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

runsolver used 0.000999 second user time and 0.005999 second system time

The end

Launcher Data (download as text)

Begin job on node17 on Tue Mar  6 06:29:48 UTC 2007

IDJOB= 330334
IDBENCH= 20561
IDSOLVER= 110
FILE ID= node17/330334-1173162588

PBS_JOBID= 4015013

Free space on /tmp= 66514 MiB

SOLVER NAME= minimarch 2007-02-08
BENCH NAME= HOME/pub/bench/SAT07/industrial/IBM_FV_2004_30/IBM_FV_2004_rule_batch_30_SAT_dat.k20.cnf
COMMAND LINE= /tmp/evaluation/330334-1173162588/minimarch /tmp/evaluation/330334-1173162588/instance-330334-1173162588.cnf            
RUNSOLVER COMMAND LINE= runsolver  --timestamp  -w ROOT/results/node17/watcher-330334-1173162588 -o ROOT/results/node17/solver-330334-1173162588 -C 1200 -W 2400 -M 1800 --output-limit 1,15  /tmp/evaluation/330334-1173162588/minimarch /tmp/evaluation/330334-1173162588/instance-330334-1173162588.cnf            

META MD5SUM SOLVER= cd0143c15836d32fe9acb8d523a59b67
MD5SUM BENCH=  42009d0a86b074043b8da4b9e8720c85

RANDOM SEED= 308172208

TIME LIMIT= 1200 seconds
MEMORY LIMIT= 1800 MiB

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

/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.229
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.229
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:       1822936 kB
Buffers:         31032 kB
Cached:         128144 kB
SwapCached:       2120 kB
Active:          72232 kB
Inactive:       109212 kB
HighTotal:           0 kB
HighFree:            0 kB
LowTotal:      2055920 kB
LowFree:       1822936 kB
SwapTotal:     4192956 kB
SwapFree:      4168576 kB
Dirty:            5980 kB
Writeback:           0 kB
Mapped:          30136 kB
Slab:            37144 kB
Committed_AS:  1384208 kB
PageTables:       1748 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= 66514 MiB

End job on node17 on Tue Mar  6 06:29:49 UTC 2007