Many businesses who are adopting VoIP Software PBX Systems are always looking for a way to cut down costs. That’s where the Intel Atom N270 comes in the picture, which is designed to deliver performance with minimal power usage. In addition many of our partners have requested the ability to put together a low cost dedicated server based on an Intel Atom. The Intel Atom N270 can be found in many low cost servers and these can be used to create a low cost dedicated 3CX server. In this post we take a look at such a device, the Allnet FW8888 and run some bench mark tests against it to see how it performs.
Allnet FW8888 Hardware Specifications:
- CPU: Intel ATOM N270, 1.60 GHz Dual Core (Hyperthreading)
- North Bridge: Intel 82945GSE, MCH- North bridge Intel 82945GSE, MCH-North bridge
- South Bridge: Intel 82801GBM, ICH 7M- South bridge Intel 82801GBM, ICH-7M South bridge
- Expansion: 1xPCI Expansion Card
- RAM: 2x 1GB DDR
- Storage: 1x IDE 1x IDE 1x CF 1x CF 2x SATA / Raid 2x SATA / Raid
- 6 Gigabit LAN controllers: (Yes 6)
- 1x -Intel 83572EI PCIe GbE Controller miniGBIC (SFP)
- 3x Intel 82574L PCIe GbE Controller RJ45
- 2x Intel 825741 PCI GbE Controller RJ45
- Housing: 19″ Rack / 1HE 19 “Rack / 1U
- HDD: 250GB SATA
- PSU: 230V / ATX / 250W Max
We will be focusing on the Atom’s functionality with 3CX, but before doing that, here’s some general information on the Atom’s general performance shown in the Windows Experience Index just to give a quick view of how Windows 7 Enterprise edition rates this device.
Windows 7 Enterprise 32 bit was used instead of Windows XP embedded with which the device shipped. The newer Windows 7 OS is more performant and more flexible because it offers remote access via RDP.
Another thing we did before the start of the test was disable UAC. Reason for this was because every time elevation was required, this spiked up the CPU. Another option is to enable the Administrator account.
CPU usage (IDLE state)
The Idle CPU usage of the Allnet FW8888 with 3CX PBX installed using IIS on Windows 7 Enterprise x86 was fluctuating around 94%-97%.
All 3CX Services at this stage consumed 34Mb of memory. Ultidev Cassini consumed 10Mb of Memory.
Under normal operation this processor requires only 34 watts. Under full load the device requires 55 watts. In standby mode, the Allnet uses just 1 watt of power.
We have made some benchmarks to see the performance of 3CX on this Atom Processor.
Database messaging/updating Test
First we started testing the management console to see the database processing speed and the communication between the 3CX Configuration service and displaying the end result to Management console/Web interface. To see this we created 1000 extensions, and after deleted them again. This process involves a lot of updates to and from the 3CX Database core informing higher application layers of the changes.
Creating and Deleting 1000 Extensions took 80 seconds.
Registrations involve a high load of processing on any sip server even though we take simple registrations for granted. Registrations involve layers of authentication, re-registrations, keep alives, persistent storage cache, caching of these registrations, registration expiry timeouts etc etc. We were pretty impressed to see that this ATOM processor can handle 1000 extensions re-registering every 3600 seconds. We have increased registrations to 1200 seconds and the CPU spiked badly so it is recommended that the registration interval is set to 3600 seconds.
This benchmark test includes stress testing of Queue Calls, Voip Provider Calls and Normal Extension to Extension calls.
The script was generated as follows – X number of calls were initiated, remained connected passing audio directly between them for 120 seconds and disconnecting all calls at random with an inter-call delay of 10-40 seconds.
Queue Call Performance:
Normal Calls Extension to Extension
Moving on to Normal calls, amazingly enough the Atom managed to reach a staggering 500 simultaneous calls with minimal jittering whilst it could easily do 400 Simultaneous calls with no jitters at all.
NOTE: Features like call recording were not active during these tests and all calls used Re-Invites and Replaces to construct SDP negotiation directly between them. With Recording on, the maximum amount of calls reached were 30 simultaneous calls which is still very impressive.
Incoming/Outgoing calls via a VoIP Provider
Next up are Voip Provider calls. Voip Provider calls are somewhat lightweight and do not take much PBX CPU, the following tests simulated external calls. Due to bandwidth limitations, the calls were restricted to just 20. Also we must keep in mind that VoIP Provider calls are bound to the 3CX Media Server to avoid routing problems and NAT issues. Like this the risk of getting 1 way audio is decreased to 2% only.
20 Simultaneous calls via a VoIP Provider produced no jitters, CPU usage in total was 19% and the total simultaneous calls hit 40.
Theoretically, you would need to make around 90 VoIP Provider calls before the Atom CPU cannot be able to handle the stress anymore and jitters and broken audio symptoms will appear.
Overall, the Allnet FW8888 gave us very good results. The Atom is no match for the Core2Duo however it can still impress.
We can recommend servers with Atom processors for businesses that have a up to 24 Simultaneous Call License.
Please note that there are many types of Atom processors. The older, slower models are NOT suitable!