Trace number 318191

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 v1UNSAT 1.23581 1.24321

General information on the benchmark

Nameindustrial/babic/
dspam/dspam_dump_vc1093.cnf
MD5SUMfe5edee84f2eb21126b00640515281bf
Bench CategoryINDUST (industrial instances)
Best result obtained on this benchmarkUNSAT
Best CPU time to get the best result obtained on this benchmark1.08383
Satisfiable
(Un)Satisfiability was proved
Number of variables106648
Number of clauses337439
Sum of the clauses size896316
Maximum clause length3
Minimum clause length1
Number of clauses of size 12907
Number of clauses of size 2110187
Number of clauses of size 3224345
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 MiraXTv1...
1.19/1.23	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-318191-1178882885 -o ROOT/results/node11/solver-318191-1178882885 -C 1200 -W 2400 -M 1800 --output-limit 1,15 /tmp/evaluation/318191-1178882885/MiraXTv1_dyn /tmp/evaluation/318191-1178882885/instance-318191-1178882885.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.94 0.99 3/77 25353
/proc/meminfo: memFree=1672760/2055920 swapFree=4144152/4192956
[pid=25353] ppid=25351 vsize=3788 CPUtime=0
/proc/25353/stat : 25353 (MiraXTv1_dyn) R 25351 25353 25109 0 -1 4194304 402 0 0 0 0 0 0 0 18 0 1 0 329337451 3878912 378 18446744073709551615 134512640 134597700 4294956656 18446744073709551615 4294960144 0 0 4096 0 0 0 0 17 1 0 0
/proc/25353/statm: 947 386 202 20 0 305 0

[startup+0.008308 s]
/proc/loadavg: 0.85 0.94 0.99 3/77 25353
/proc/meminfo: memFree=1672760/2055920 swapFree=4144152/4192956
[pid=25353] ppid=25351 vsize=4728 CPUtime=0
/proc/25353/stat : 25353 (MiraXTv1_dyn) R 25351 25353 25109 0 -1 4194304 719 0 0 0 0 0 0 0 18 0 1 0 329337451 4841472 694 18446744073709551615 134512640 134597700 4294956656 18446744073709551615 8418253 0 0 4096 0 0 0 0 17 1 0 0
/proc/25353/statm: 1182 702 206 20 0 540 0
Current children cumulated CPU time (s) 0
Current children cumulated vsize (KiB) 4728

[startup+0.10132 s]
/proc/loadavg: 0.85 0.94 0.99 3/77 25353
/proc/meminfo: memFree=1672760/2055920 swapFree=4144152/4192956
[pid=25353] ppid=25351 vsize=20676 CPUtime=0.09
/proc/25353/stat : 25353 (MiraXTv1_dyn) R 25351 25353 25109 0 -1 4194304 3877 0 0 0 7 2 0 0 18 0 1 0 329337451 21172224 3838 18446744073709551615 134512640 134597700 4294956656 18446744073709551615 8414843 0 0 4096 0 0 0 0 17 1 0 0
/proc/25353/statm: 5169 3838 206 20 0 4527 0
Current children cumulated CPU time (s) 0.09
Current children cumulated vsize (KiB) 20676

[startup+0.301343 s]
/proc/loadavg: 0.85 0.94 0.99 3/77 25353
/proc/meminfo: memFree=1672760/2055920 swapFree=4144152/4192956
[pid=25353] ppid=25351 vsize=31596 CPUtime=0.29
/proc/25353/stat : 25353 (MiraXTv1_dyn) R 25351 25353 25109 0 -1 4194304 6483 0 0 0 26 3 0 0 19 0 1 0 329337451 32354304 6444 18446744073709551615 134512640 134597700 4294956656 18446744073709551615 8414843 0 0 4096 0 0 0 0 17 1 0 0
/proc/25353/statm: 7899 6445 206 20 0 7257 0
Current children cumulated CPU time (s) 0.29
Current children cumulated vsize (KiB) 31596

[startup+0.70139 s]
/proc/loadavg: 0.85 0.94 0.99 3/77 25353
/proc/meminfo: memFree=1672760/2055920 swapFree=4144152/4192956
[pid=25353] ppid=25351 vsize=40872 CPUtime=0.69
/proc/25353/stat : 25353 (MiraXTv1_dyn) R 25351 25353 25109 0 -1 4194304 8772 0 0 0 65 4 0 0 22 0 1 0 329337451 41852928 8733 18446744073709551615 134512640 134597700 4294956656 18446744073709551615 8418837 0 0 4096 0 0 0 0 17 1 0 0
/proc/25353/statm: 10218 8733 207 20 0 9576 0
Current children cumulated CPU time (s) 0.69
Current children cumulated vsize (KiB) 40872

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

[startup+1.10545 s]
/proc/loadavg: 0.85 0.94 0.99 2/78 25354
/proc/meminfo: memFree=1632048/2055920 swapFree=4144152/4192956
[pid=25353] ppid=25351 vsize=48960 CPUtime=1.09
/proc/25353/stat : 25353 (MiraXTv1_dyn) R 25351 25353 25109 0 -1 4194304 10978 0 0 0 104 5 0 0 25 0 1 0 329337451 50135040 10939 18446744073709551615 134512640 134597700 4294956656 18446744073709551615 8418493 0 0 4096 0 0 0 0 17 0 0 0
/proc/25353/statm: 12240 10939 207 20 0 11598 0
Current children cumulated CPU time (s) 1.09
Current children cumulated vsize (KiB) 48960

[startup+1.20145 s]
/proc/loadavg: 0.85 0.94 0.99 2/78 25354
/proc/meminfo: memFree=1632048/2055920 swapFree=4144152/4192956
[pid=25353] ppid=25351 vsize=53028 CPUtime=1.19
/proc/25353/stat : 25353 (MiraXTv1_dyn) R 25351 25353 25109 0 -1 4194304 11569 0 0 0 113 6 0 0 25 0 1 0 329337451 54300672 11530 18446744073709551615 134512640 134597700 4294956656 18446744073709551615 134581523 0 0 4096 0 0 0 0 17 0 0 0
/proc/25353/statm: 13257 11530 207 20 0 12615 0
Current children cumulated CPU time (s) 1.19
Current children cumulated vsize (KiB) 53028

Child status: 20
Real time (s): 1.24321
CPU time (s): 1.23581
CPU user time (s): 1.16682
CPU system time (s): 0.068989
CPU usage (%): 99.4051
Max. virtual memory (cumulated for all children) (KiB): 53028

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

runsolver used 0.004999 second user time and 0.003999 second system time

The end

Launcher Data (download as text)

Begin job on node11 on Fri May 11 11:28:05 UTC 2007

IDJOB= 318191
IDBENCH= 20448
IDSOLVER= 130
FILE ID= node11/318191-1178882885

PBS_JOBID= 5251062

Free space on /tmp= 66550 MiB

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

META MD5SUM SOLVER= 2ad149617ed8d249d89b067eb44c33da
MD5SUM BENCH=  fe5edee84f2eb21126b00640515281bf

RANDOM SEED= 249579956

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:       1672976 kB
Buffers:         50024 kB
Cached:         244264 kB
SwapCached:      18376 kB
Active:         137380 kB
Inactive:       181540 kB
HighTotal:           0 kB
HighFree:            0 kB
LowTotal:      2055920 kB
LowFree:       1672976 kB
SwapTotal:     4192956 kB
SwapFree:      4144152 kB
Dirty:           10392 kB
Writeback:           0 kB
Mapped:          29956 kB
Slab:            49516 kB
Committed_AS:  7626856 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= 66550 MiB

End job on node11 on Fri May 11 11:28:07 UTC 2007