Trace number 201765

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.511921 0.517533

General information on the benchmark

Namerlfap/rlfapScens/
scen2.xml
MD5SUM6fd929da3fdebf81252e0d9d01639132
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.480926
SatisfiableYES
(Un)Satisfiability was provedYES
Number of variables200
Number of constraints1235
Maximum constraint arity2
Maximum domain size44
Number of constraints which are defined in extension0
Number of constraints which are defined in intension1235
Global constraints used (with number of constraints)

Solver Data (download as text)

0.01	c 
0.01	c Parsing xml file
0.01	c 	domains...............    0
0.01	c 	variables.............    0
0.02	c 	predicates............    0
0.02	c 	constraints........... 0.07
0.09	c Allocating memory
0.09	c 
0.09	c time limit = -1
0.09	c heuristic = dom/wdeg
0.09	c restart policy = Geometric increment
0.09	c restart base = 133
0.09	c restart factor = 1.33
0.09	c 
0.09	c Solving
0.09	c
0.38	s SATISFIABLE
0.38	v 72 310 694 456 30 268 254 16 86 324 114 352 254 16 16 254 324 86 156 394 156 394 268 30 296 58 128 366 30 268 16 254 380 142 394 156 324 86 254 16 254 16 338 100 338 100 254 16 100 338 100 338 268 30 100 338 338 100 414 652 72 310 680 442 16 254 352 114 366 128 352 114 352 114 44 282 100 338 30 268 338 100 352 114 114 352 30 268 58 296 44 282 100 338 72 310 268 30 16 254 16 254 142 380 338 100 254 16 16 254 30 268 352 114 282 44 366 128 58 296 352 114 268 30 380 142 310 72 30 268 282 44 268 30 44 282 114 352 30 268 44 282 352 114 366 128 16 254 254 16 268 30 16 254 142 380 16 254 254 16 338 100 268 30 86 324 156 394 30 268 128 366 100 338 100 338 366 128 16 254 338 100 86 324 268 30 100 338 30 268 100 338 30 268 100 338 142 380 30 268
0.38	d          SAT         0 BTS      0.06 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/node48/watcher-201765-1168149649 -o ROOT/results/node48/solver-201765-1168149649 -C 1800 -M 900 /tmp/evaluation/201765-1168149649/tramontane/bin/solver /tmp/evaluation/201765-1168149649/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: 1.08 1.02 1.05 6/69 22218
/proc/meminfo: memFree=1250184/2055920 swapFree=4192812/4192956
[pid=22217] ppid=22212 vsize=4504 CPUtime=0
/proc/22217/stat : 22217 (solver) R 22212 22217 21237 0 -1 4194304 44 0 0 0 0 0 0 0 18 0 1 0 163363657 4612096 29 18446744073709551615 134512640 134893233 4294956656 18446744073709551615 3484807 0 0 4096 0 0 0 0 17 1 0 0
/proc/22217/statm: 1126 31 23 92 0 19 0

[startup+0.107114 s]
/proc/loadavg: 1.08 1.02 1.05 6/69 22218
/proc/meminfo: memFree=1250184/2055920 swapFree=4192812/4192956
[pid=22217] ppid=22212 vsize=10480 CPUtime=0.09
/proc/22217/stat : 22217 (solver) R 22212 22217 21237 0 -1 4194304 1709 0 0 0 9 0 0 0 18 0 1 0 163363657 10731520 1677 18446744073709551615 134512640 134893233 4294956656 18446744073709551615 4156055944 0 0 4096 0 0 0 0 17 1 0 0
/proc/22217/statm: 2620 1677 716 92 0 964 0
Current children cumulated CPU time (s) 0.09
Current children cumulated vsize (KiB) 10480

Child status: 0
Real time (s): 0.517533
CPU time (s): 0.511921
CPU user time (s): 0.464929
CPU system time (s): 0.046992
CPU usage (%): 98.9156
Max. virtual memory (cumulated for all children) (KiB): 45596

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

runsolver used 0.005999 s user time and 0.004999 s system time

The end

Launcher Data (download as text)

Begin job on node48 on Sun Jan  7 06:00:50 UTC 2007


IDJOB= 201765
IDBENCH= 3782
FILE ID= node48/201765-1168149649

PBS_JOBID= 3478416

Free space on /tmp= 66558 MiB

BENCH NAME= HOME/pub/bench/CPAI06/rlfap/rlfapScens/scen2.xml
COMMAND LINE= /tmp/evaluation/201765-1168149649/tramontane/bin/solver /tmp/evaluation/201765-1168149649/unknown.xml -res geom -f 3 -v 1
RUNSOLVER COMMAND LINE= runsolver  --timestamp  -w ROOT/results/node48/watcher-201765-1168149649 -o ROOT/results/node48/solver-201765-1168149649 -C 1800 -M 900  /tmp/evaluation/201765-1168149649/tramontane/bin/solver /tmp/evaluation/201765-1168149649/unknown.xml -res geom -f 3 -v 1

META MD5SUM SOLVER= cb80ed4ac975bdc0101f830a5b1b8f77
MD5SUM BENCH=  6fd929da3fdebf81252e0d9d01639132

RANDOM SEED= 37184792

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.218
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.218
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:       1250864 kB
Buffers:         52556 kB
Cached:         655868 kB
SwapCached:          0 kB
Active:         246844 kB
Inactive:       481824 kB
HighTotal:           0 kB
HighFree:            0 kB
LowTotal:      2055920 kB
LowFree:       1250864 kB
SwapTotal:     4192956 kB
SwapFree:      4192812 kB
Dirty:            6420 kB
Writeback:           0 kB
Mapped:          30420 kB
Slab:            62120 kB
Committed_AS:  3401284 kB
PageTables:       1584 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= 66558 MiB



End job on node48 on Sun Jan  7 06:00:50 UTC 2007