Recommended reading:
If you wish to protect your service against hardware failure and reach higher
availability of your Ozeki NG SMS Gateway software, we recommend you to try
our Ozeki Cluster software product.
Ozeki Cluster automatically moves any
service to another computer in case of a hardware failure. You can
download it from:
Ozeki Cluster Site
If you wish to find the optimal hardware configuration for your SMS
gateway system, you should have some information about the way Ozeki NG
SMS Gateway uses the computer resources. This guide gives you information
on this topic and provides hardware configuration examples and recommends
specific computer models for certain usage.
Introduction
The performance of Ozeki NG SMS gateway depends on the underlying computer
system. The software was designed to take advantage of large memory
and parallel processing capabilities. Ozeki NG SMS Gateway performs
significantly better on multi core and
multi processor systems. The software keeps most of the data that is
required for operation in memory. The hard disk access and the hard disk
performance is not the most critical part of the configuration. The most
important is to have a fast processor and large memory space.
System resource management
The core components of Ozeki NG SMS Gateway are:
Component
Resource demand
Service provider connections (e.g.: UCP connection to T-mobile,
SMPP to Vodafone)
CPU resources
Users and applications
(e.g.: A C# application or a web application who sends messages
over HTTP or a person (an office user) using an office client, such as Excel
SMS client)
CPU resources, Memory resources
Logging, reporting
HDD resources
Routing, resource management
CPU resources are used. (This
unit is responsible for distributing system resources among other components)
Concerning CPU resources, separate processing threads are used for each
service provider connection and each active user or application. As
the number of active threads increase the amount of CPU processing power consumed
is also increased. If you wish to serve a lot of users and you wish to have
a lot of service provider connections, get a powerful CPU or put more CPUs in
your server. (For optimal performance a thread pool is used to make sure inactive
users and inactive service provider connections do not take up system resources.)
Concerning memory resources, messages being processed or that are waiting
for
processing are stored in memory. The more memory you have the more messages can
be cached in memory which gives you better throughput. If you want to send or
receive a large number of messages you should have more RAM.
Large hard disk space and fast hard disk access is not the most crucial
part.
The software tries to do everything in memory. You should get a fast hard disk
if you want to configure detailed logging or you want to save messages to the
hard disk. For example if you setup an SQL to SMS gateway configuration, where
all messages that go through the system should be saved into a database, your
system will use the hard disk extensively. If you configure an HTTP to SMS
gateway system with low log level your system will not use the hard disk to
often.
Example system resource demand
Example #1: If you have many service provider connections, and
many users
accessing the SMS gateway directly, each sending a small number of messages,
your system will need fast CPU, medium RAM, low HDD.
Example #2: If you have a few service provider connections, one or two
applications connected to the SMS gateway directly, each application is sending
a large number of messages, your system will need medium CPU, large
RAM, low HDD.
Typical hardware configurations
The best method to select the appropriate hardware configuration is to calculate
the number of messages you need to send and receive and to determine the average
message throughput (message per minute MPM or message per second MPS). In the
following table we give you common hardware configurations.
Capacity
Hardware configuration
Recommended model
5 MPM - 30 MPM
(MPM = Message per minute)
CPU: Intel Pentium 4D, 3 Ghz (Dual core)
RAM: 2 GB RAM
HDD: 120 GB SATA
OS: 32 Bit
HP ProLiant ML110 G5
Dell PowerEdge SC440
1 MPS - 25 MPS
(MPS = Message per second)
CPU: Intel Xeon 3000, 2.33 Ghz (Dual core)
RAM: 4 GB RAM
HDD: 120 GB SATA
OS: 32 Bit
HP ProLiant DL145 G3
Dell PowerEdge 860
50 MPS - 200 MPS
(MPS = Message per second)
CPU: Intel Xeon 5000, 3 Ghz, (Quad core)
RAM: 16 GB RAM
HDD: 120 GB, SCSI (Raid 0 or Raid 5 is recommended)
OS: 64 Bit
