Trace number 321079

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.262959 0.277126

General information on the benchmark

Nameindustrial/babic/
xinetd/itox_vc979.cnf
MD5SUM0ebda2525041210e494c68044b8ad9a6
Bench CategoryINDUST (industrial instances)
Best result obtained on this benchmarkUNSAT
Best CPU time to get the best result obtained on this benchmark0.262959
Satisfiable
(Un)Satisfiability was proved
Number of variables115679
Number of clauses338708
Sum of the clauses size883655
Maximum clause length3
Minimum clause length1
Number of clauses of size 17057
Number of clauses of size 2118355
Number of clauses of size 3213296
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.19/0.27	c MXC attempting /tmp/evaluation/321079-1176326497/instance-321079-1176326497.cnf
0.19/0.27	c 7551 assignments made, starting to guess now
0.19/0.27	c ===================================[MXC]=====================================
0.19/0.27	c | Conflicts |     ORIGINAL     |             LEARNT              | Progress |
0.19/0.27	c |           | Clauses Literals |  Limit Clauses Literals  Lit/Cl |          |
0.19/0.27	c =============================================================================
0.19/0.27	c |         0 |  212809   638427 |   70936       0       0     nan |  6.518 % |
0.19/0.27	c 0.250s elapsed
0.19/0.27	c restarts: 0
0.19/0.27	c decisions: 1
0.19/0.27	c propagations: 17558
0.19/0.27	c conflicts: 1
0.19/0.27	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/node74/watcher-321079-1176326497 -o ROOT/results/node74/solver-321079-1176326497 -C 1200 -W 2400 -M 1800 --output-limit 1,15 /tmp/evaluation/321079-1176326497/mxc /tmp/evaluation/321079-1176326497/instance-321079-1176326497.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 0.97 0.99 3/66 29188
/proc/meminfo: memFree=1511080/2055920 swapFree=4192812/4192956
[pid=29188] ppid=29186 vsize=7164 CPUtime=0
/proc/29188/stat : 29188 (mxc) R 29186 29188 27762 0 -1 4194304 771 0 0 0 0 0 0 0 18 0 1 0 80564462 7335936 755 18446744073709551615 134512640 135013041 4294956608 18446744073709551615 134550509 0 0 4096 0 0 0 0 17 1 0 0
/proc/29188/statm: 1791 761 42 122 0 1665 0

[startup+0.068878 s]
/proc/loadavg: 0.93 0.97 0.99 3/66 29188
/proc/meminfo: memFree=1511080/2055920 swapFree=4192812/4192956
[pid=29188] ppid=29186 vsize=21992 CPUtime=0.06
/proc/29188/stat : 29188 (mxc) R 29186 29188 27762 0 -1 4194304 4782 0 0 0 4 2 0 0 18 0 1 0 80564462 22519808 4766 18446744073709551615 134512640 135013041 4294956608 18446744073709551615 134547915 0 0 4096 0 0 0 0 17 1 0 0
/proc/29188/statm: 5498 4767 46 122 0 5372 0
Current children cumulated CPU time (s) 0.06
Current children cumulated vsize (KiB) 21992

[startup+0.102881 s]
/proc/loadavg: 0.93 0.97 0.99 3/66 29188
/proc/meminfo: memFree=1511080/2055920 swapFree=4192812/4192956
[pid=29188] ppid=29186 vsize=23964 CPUtime=0.09
/proc/29188/stat : 29188 (mxc) R 29186 29188 27762 0 -1 4194304 5248 0 0 0 7 2 0 0 18 0 1 0 80564462 24539136 5232 18446744073709551615 134512640 135013041 4294956608 18446744073709551615 134522205 0 0 4096 0 0 0 0 17 1 0 0
/proc/29188/statm: 5991 5232 46 122 0 5865 0
Current children cumulated CPU time (s) 0.09
Current children cumulated vsize (KiB) 23964

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

[startup+0.202892 s]
/proc/loadavg: 0.93 0.97 0.99 3/66 29188
/proc/meminfo: memFree=1511080/2055920 swapFree=4192812/4192956
[pid=29188] ppid=29186 vsize=29768 CPUtime=0.19
/proc/29188/stat : 29188 (mxc) R 29186 29188 27762 0 -1 4194304 6658 0 0 0 17 2 0 0 18 0 1 0 80564462 30482432 6642 18446744073709551615 134512640 135013041 4294956608 18446744073709551615 134547915 0 0 4096 0 0 0 0 17 1 0 0
/proc/29188/statm: 7442 6644 46 122 0 7316 0
Current children cumulated CPU time (s) 0.19
Current children cumulated vsize (KiB) 29768

Child status: 20
Real time (s): 0.277126
CPU time (s): 0.262959
CPU user time (s): 0.228965
CPU system time (s): 0.033994
CPU usage (%): 94.8879
Max. virtual memory (cumulated for all children) (KiB): 29768

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

runsolver used 0.002999 second user time and 0.002999 second system time

The end

Launcher Data (download as text)

Begin job on node74 on Wed Apr 11 21:21:37 UTC 2007

IDJOB= 321079
IDBENCH= 20519
IDSOLVER= 107
FILE ID= node74/321079-1176326497

PBS_JOBID= 4516708

Free space on /tmp= 103238 MiB

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

META MD5SUM SOLVER= fd459248d3e92e664505cc2f0f683bf4
MD5SUM BENCH=  0ebda2525041210e494c68044b8ad9a6

RANDOM SEED= 313120347

TIME LIMIT= 1200 seconds
MEMORY LIMIT= 1800 MiB

Linux node74.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.213
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.213
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:       1511552 kB
Buffers:         36252 kB
Cached:         369436 kB
SwapCached:          0 kB
Active:         182060 kB
Inactive:       240608 kB
HighTotal:           0 kB
HighFree:            0 kB
LowTotal:      2055920 kB
LowFree:       1511552 kB
SwapTotal:     4192956 kB
SwapFree:      4192812 kB
Dirty:            6820 kB
Writeback:           0 kB
Mapped:          27324 kB
Slab:           107508 kB
Committed_AS:   109724 kB
PageTables:       1484 kB
VmallocTotal: 536870911 kB
VmallocUsed:    264960 kB
VmallocChunk: 536605679 kB
HugePages_Total:     0
HugePages_Free:      0
Hugepagesize:     2048 kB

Free space on /tmp at the end= 103238 MiB

End job on node74 on Wed Apr 11 21:21:37 UTC 2007