blanchae
Guru
- Joined
- Mar 12, 2008
- Messages
- 1,910
- Reaction score
- 9
This is a continuation from the initial stress testing performed in this thread. This thread discusses the load placed on a PiaF server with the FOP2 (flash operator panel version 2) installed. Specifically it discusses how FOP2 interacts with the Asterisk Manager Interface AMI and the issues surrounding the AMI interface.
The developer of FOP2, Asternic responded to the initial performance query:
The AMI is MORE verbose than the logging that we saw in the initial stress testing! The AMI sends out many "event" notices based on a single request from FOP2. Asternic has described a method of reducing the number of AMI event notices by using the AMI eventfilter.
The developer of FOP2, Asternic responded to the initial performance query:
FOP(1) uses a lot more cpu than FOP2. You can quickly verify that by
running both and checking the cpu time used by each one. The main reason
for that is that FOP(1) supports REGEX based channel matching, and Regex
are expensive to match on every AMI event you get.
FOP2 is much more nice to cpu because of the above. However, as you have
seen in your stress tests, it analyzes every AMI event that is
broadcasted. AMI is *much* more verbose than the CLI or probably event
the full log.
So, if you run hundreds of calls per minute, and you pass them via the
humongous FreePBX dialplan, AMI will generate hundreds of events to be
processed by external applications, like fop/fop2. Take into account
that each priority in a dialplan generates an event, and depending the
application you run in that priority, it might generate *another* event.
You can run fop2_server in debug level 1 to see the events being
broadcasted by asterisk and received by fop2. "fop2_server --debuglevel
1" or use option "-X 1"
If you plan to run 50 calls per seconds on an asterisk box, then you are
probably not using it as a regular PBX, so fop2 is not to be installed
there. Even if you plan to do that, you should consider on installing
all monitoring/reporting tools on a separate box.
There are ways to optimize the manager to reduce the load on the
machine, they are described in a blog post here:
http://www.fop2.com/blog/make-fop2-snappier-using-ami-eventfilter
The AMI is MORE verbose than the logging that we saw in the initial stress testing! The AMI sends out many "event" notices based on a single request from FOP2. Asternic has described a method of reducing the number of AMI event notices by using the AMI eventfilter.
Last edited by a moderator: