Can someone tell me the size (or any other) limitations for the extensions.conf? We have managed to keep our file pretty small thanks to AGI but we are about to setup a bunch of call restrictions based on area and country code. One line per area code in the US alone adds a LOT of text to this file. Is it a bad thing to have 5 or 6000 lines of text in your extensions.conf on a production system? Will it affect the performance?
trixter aka Bret McDanel
2006-Jun-03 14:35 UTC
[Asterisk-Users] Size limitations of extensions.conf
On Sat, 2006-06-03 at 16:03 -0500, voiplist wrote:> Can someone tell me the size (or any other) limitations for the extensions.conf? > > We have managed to keep our file pretty small thanks to AGI but we are > about to setup a bunch of call restrictions based on area and country > code. > > One line per area code in the US alone adds a LOT of text to this file. > > Is it a bad thing to have 5 or 6000 lines of text in your > extensions.conf on a production system? > > Will it affect the performance?it adds memory and increases load time, it also causes asterisk to walk a longer tree each time it has to do something in that context at least rather than not ... -- Trixter http://www.0xdecafbad.com Bret McDanel Belfast IE +44 28 9099 6461 DE +49 801 777 555 3402 Utrecht NL +31 306 553058 US WA +1 360 207 0479 US NY +1 516 687 5200 FreeWorldDialup: 635378 http://www.trxtel.com we pay you to terminate calls with us! -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 189 bytes Desc: This is a digitally signed message part Url : http://lists.digium.com/pipermail/asterisk-users/attachments/20060603/ee00abb2/attachment.pgp
Brent Torrenga
2006-Jun-05 07:10 UTC
[Asterisk-Users] RE: Size limitations of extensions.conf
If you need to do a couple differing operations on a list of many area/country codes, then you may consider using the database to let the dial plan choose what to do, rather than go through so many extensions. I mention this to keep your extensions.conf easier to read, not because I know whether or not a long extensions.conf will break things...> Can someone tell me the size (or any other) limitations for theextensions.conf?> > We have managed to keep our file pretty small thanks to AGI but we are > about to setup a bunch of call restrictions based on area and country > code. > > One line per area code in the US alone adds a LOT of text to this file. > > Is it a bad thing to have 5 or 6000 lines of text in your > extensions.conf on a production system? > > Will it affect the performance?Sincerely, Brent A. Torrenga Torrenga Engineering, Inc. 907 Ridge Road Munster, Indiana 46321-1771 tel:+1 219 836 8918 x325 fax:+1 219 836 1138 email:brent.torrenga@torrenga.com web:www.torrenga.com
Moises Silva
2006-Jun-05 09:24 UTC
[Asterisk-Users] RE: Size limitations of extensions.conf
Asterisk support the concept of "configuration engine", this means that you can write a configuration engine to get the data from anywhere. The default configuration engine is "text_file_engine", that reads the configuration from text files. This engine does not have any limit in the code, so the only limit is the performance hit of starting or reloading. Actually some limits exists for the size of context names, nested includes etc, but no for number of lines. Why dont use database engine? instead of large files? Regards On 6/5/06, Brent Torrenga <lists@torrenga.com> wrote:> If you need to do a couple differing operations on a list of many > area/country codes, then you may consider using the database to let the dial > plan choose what to do, rather than go through so many extensions. > > I mention this to keep your extensions.conf easier to read, not because I > know whether or not a long extensions.conf will break things... > > > Can someone tell me the size (or any other) limitations for the > extensions.conf? > > > > We have managed to keep our file pretty small thanks to AGI but we are > > about to setup a bunch of call restrictions based on area and country > > code. > > > > One line per area code in the US alone adds a LOT of text to this file. > > > > Is it a bad thing to have 5 or 6000 lines of text in your > > extensions.conf on a production system? > > > > Will it affect the performance? > > > Sincerely, > > Brent A. Torrenga > > Torrenga Engineering, Inc. > 907 Ridge Road > Munster, Indiana 46321-1771 > > tel:+1 219 836 8918 x325 > fax:+1 219 836 1138 > email:brent.torrenga@torrenga.com > web:www.torrenga.com > > _______________________________________________ > --Bandwidth and Colocation provided by Easynews.com -- > > Asterisk-Users mailing list > To UNSUBSCRIBE or update options visit: > http://lists.digium.com/mailman/listinfo/asterisk-users >-- "Su nombre es GNU/Linux, no solamente Linux, mas info en http://www.gnu.org"
Douglas Garstang
2006-Jun-05 09:52 UTC
[Asterisk-Users] RE: Size limitations of extensions.conf
If by database you are referring to an external database, such as MySQL, you have to address failover, redundancy and performance issues if you go in that direction.> -----Original Message----- > From: Moises Silva [mailto:moises.silva@gmail.com] > Sent: Monday, June 05, 2006 10:24 AM > To: Asterisk Users Mailing List - Non-Commercial Discussion > Subject: Re: [Asterisk-Users] RE: Size limitations of extensions.conf > > > Asterisk support the concept of "configuration engine", this means > that you can write a configuration engine to get the data from > anywhere. The default configuration engine is "text_file_engine", that > reads the configuration from text files. This engine does not have any > limit in the code, so the only limit is the performance hit of > starting or reloading. Actually some limits exists for the size of > context names, nested includes etc, but no for number of lines. > > Why dont use database engine? instead of large files? > > Regards > > > > > On 6/5/06, Brent Torrenga <lists@torrenga.com> wrote: > > If you need to do a couple differing operations on a list of many > > area/country codes, then you may consider using the > database to let the dial > > plan choose what to do, rather than go through so many extensions. > > > > I mention this to keep your extensions.conf easier to read, > not because I > > know whether or not a long extensions.conf will break things... > > > > > Can someone tell me the size (or any other) limitations for the > > extensions.conf? > > > > > > We have managed to keep our file pretty small thanks to > AGI but we are > > > about to setup a bunch of call restrictions based on area > and country > > > code. > > > > > > One line per area code in the US alone adds a LOT of text > to this file. > > > > > > Is it a bad thing to have 5 or 6000 lines of text in your > > > extensions.conf on a production system? > > > > > > Will it affect the performance? > > > > > > Sincerely, > > > > Brent A. Torrenga > > > > Torrenga Engineering, Inc. > > 907 Ridge Road > > Munster, Indiana 46321-1771 > > > > tel:+1 219 836 8918 x325 > > fax:+1 219 836 1138 > > email:brent.torrenga@torrenga.com > > web:www.torrenga.com > > > > _______________________________________________ > > --Bandwidth and Colocation provided by Easynews.com -- > > > > Asterisk-Users mailing list > > To UNSUBSCRIBE or update options visit: > > http://lists.digium.com/mailman/listinfo/asterisk-users > > > > > -- > "Su nombre es GNU/Linux, no solamente Linux, mas info enhttp://www.gnu.org" _______________________________________________ --Bandwidth and Colocation provided by Easynews.com -- Asterisk-Users mailing list To UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-users