Trace number 1075612

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
Mistral-prime 1.313SAT 0.657899 0.665504

DiagnosticValue
ASSIGNMENTS124
CHECKS169335

General information on the benchmark

Namecsp/ogdHerald/
normalized-crossword-m1-ogd-19-05.xml
MD5SUM004360dc4ee08fb7f6c35dfdfdd00b76
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.590909
Satisfiable
(Un)Satisfiability was proved
Number of variables291
Number of constraints2544
Maximum constraint arity32
Maximum domain size26
Number of constraints which are defined in extension126
Number of constraints which are defined in intension2418
Global constraints used (with number of constraints)

Solver Data (download as text)

0.18/0.21	c mistral-prime version 1.313
0.58/0.62	s SATISFIABLE
0.58/0.62	v 5 0 13 18 1 0 2 4 2 7 14 3 0 17 3 0 1 0 19 10 0 13 0 15 8 0 5 8 3 4 4 0 1 14 8 4 3 0 12 7 0 11 11 15 0 17 0 0 4 18 2 7 13 4 0 8 4 4 0 17 11 10 0 24 18 4 17 18 1 4 17 6 4 14 8 18 4 1 17 8 18 10 0 3 0 1 8 19 18 4 17 0 13 17 4 12 0 13 4 4 0 4 17 0 18 0 20 19 0 11 15 4 4 13 13 0 4 2 7 0 8 17 0 13 8 4 19 18 19 17 0 18 0 8 3 0 3 4 17 13 0 2 20 4 8 11 11 4 19 19 14 8 18 4 18 0 23 0 8 0 3 0 6 4 3 0 1 0 0 8 11 0 11 5 0 12 0 13 0 0 17 0 10 18 13 14 1 0 2 17 0 19 4 17 0 14 7 4 4 2 17 20 4 19 4 12 15 4 14 20 17 3 8 18 18 0 8 13 19 2 7 0 12 0 18 18 4 13 13 4 17 0 8 0 15 18 24 0 3 0 15 19 0 8 1 0 3 0 15 8 5 0 11 4 18 4 4 0 20 23 11 0 2 10 0 13 0 17 11 0 2 18 17 0 3 0 4 18 0 20 11 4 13 19 4 20 7 0 11 4 18
0.58/0.62	d CHECKS 169335
0.58/0.62	d ASSIGNMENTS 124

Verifier Data (download as text)

OK

Watcher Data (download as text)

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

command line: /home/evaluation/evaluation/pub/bin/runsolver --timestamp -w /tmp/evaluation-result-1075612-1215181260/watcher-1075612-1215181260 -o /tmp/evaluation-result-1075612-1215181260/solver-1075612-1215181260 -C 1800 -W 2200 -M 900 --output-limit 1,15 HOME/xsolve HOME/instance-1075612-1215181260.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): 2200 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
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: 2.39 2.15 2.05 4/82 10834
/proc/meminfo: memFree=1016904/2055920 swapFree=4179968/4192956
[pid=10834] ppid=10832 vsize=18572 CPUtime=0
/proc/10834/stat : 10834 (runsolver) R 10832 10834 8814 0 -1 4194368 15 0 0 0 0 0 0 0 18 0 1 0 1997100832 19017728 292 996147200 4194304 4296836 548682068496 18446744073709551615 262910045479 0 0 4096 24578 0 0 0 17 1 0 0
/proc/10834/statm: 4643 292 257 25 0 2626 0

[startup+0.0745579 s]
/proc/loadavg: 2.39 2.15 2.05 4/82 10834
/proc/meminfo: memFree=1016904/2055920 swapFree=4179968/4192956
[pid=10834] ppid=10832 vsize=5724 CPUtime=0.06
/proc/10834/stat : 10834 (xsolve) R 10832 10834 8814 0 -1 4194304 714 0 0 0 6 0 0 0 18 0 1 0 1997100832 5861376 680 996147200 134512640 135237403 4294956240 18446744073709551615 134579559 0 0 4096 0 0 0 0 17 0 0 0
/proc/10834/statm: 1431 680 354 176 0 335 0
Current children cumulated CPU time (s) 0.06
Current children cumulated vsize (KiB) 5724

[startup+0.102553 s]
/proc/loadavg: 2.39 2.15 2.05 4/82 10834
/proc/meminfo: memFree=1016904/2055920 swapFree=4179968/4192956
[pid=10834] ppid=10832 vsize=6120 CPUtime=0.09
/proc/10834/stat : 10834 (xsolve) R 10832 10834 8814 0 -1 4194304 821 0 0 0 9 0 0 0 18 0 1 0 1997100832 6266880 787 996147200 134512640 135237403 4294956240 18446744073709551615 134579537 0 0 4096 0 0 0 0 17 0 0 0
/proc/10834/statm: 1530 787 354 176 0 434 0
Current children cumulated CPU time (s) 0.09
Current children cumulated vsize (KiB) 6120

[startup+0.30259 s]
/proc/loadavg: 2.39 2.15 2.05 4/82 10834
/proc/meminfo: memFree=1016904/2055920 swapFree=4179968/4192956
[pid=10834] ppid=10832 vsize=10520 CPUtime=0.29
/proc/10834/stat : 10834 (xsolve) R 10832 10834 8814 0 -1 4194304 1886 0 0 0 28 1 0 0 19 0 1 0 1997100832 10772480 1852 996147200 134512640 135237403 4294956240 18446744073709551615 134998982 0 0 4096 0 0 0 0 17 0 0 0
/proc/10834/statm: 2630 1852 377 176 0 1534 0
Current children cumulated CPU time (s) 0.29
Current children cumulated vsize (KiB) 10520

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

[startup+0.502611 s]
/proc/loadavg: 2.39 2.15 2.05 4/82 10834
/proc/meminfo: memFree=1016904/2055920 swapFree=4179968/4192956
[pid=10834] ppid=10832 vsize=19316 CPUtime=0.48
/proc/10834/stat : 10834 (xsolve) R 10832 10834 8814 0 -1 4194304 4042 0 0 0 46 2 0 0 21 0 1 0 1997100832 19779584 4008 996147200 134512640 135237403 4294956240 18446744073709551615 134819592 0 0 4096 0 0 0 0 17 0 0 0
/proc/10834/statm: 4829 4008 408 176 0 3733 0
Current children cumulated CPU time (s) 0.48
Current children cumulated vsize (KiB) 19316

[startup+0.602627 s]
/proc/loadavg: 2.39 2.15 2.05 4/82 10834
/proc/meminfo: memFree=1016904/2055920 swapFree=4179968/4192956
[pid=10834] ppid=10832 vsize=19388 CPUtime=0.58
/proc/10834/stat : 10834 (xsolve) R 10832 10834 8814 0 -1 4194304 4076 0 0 0 56 2 0 0 22 0 1 0 1997100832 19853312 4042 996147200 134512640 135237403 4294956240 18446744073709551615 134797832 0 0 4096 0 0 0 0 17 0 0 0
/proc/10834/statm: 4847 4042 408 176 0 3751 0
Current children cumulated CPU time (s) 0.58
Current children cumulated vsize (KiB) 19388

Child status: 0
Real time (s): 0.665504
CPU time (s): 0.657899
CPU user time (s): 0.628904
CPU system time (s): 0.028995
CPU usage (%): 98.8573
Max. virtual memory (cumulated for all children) (KiB): 19388

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

runsolver used 0.002999 second user time and 0.004999 second system time

The end

Launcher Data (download as text)

Begin job on node11 at 2008-07-04 16:21:00
IDJOB=1075612
IDBENCH=56528
IDSOLVER=358
FILE ID=node11/1075612-1215181260
PBS_JOBID= 7881515
Free space on /tmp= 66548 MiB

SOLVER NAME= Mistral-prime 1.313
BENCH NAME= CPAI08/csp/ogdHerald/normalized-crossword-m1-ogd-19-05.xml
COMMAND LINE= HOME/xsolve BENCHNAME 
RUNSOLVER COMMAND LINE= /home/evaluation/evaluation/pub/bin/runsolver --timestamp -w /tmp/evaluation-result-1075612-1215181260/watcher-1075612-1215181260 -o /tmp/evaluation-result-1075612-1215181260/solver-1075612-1215181260 -C 1800 -W 2200 -M 900 --output-limit 1,15  HOME/xsolve HOME/instance-1075612-1215181260.xml 

TIME LIMIT= 1800 seconds
MEMORY LIMIT= 900 MiB

MD5SUM BENCH= 004360dc4ee08fb7f6c35dfdfdd00b76
RANDOM SEED=1021677264

node11.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.224
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.224
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:       1017384 kB
Buffers:         44552 kB
Cached:         118276 kB
SwapCached:       7036 kB
Active:         920044 kB
Inactive:        62508 kB
HighTotal:           0 kB
HighFree:            0 kB
LowTotal:      2055920 kB
LowFree:       1017384 kB
SwapTotal:     4192956 kB
SwapFree:      4179968 kB
Dirty:            2496 kB
Writeback:           0 kB
Mapped:         820492 kB
Slab:            39528 kB
Committed_AS:  4061720 kB
PageTables:       3456 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= 66548 MiB
End job on node11 at 2008-07-04 16:21:01