asterisk users - Jun 2005 - Management: Reload performace & Realtime performance ?

Hello,

I am interested in some management-performance issues:

1st Scenario:

A management tool (for example a webbased one) has the following process:

- write in database
- read with script (for example perl) data from db and write conf files
- reload asterisk

I was reading around in the mailing lists and people say reloading is 
stable. Now this tool has to manage 1000 clients so the conf files are 
quite big and reloading needs some time. What happens if a call comes in 
during that reload time ?
How is the performance in general of the process described above 
(assumed the used hardware is not under- and not overdimensioned), can 
such a tool easily handle 1000 clients ?
Does somebody use a similar tool with many clients ?

2nd Scenario

A management tool has the following process:

- write in database
- asterisk reads with realtime the conf

Somewhere in the mailing lists someone said that the realtime uses many 
database queries. If there are also 1000 clients to manage, this should 
lead to lots of database queries.
And again the questions, how is the performance in general of the 
realtime process (again normal hardware assumed) ? Can realtime handle 
1000 clients ?
Does somebody use it with lots of clients ?

Thanks in advance for the answers.

Best regards,
Ren?

> 
> I was reading around in the mailing lists and people say reloading is
> stable. Now this tool has to manage 1000 clients so the conf files are
> quite big and reloading needs some time. What happens if a call comes in
> during that reload time ?
> How is the performance in general of the process described above
> (assumed the used hardware is not under- and not overdimensioned), can
> such a tool easily handle 1000 clients ?
> Does somebody use a similar tool with many clients ?
This really depends on your usage patterns and a lot of other things
like what database you are using and how it is configured, etc..   You
probably need to list a lot more details about what it is you are
trying to do before you will get an answer.

 I haven't had the time to test what happens when you reload a large
static database, but I'm guessing it would load everything from the
database first, then when it replaces what's in memory it only takes a
second or so.
> 
> Somewhere in the mailing lists someone said that the realtime uses many
> database queries. If there are also 1000 clients to manage, this should
> lead to lots of database queries.
That's only for the realtime extensions.

Chris

On Thu, Jun 23, 2005 at 02:57:36PM +0200, Ren? Ott
wrote:
> Hello,
> 
> I am interested in some management-performance issues:
> 
> 1st Scenario:
> 
> A management tool (for example a webbased one) has the following process:
> 
> - write in database
> - read with script (for example perl) data from db and write conf files
> - reload asterisk
A full reload? You can, e.g, reload extension and sip peers.

What can't you reload without a full reload?
(e.g.: IAX in 1.0)

Is it applicable to read current configuration through the management
interface, "diff" it from the config files, and "apply a
diff" through
the manager interface without a full reload?

Obviously it takes much work to get this right. But is it even
theoretically possible today?

-- 
Tzafrir Cohen         | tzafrir@jbr.cohens.org.il | VIM is
http://tzafrir.org.il |                           | a Mutt's  
tzafrir@cohens.org.il |                           |  best
ICQ# 16849755         |                           | friend