PhonePad 5 Server Resource Tests
Copyright © 1995 - 2021 Cybercom Software. All rights
reserved. In business since 1995.
We ran some tests to check PhonePad 5 Server’s resource usage
under different scenarios. These are the results of these tests.
In all of these tests, the users were all logged in simultaneously,
ie. at exactly the same time. This would rarely happen in the real
The images below show the CPU usage when the server is idling
with the indicated number of users connected, as well as the
amount of memory usage. Naturally, the more users that are
connected the higher the memory usage.
The “blips” or bursts of activity in the graph are from the
simultaneous logins. Normally users wouldn’t all login at exactly
the same time and so the amount of CPU usage would be a lot
lower when logins occur.
Test 1 - 10 Users
As you can see, memory usage is quite low, and CPU usage is
Test 2 - 50 Users
Memory usage is still low, and CPU usage (after everyone logging
in at once) returns to very low usage.
Test 3 - 100 Users
Memory usage has doubled from the previous test, with
double the number of users. After the initial burst of
activity from all of the simultaneous logins, the server has
settled down to a gentle idle.
Test 4 - 300 Users
We wouldn’t recommend having 300 users connected to the one
PhonePad Server (multiple servers should be used) but we just
wanted to see what would happen.
Memory usage has now passed 1GB, but the CPU usage after all
of the logins is still very low.
Test 5 - 500 Users
One more test to see if we can break the PhonePad Server.
Memory usage now is quite high, but we expected that given that
there are 500 users logged in. Still, the CPU usage is very low
with all of those connections. Mind you, the users aren’t actually
doing anything so the system is just idling.
The PhonePad 5 Server can handle a large number of
connections, although we wouldn’t advise more than 100
users per server instance.
Memory usage is quite reasonable and CPU usage is very
low at idle, which is what we would expect.
Modules were cached in these tests (the recommended setting).
Performance Boost was not enabled.