Trace number 320915

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
MXC 2007-02-08UNSAT 0.343946 0.3578

General information on the benchmark

Nameindustrial/babic/
xinetd/itox_vc1216.cnf
MD5SUMc076019a7fab0d8f88cfc5880f64abd3
Bench CategoryINDUST (industrial instances)
Best result obtained on this benchmarkUNSAT
Best CPU time to get the best result obtained on this benchmark0.343946
Satisfiable
(Un)Satisfiability was proved
Number of variables151619
Number of clauses440151
Sum of the clauses size1138189
Maximum clause length3
Minimum clause length1
Number of clauses of size 110189
Number of clauses of size 2161886
Number of clauses of size 3268076
Number of clauses of size 40
Number of clauses of size 50
Number of clauses of size over 50

Solver Data (download as text)

0.29/0.35	c MXC attempting /tmp/evaluation/320915-1176325253/instance-320915-1176325253.cnf
0.29/0.35	c 10689 assignments made, starting to guess now
0.29/0.35	c ===================================[MXC]=====================================
0.29/0.35	c | Conflicts |     ORIGINAL     |             LEARNT              | Progress |
0.29/0.35	c |           | Clauses Literals |  Limit Clauses Literals  Lit/Cl |          |
0.29/0.35	c =============================================================================
0.29/0.35	c |         0 |  267454   802362 |   89151       0       0     nan |  7.042 % |
0.29/0.35	c 0.330s elapsed
0.29/0.35	c restarts: 0
0.29/0.35	c decisions: 97
0.29/0.35	c propagations: 20791
0.29/0.35	c conflicts: 1
0.29/0.35	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/node10/watcher-320915-1176325253 -o ROOT/results/node10/solver-320915-1176325253 -C 1200 -W 2400 -M 1800 --output-limit 1,15 /tmp/evaluation/320915-1176325253/mxc /tmp/evaluation/320915-1176325253/instance-320915-1176325253.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.93 1.11 1.12 3/77 23692
/proc/meminfo: memFree=1872520/2055920 swapFree=4172956/4192956
[pid=23692] ppid=23690 vsize=9204 CPUtime=0
/proc/23692/stat : 23692 (mxc) R 23690 23692 21583 0 -1 4194304 758 0 0 0 0 0 0 0 18 0 1 0 108562848 9424896 742 18446744073709551615 134512640 135013041 4294956592 18446744073709551615 134550509 0 0 4096 0 0 0 0 17 1 0 0
/proc/23692/statm: 2301 748 42 122 0 2175 0

[startup+0.0972911 s]
/proc/loadavg: 0.93 1.11 1.12 3/77 23692
/proc/meminfo: memFree=1872520/2055920 swapFree=4172956/4192956
[pid=23692] ppid=23690 vsize=28896 CPUtime=0.09
/proc/23692/stat : 23692 (mxc) R 23690 23692 21583 0 -1 4194304 6355 0 0 0 6 3 0 0 18 0 1 0 108562848 29589504 6339 18446744073709551615 134512640 135013041 4294956592 18446744073709551615 134688363 0 0 4096 0 0 0 0 17 1 0 0
/proc/23692/statm: 7224 6339 46 122 0 7098 0
Current children cumulated CPU time (s) 0.09
Current children cumulated vsize (KiB) 28896

[startup+0.101291 s]
/proc/loadavg: 0.93 1.11 1.12 3/77 23692
/proc/meminfo: memFree=1872520/2055920 swapFree=4172956/4192956
[pid=23692] ppid=23690 vsize=29416 CPUtime=0.09
/proc/23692/stat : 23692 (mxc) R 23690 23692 21583 0 -1 4194304 6407 0 0 0 6 3 0 0 18 0 1 0 108562848 30121984 6391 18446744073709551615 134512640 135013041 4294956592 18446744073709551615 134688363 0 0 4096 0 0 0 0 17 1 0 0
/proc/23692/statm: 7354 6392 46 122 0 7228 0
Current children cumulated CPU time (s) 0.09
Current children cumulated vsize (KiB) 29416

[startup+0.301334 s]
/proc/loadavg: 0.93 1.11 1.12 3/77 23692
/proc/meminfo: memFree=1872520/2055920 swapFree=4172956/4192956
[pid=23692] ppid=23690 vsize=32192 CPUtime=0.29
/proc/23692/stat : 23692 (mxc) R 23690 23692 21583 0 -1 4194304 9004 0 0 0 25 4 0 0 19 0 1 0 108562848 32964608 6920 18446744073709551615 134512640 135013041 4294956592 18446744073709551615 134520329 0 0 4096 0 0 0 0 17 1 0 0
/proc/23692/statm: 8048 6920 47 122 0 7922 0
Current children cumulated CPU time (s) 0.29
Current children cumulated vsize (KiB) 32192

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

Child status: 20
Real time (s): 0.3578
CPU time (s): 0.343946
CPU user time (s): 0.290955
CPU system time (s): 0.052991
CPU usage (%): 96.128
Max. virtual memory (cumulated for all children) (KiB): 35216

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

runsolver used 0.003999 second user time and 0.005999 second system time

The end

Launcher Data (download as text)

Begin job on node10 on Wed Apr 11 21:00:53 UTC 2007

IDJOB= 320915
IDBENCH= 20515
IDSOLVER= 107
FILE ID= node10/320915-1176325253

PBS_JOBID= 4516507

Free space on /tmp= 66554 MiB

SOLVER NAME= MXC 2007-02-08
BENCH NAME= HOME/pub/bench/SAT07/industrial/babic/xinetd/itox_vc1216.cnf
COMMAND LINE= /tmp/evaluation/320915-1176325253/mxc /tmp/evaluation/320915-1176325253/instance-320915-1176325253.cnf            
RUNSOLVER COMMAND LINE= runsolver  --timestamp  -w ROOT/results/node10/watcher-320915-1176325253 -o ROOT/results/node10/solver-320915-1176325253 -C 1200 -W 2400 -M 1800 --output-limit 1,15  /tmp/evaluation/320915-1176325253/mxc /tmp/evaluation/320915-1176325253/instance-320915-1176325253.cnf            

META MD5SUM SOLVER= fd459248d3e92e664505cc2f0f683bf4
MD5SUM BENCH=  c076019a7fab0d8f88cfc5880f64abd3

RANDOM SEED= 298090398

TIME LIMIT= 1200 seconds
MEMORY LIMIT= 1800 MiB

Linux node10.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.259
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.259
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:       1872864 kB
Buffers:         11700 kB
Cached:          73676 kB
SwapCached:        576 kB
Active:          79048 kB
Inactive:        48032 kB
HighTotal:           0 kB
HighFree:            0 kB
LowTotal:      2055920 kB
LowFree:       1872864 kB
SwapTotal:     4192956 kB
SwapFree:      4172956 kB
Dirty:            9032 kB
Writeback:           0 kB
Mapped:          50992 kB
Slab:            41520 kB
Committed_AS:  2164636 kB
PageTables:       1728 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= 66554 MiB

End job on node10 on Wed Apr 11 21:00:54 UTC 2007