Trace number 192084

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
Tramontane 2006-12-04SAT 0.603907 0.653122

General information on the benchmark

Namequeens/
queens-120.xml
MD5SUM548120b0d306cf96da26e553b06794d8
Bench Category2-ARY-INT (binary constraints in intension)
Best result obtained on this benchmarkSAT
Best CPU time to get the best result obtained on this benchmark0.603907
SatisfiableYES
(Un)Satisfiability was provedYES
Number of variables120
Number of constraints7140
Maximum constraint arity2
Maximum domain size120
Number of constraints which are defined in extension0
Number of constraints which are defined in intension7140
Global constraints used (with number of constraints)

Solver Data (download as text)

0.06	c 
0.06	c Parsing xml file
0.06	c 	domains...............    0
0.06	c 	variables.............    0
0.06	c 	predicates............    0
0.06	c 	constraints........... 0.47
0.53	c Allocating memory
0.53	c 
0.53	c time limit = -1
0.53	c heuristic = dom/wdeg
0.53	c restart policy = Geometric increment
0.53	c restart base = 79
0.53	c restart factor = 1.33
0.53	c 
0.53	c Solving
0.53	c
0.64	s SATISFIABLE
0.64	v 1 3 5 73 98 4 85 7 93 68 70 84 6 91 97 104 8 105 116 88 96 103 9 118 108 112 107 48 89 10 79 47 83 57 45 75 56 11 46 43 58 64 61 40 49 18 12 81 37 82 77 92 78 60 42 19 13 69 54 95 113 39 99 115 33 120 20 14 106 101 114 117 94 102 109 90 119 87 21 15 111 71 110 76 22 35 100 38 51 74 65 23 16 55 53 63 66 24 59 52 72 80 44 86 25 30 17 62 28 67 50 29 26 32 36 41 2 27 31 34
0.64	d          SAT         8 BTS      0.09 s

Verifier Data (download as text)

OK

Watcher Data (download as text)

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

command line: runsolver --timestamp -w ROOT/results/node24/watcher-192084-1168096597 -o ROOT/results/node24/solver-192084-1168096597 -C 1800 -M 900 /tmp/evaluation/192084-1168096597/tramontane/bin/solver /tmp/evaluation/192084-1168096597/unknown.xml -res geom -f 3 -v 1 

Enforcing CPUTime limit (soft limit, will send SIGTERM then SIGKILL): 1800 seconds
Enforcing CPUTime limit (hard limit, will send SIGXCPU): 1830 seconds
Enforcing VSIZE limit (soft limit, will send SIGTERM then SIGKILL): 921600 KiB
Enforcing VSIZE limit (hard limit, stack expansion will fail with SIGSEGV, brk() and mmap() will return ENOMEM): 972800 KiB
Current StackSize limit: 10240 KiB

/proc/loadavg: 0.50 0.46 0.89 1/83 23514
/proc/meminfo: memFree=1820400/2055920 swapFree=4192812/4192956
[pid=23513] ppid=23510 vsize=540 CPUtime=0
/proc/23513/stat : 23513 (solver) D 23510 23513 23206 0 -1 4194304 41 0 0 0 0 0 0 0 18 0 1 0 158055969 552960 26 18446744073709551615 134512640 134893233 4294956656 18446744073709551615 2605860 0 2147483391 4096 0 18446744072099855350 0 0 17 0 0 0
/proc/23513/statm: 135 26 21 92 0 18 0

[startup+0.101718 s]
/proc/loadavg: 0.50 0.46 0.89 1/83 23514
/proc/meminfo: memFree=1820400/2055920 swapFree=4192812/4192956
[pid=23513] ppid=23510 vsize=7180 CPUtime=0.04
/proc/23513/stat : 23513 (solver) R 23510 23513 23206 0 -1 4194304 893 0 0 0 4 0 0 0 18 0 1 0 158055969 7352320 861 18446744073709551615 134512640 134893233 4294956656 18446744073709551615 3040891 0 0 4096 0 0 0 0 17 1 0 0
/proc/23513/statm: 1795 861 706 92 0 139 0
Current children cumulated CPU time (s) 0.04
Current children cumulated vsize (KiB) 7180

[startup+0.509757 s]
/proc/loadavg: 0.50 0.46 0.89 1/83 23514
/proc/meminfo: memFree=1820400/2055920 swapFree=4192812/4192956
[pid=23513] ppid=23510 vsize=8928 CPUtime=0.45
/proc/23513/stat : 23513 (solver) R 23510 23513 23206 0 -1 4194304 1310 0 0 0 45 0 0 0 21 0 1 0 158055969 9142272 1278 18446744073709551615 134512640 134893233 4294956656 18446744073709551615 4159381097 0 0 4096 0 0 0 0 17 1 0 0
/proc/23513/statm: 2232 1278 706 92 0 576 0
Current children cumulated CPU time (s) 0.45
Current children cumulated vsize (KiB) 8928

Child status: 0
Real time (s): 0.653122
CPU time (s): 0.603907
CPU user time (s): 0.593909
CPU system time (s): 0.009998
CPU usage (%): 92.4647
Max. virtual memory (cumulated for all children) (KiB): 9720

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

runsolver used 0.002999 s user time and 0.007998 s system time

The end

Launcher Data (download as text)

Begin job on node24 on Sat Jan  6 15:16:39 UTC 2007


IDJOB= 192084
IDBENCH= 3089
FILE ID= node24/192084-1168096597

PBS_JOBID= 3476764

Free space on /tmp= 66462 MiB

BENCH NAME= HOME/pub/bench/CPAI06/queens/queens-120.xml
COMMAND LINE= /tmp/evaluation/192084-1168096597/tramontane/bin/solver /tmp/evaluation/192084-1168096597/unknown.xml -res geom -f 3 -v 1
RUNSOLVER COMMAND LINE= runsolver  --timestamp  -w ROOT/results/node24/watcher-192084-1168096597 -o ROOT/results/node24/solver-192084-1168096597 -C 1800 -M 900  /tmp/evaluation/192084-1168096597/tramontane/bin/solver /tmp/evaluation/192084-1168096597/unknown.xml -res geom -f 3 -v 1

META MD5SUM SOLVER= cb80ed4ac975bdc0101f830a5b1b8f77
MD5SUM BENCH=  548120b0d306cf96da26e553b06794d8

RANDOM SEED= 364131896

TIME LIMIT= 1800 seconds

MEMORY LIMIT= 900 MiB


/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.234
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.234
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:       1821512 kB
Buffers:         21344 kB
Cached:          98472 kB
SwapCached:          0 kB
Active:          92684 kB
Inactive:        84376 kB
HighTotal:           0 kB
HighFree:            0 kB
LowTotal:      2055920 kB
LowFree:       1821512 kB
SwapTotal:     4192956 kB
SwapFree:      4192812 kB
Dirty:            5748 kB
Writeback:           0 kB
Mapped:          76264 kB
Slab:            42384 kB
Committed_AS:  3028000 kB
PageTables:       2196 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= 66462 MiB



End job on node24 on Sat Jan  6 15:16:51 UTC 2007