Trace number 2074904

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. The first timestamp (if present) is estimated CPU time. The last timestamp is wall clock 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
pcs 0.3.2SAT 0.196969 0.20395

DiagnosticValue
ASSIGNMENTS20

General information on the benchmark

Namecsp/wordsPuzzle/
normalized-crossword-m1-words-puzzle11.xml
MD5SUMece4d83d6a4e34acc08dc67ab6a0ddb9
Bench CategoryN-ARY-INT (n-ary constraints in intension)
Best result obtained on this benchmarkSAT
Best CPU time to get the best result obtained on this benchmark0.103983
Satisfiable
(Un)Satisfiability was proved
Number of variables38
Number of constraints47
Maximum constraint arity14
Maximum domain size26
Number of constraints which are defined in extension18
Number of constraints which are defined in intension29
Global constraints used (with number of constraints)

Solver Data 

0.00/0.02	c small-domain mode
0.00/0.04	c Seed is 1106098480
0.00/0.04	c Constructing HOME/instance-2074904-1247712502.xml  with 407 constraints
0.00/0.10	c Solving 20 backtracks 1 restarts
0.18/0.20	s SATISFIABLE
0.18/0.20	c V0=5, V1=14, V2=4, V3=18, V4=2, V5=14, V6=17, V7=21, V8=20, V9=18, V10=15, V11=0, V12=17, V13=0, V14=19, V15=4, V16=4, V17=17, V18=6, V19=18, V20=20, V21=4, V22=4, V23=21, V24=0, V25=8, V26=17, V27=10, V28=17, V29=4, V30=21, V31=8, V32=21, V33=4, V34=17, V35=4, V36=13, V37=4, 
0.18/0.20	v 5 14 4 18 2 14 17 21 20 18 15 0 17 0 19 4 4 17 6 18 20 4 4 21 0 8 17 10 17 4 21 8 21 4 17 4 13 4 
0.18/0.20	d ASSIGNMENTS 20

Verifier Data 

OK

Watcher Data 

runsolver version 3.2.9 (svn:492) (c) roussel@cril.univ-artois.fr

command line: BIN/runsolver --timestamp -w /tmp/evaluation-result-2074904-1247712502/watcher-2074904-1247712502 -o /tmp/evaluation-result-2074904-1247712502/solver-2074904-1247712502 -C 1800 -W 2000 -M 900 HOME/pcssolve -s 1106098480 HOME/instance-2074904-1247712502.xml 

Enforcing CPUTime limit (soft limit, will send SIGTERM then SIGKILL): 1800 seconds
Enforcing CPUTime limit (hard limit, will send SIGXCPU): 1830 seconds
Enforcing wall clock limit (soft limit, will send SIGTERM then SIGKILL): 2000 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


[startup+0 s]
/proc/loadavg: 2.29 2.10 2.06 3/82 16825
/proc/meminfo: memFree=969944/2055920 swapFree=4192812/4192956
[pid=16825] ppid=16823 vsize=5356 CPUtime=0
/proc/16825/stat : 16825 (pcssolve) R 16823 16825 16386 0 -1 4194304 263 0 0 0 0 0 0 0 20 0 1 0 58314347 5484544 231 996147200 4194304 4889804 548682068800 18446744073709551615 4315763 0 0 4100 65536 0 0 0 17 1 0 0
/proc/16825/statm: 1339 231 193 169 0 50 0

[startup+0.10847 s]
/proc/loadavg: 2.29 2.10 2.06 3/82 16825
/proc/meminfo: memFree=969944/2055920 swapFree=4192812/4192956
[pid=16825] ppid=16823 vsize=5392 CPUtime=0.08
/proc/16825/stat : 16825 (pcs.small) R 16823 16825 16386 0 -1 4194304 1050 974 0 0 8 0 0 0 18 0 1 0 58314347 5521408 658 996147200 134512640 135095119 4294956304 18446744073709551615 134927253 0 0 4096 0 0 0 0 17 1 0 0
/proc/16825/statm: 1348 658 401 142 0 302 0
Current children cumulated CPU time (s) 0.08
Current children cumulated vsize (KiB) 5392

[startup+0.201491 s]
/proc/loadavg: 2.29 2.10 2.06 3/82 16825
/proc/meminfo: memFree=969944/2055920 swapFree=4192812/4192956
[pid=16825] ppid=16823 vsize=5392 CPUtime=0.18
/proc/16825/stat : 16825 (pcs.small) R 16823 16825 16386 0 -1 4194304 1050 974 0 0 18 0 0 0 18 0 1 0 58314347 5521408 658 996147200 134512640 135095119 4294956304 18446744073709551615 134918185 0 0 4096 0 0 0 0 17 1 0 0
/proc/16825/statm: 1348 658 401 142 0 302 0
Current children cumulated CPU time (s) 0.18
Current children cumulated vsize (KiB) 5392

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

Child status: 0
Real time (s): 0.20395
CPU time (s): 0.196969
CPU user time (s): 0.186971
CPU system time (s): 0.009998
CPU usage (%): 96.5771
Max. virtual memory (cumulated for all children) (KiB): 5392

getrusage(RUSAGE_CHILDREN,...) data:
user time used= 0.186971
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= 2026
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= 15

runsolver used 0.003999 second user time and 0.004999 second system time

The end

Launcher Data 

Begin job on node37 at 2009-07-16 04:48:22
IDJOB=2074904
IDBENCH=56151
IDSOLVER=733
FILE ID=node37/2074904-1247712502
PBS_JOBID= 9521431
Free space on /tmp= 66396 MiB

SOLVER NAME= pcs 0.2
BENCH NAME= CPAI08/csp/wordsPuzzle/normalized-crossword-m1-words-puzzle11.xml
COMMAND LINE= HOME/pcssolve -s RANDOMSEED BENCHNAME
RUNSOLVER COMMAND LINE= BIN/runsolver --timestamp -w /tmp/evaluation-result-2074904-1247712502/watcher-2074904-1247712502 -o /tmp/evaluation-result-2074904-1247712502/solver-2074904-1247712502 -C 1800 -W 2000 -M 900  HOME/pcssolve -s 1106098480 HOME/instance-2074904-1247712502.xml

TIME LIMIT= 1800 seconds
MEMORY LIMIT= 900 MiB
MAX NB THREAD= 0

MD5SUM BENCH= ece4d83d6a4e34acc08dc67ab6a0ddb9
RANDOM SEED=1106098480

node37.alineos.net Linux 2.6.9-22.EL.rootsmp #1 SMP Mon Oct 3 08:59:52 CEST 2005

/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.260
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.260
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:        970488 kB
Buffers:         83848 kB
Cached:         413028 kB
SwapCached:          0 kB
Active:         674452 kB
Inactive:       322280 kB
HighTotal:           0 kB
HighFree:            0 kB
LowTotal:      2055920 kB
LowFree:        970488 kB
SwapTotal:     4192956 kB
SwapFree:      4192812 kB
Dirty:            3676 kB
Writeback:           0 kB
Mapped:         520316 kB
Slab:            73028 kB
Committed_AS:  1155796 kB
PageTables:       2756 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= 66396 MiB
End job on node37 at 2009-07-16 04:48:22