Trace number 318559

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
MiraXT v2UNSAT 1.3128 1.31438

General information on the benchmark

Nameindustrial/babic/
dspam/dspam_dump_vc1080.cnf
MD5SUM4648b50fdaaf9e2a2c3c691f7cb02f96
Bench CategoryINDUST (industrial instances)
Best result obtained on this benchmarkUNSAT
Best CPU time to get the best result obtained on this benchmark1.20881
Satisfiable
(Un)Satisfiability was proved
Number of variables118226
Number of clauses375379
Sum of the clauses size994145
Maximum clause length3
Minimum clause length1
Number of clauses of size 13289
Number of clauses of size 2125414
Number of clauses of size 3246676
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.00/0.00	c Starting MiraXTv2...
1.29/1.30	s UNSATISFIABLE

Verifier Data (download as text)

No possible verification on an UNSAT instance

Watcher Data (download as text)

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

command line: runsolver --timestamp -w ROOT/results/node11/watcher-318559-1178882982 -o ROOT/results/node11/solver-318559-1178882982 -C 1200 -W 2400 -M 1800 --output-limit 1,15 /tmp/evaluation/318559-1178882982/MiraXTv2_dyn /tmp/evaluation/318559-1178882982/instance-318559-1178882982.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.85 0.91 0.97 3/77 26417
/proc/meminfo: memFree=1646848/2055920 swapFree=4144152/4192956
[pid=26417] ppid=26415 vsize=3788 CPUtime=0
/proc/26417/stat : 26417 (MiraXTv2_dyn) R 26415 26417 25109 0 -1 4194304 404 0 0 0 0 0 0 0 18 0 1 0 329347232 3878912 379 18446744073709551615 134512640 134597668 4294956656 18446744073709551615 4294960144 0 0 4096 0 0 0 0 17 1 0 0
/proc/26417/statm: 947 387 202 20 0 305 0

[startup+0.022259 s]
/proc/loadavg: 0.85 0.91 0.97 3/77 26417
/proc/meminfo: memFree=1646848/2055920 swapFree=4144152/4192956
[pid=26417] ppid=26415 vsize=8292 CPUtime=0.01
/proc/26417/stat : 26417 (MiraXTv2_dyn) R 26415 26417 25109 0 -1 4194304 1560 0 0 0 1 0 0 0 18 0 1 0 329347232 8491008 1526 18446744073709551615 134512640 134597668 4294956656 18446744073709551615 134579235 0 0 4096 0 0 0 0 17 1 0 0
/proc/26417/statm: 2073 1528 206 20 0 1431 0
Current children cumulated CPU time (s) 0.01
Current children cumulated vsize (KiB) 8292

[startup+0.101269 s]
/proc/loadavg: 0.85 0.91 0.97 3/77 26417
/proc/meminfo: memFree=1646848/2055920 swapFree=4144152/4192956
[pid=26417] ppid=26415 vsize=20412 CPUtime=0.09
/proc/26417/stat : 26417 (MiraXTv2_dyn) R 26415 26417 25109 0 -1 4194304 4079 0 0 0 8 1 0 0 18 0 1 0 329347232 20901888 4029 18446744073709551615 134512640 134597668 4294956656 18446744073709551615 8414843 0 0 4096 0 0 0 0 17 1 0 0
/proc/26417/statm: 5103 4030 206 20 0 4461 0
Current children cumulated CPU time (s) 0.09
Current children cumulated vsize (KiB) 20412

[startup+0.301295 s]
/proc/loadavg: 0.85 0.91 0.97 3/77 26417
/proc/meminfo: memFree=1646848/2055920 swapFree=4144152/4192956
[pid=26417] ppid=26415 vsize=31464 CPUtime=0.29
/proc/26417/stat : 26417 (MiraXTv2_dyn) R 26415 26417 25109 0 -1 4194304 6707 0 0 0 25 4 0 0 19 0 1 0 329347232 32219136 6657 18446744073709551615 134512640 134597668 4294956656 18446744073709551615 8414843 0 0 4096 0 0 0 0 17 1 0 0
/proc/26417/statm: 7866 6658 206 20 0 7224 0
Current children cumulated CPU time (s) 0.29
Current children cumulated vsize (KiB) 31464

[startup+0.701342 s]
/proc/loadavg: 0.85 0.91 0.97 3/77 26417
/proc/meminfo: memFree=1646848/2055920 swapFree=4144152/4192956
[pid=26417] ppid=26415 vsize=41784 CPUtime=0.69
/proc/26417/stat : 26417 (MiraXTv2_dyn) R 26415 26417 25109 0 -1 4194304 9324 0 0 0 64 5 0 0 22 0 1 0 329347232 42786816 9274 18446744073709551615 134512640 134597668 4294956656 18446744073709551615 8414843 0 0 4096 0 0 0 0 17 1 0 0
/proc/26417/statm: 10446 9274 207 20 0 9804 0
Current children cumulated CPU time (s) 0.69
Current children cumulated vsize (KiB) 41784

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

[startup+1.10639 s]
/proc/loadavg: 0.85 0.91 0.97 2/78 26418
/proc/meminfo: memFree=1603704/2055920 swapFree=4144152/4192956
[pid=26417] ppid=26415 vsize=52236 CPUtime=1.1
/proc/26417/stat : 26417 (MiraXTv2_dyn) R 26415 26417 25109 0 -1 4194304 11693 0 0 0 103 7 0 0 25 0 1 0 329347232 53489664 11643 18446744073709551615 134512640 134597668 4294956656 18446744073709551615 8414843 0 0 4096 0 0 0 0 17 1 0 0
/proc/26417/statm: 13059 11643 207 20 0 12417 0
Current children cumulated CPU time (s) 1.1
Current children cumulated vsize (KiB) 52236

[startup+1.30141 s]
/proc/loadavg: 0.85 0.91 0.97 2/78 26418
/proc/meminfo: memFree=1603704/2055920 swapFree=4144152/4192956
[pid=26417] ppid=26415 vsize=56148 CPUtime=1.29
/proc/26417/stat : 26417 (MiraXTv2_dyn) R 26415 26417 25109 0 -1 4194304 12756 0 0 0 122 7 0 0 25 0 1 0 329347232 57495552 12706 18446744073709551615 134512640 134597668 4294956656 18446744073709551615 134569691 0 0 4096 0 0 0 0 17 1 0 0
/proc/26417/statm: 14037 12706 207 20 0 13395 0
Current children cumulated CPU time (s) 1.29
Current children cumulated vsize (KiB) 56148

Child status: 20
Real time (s): 1.31438
CPU time (s): 1.3128
CPU user time (s): 1.22681
CPU system time (s): 0.085986
CPU usage (%): 99.8796
Max. virtual memory (cumulated for all children) (KiB): 56148

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

runsolver used 0.002999 second user time and 0.005999 second system time

The end

Launcher Data (download as text)

Begin job on node11 on Fri May 11 11:29:43 UTC 2007

IDJOB= 318559
IDBENCH= 20457
IDSOLVER= 129
FILE ID= node11/318559-1178882982

PBS_JOBID= 5251062

Free space on /tmp= 66549 MiB

SOLVER NAME= MiraXT v2
BENCH NAME= HOME/pub/bench/SAT07/industrial/babic/dspam/dspam_dump_vc1080.cnf
COMMAND LINE= /tmp/evaluation/318559-1178882982/MiraXTv2_dyn /tmp/evaluation/318559-1178882982/instance-318559-1178882982.cnf            
RUNSOLVER COMMAND LINE= runsolver  --timestamp  -w ROOT/results/node11/watcher-318559-1178882982 -o ROOT/results/node11/solver-318559-1178882982 -C 1200 -W 2400 -M 1800 --output-limit 1,15  /tmp/evaluation/318559-1178882982/MiraXTv2_dyn /tmp/evaluation/318559-1178882982/instance-318559-1178882982.cnf            

META MD5SUM SOLVER= 2ad149617ed8d249d89b067eb44c33da
MD5SUM BENCH=  4648b50fdaaf9e2a2c3c691f7cb02f96

RANDOM SEED= 30779689

TIME LIMIT= 1200 seconds
MEMORY LIMIT= 1800 MiB

Linux node11.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.235
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.235
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:       1647256 kB
Buffers:         50288 kB
Cached:         269296 kB
SwapCached:      18376 kB
Active:         154916 kB
Inactive:       189224 kB
HighTotal:           0 kB
HighFree:            0 kB
LowTotal:      2055920 kB
LowFree:       1647256 kB
SwapTotal:     4192956 kB
SwapFree:      4144152 kB
Dirty:           11132 kB
Writeback:           0 kB
Mapped:          29956 kB
Slab:            50004 kB
Committed_AS:  7646692 kB
PageTables:       1848 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= 66549 MiB

End job on node11 on Fri May 11 11:29:44 UTC 2007