I've got Asterisk loading 100,000+ extensions in extensions.conf. This process is taking a little upwards of 10 minutes to complete on each of my dual 3.2Ghz HP DL380 with SuSE Linux Enterprise 8 boxes. Although asterisk creates child processes, it appears that it is only using a single processor to parse extensions.conf. I've turned off Hyper Threading on the servers which has increased the extensions.conf parsing speed, but not by more than a couple minutes. Is this a bug, or simply the way Asterisk works during startup? If it is the way Asterisk works during startup, would it be safe to say that once started - that the child processes would function? Thanks, - Darren
<quote who="Darren Sessions">> I've got Asterisk loading 100,000+ extensions in extensions.conf. This > process is taking a little upwards of 10 minutes to complete on each of my > dual 3.2Ghz HP DL380 with SuSE Linux Enterprise 8 boxes. > > Although asterisk creates child processes, it appears that it is only using > a single processor to parse extensions.conf. I've turned off Hyper Threading > on the servers which has increased the extensions.conf parsing speed, but > not by more than a couple minutes. > > Is this a bug, or simply the way Asterisk works during startup? If it is the > way Asterisk works during startup, would it be safe to say that once started > - that the child processes would function?This behaviour is just for parsing "*.conf" files. You may want to put the extensions into a database and use an AGI script to perform extension routing. (Though, I think it would bypass CDR.) -- END OF LINE -MCP