aboutsummaryrefslogtreecommitdiffstats
path: root/configs
diff options
context:
space:
mode:
authormurf <murf@f38db490-d61c-443f-a65b-d21fe96a405b>2007-11-26 16:24:27 +0000
committermurf <murf@f38db490-d61c-443f-a65b-d21fe96a405b>2007-11-26 16:24:27 +0000
commit4f8e82fa2bbb0f9fad7fba8dda4c1192bccb7a39 (patch)
tree092a70555fdce2065649b08f3b40615be54641cd /configs
parent60d6d5e6e4d72c27e03a0ea55a52821821a66972 (diff)
Thanks to pnlarsson for noting the spelling error in the cli commands. Also, added some verbage about the new algorithm to CHANGES.
git-svn-id: http://svn.digium.com/svn/asterisk/trunk@89583 f38db490-d61c-443f-a65b-d21fe96a405b
Diffstat (limited to 'configs')
-rw-r--r--configs/extensions.conf.sample23
1 files changed, 18 insertions, 5 deletions
diff --git a/configs/extensions.conf.sample b/configs/extensions.conf.sample
index a5d992de1..b7a7445a0 100644
--- a/configs/extensions.conf.sample
+++ b/configs/extensions.conf.sample
@@ -36,20 +36,33 @@ writeprotect=no
;
;autofallthrough=no
;
-; By default, the old pattern matcher is used.
-
+;
+;
; If extenpatternmatchnew is set (true, yes, etc), then a new algorithm that uses
; a Trie to find the best matching pattern is used. In dialplans
; with more than about 20-40 extensions in a single context, this
; new algorithm can provide a noticeable speedup.
+; With 50 extensions, the speedup is 1.32x
+; with 88 extensions, the speedup is 2.23x
+; with 138 extensions, the speedup is 3.44x
+; with 238 extensions, the speedup is 5.8x
+; with 438 extensions, the speedup is 10.4x
; With 1000 extensions, the speedup is ~25x
; with 10,000 extensions, the speedup is 374x
-; Basically, the new algorithm provides a fairly flat response
+; Basically, the new algorithm provides a flat response
; time, no matter the number of extensions.
;
+; By default, the old pattern matcher is used.
+;
+; ****This is a new feature! *********************
; The new pattern matcher is for the brave, the bold, and
-; the desperate. If you have large dialplans, and/or high
-; call volume, you might consider setting this value to "yes" !!
+; the desperate. If you have large dialplans (more than about 50 extensions
+; in a context), and/or high call volume, you might consider setting
+; this value to "yes" !!
+; Please, if you try this out, and are forced to return to the
+; old pattern matcher, please report your reasons in a bug report
+; on bugs.digium.com. We have made good progress in providing something
+; compatible with the old matcher; help us finish the job!
;
; This value can be switched at runtime using the cli command "dialplan set extenpatternmatchnew true"
; or "dialplan set extenpatternmatchnew false", so you can experiment to your hearts content.