The hardware requirements depend on the usage or traffic PerfectApps will experience. In general, two points to consider are:
•Average or long-term load
•Burst or short-term load
The long-term load is the steady, daily usage that PerfectApps is subjected to. Average load rarely presents problems that cannot be addressed by gradually increasing the hardware capacity of the system.
The burst load is when an app or a report is subjected to very heavy usage within a short period of time. Burst load is less predictable and can lead to a slowdown in the system that can affect all users.
|
You build a survey app and then send it to 100,000 people at the same time. Predictably, a percentage of these people open the app soon after it enters their inboxes. If even 5,000 users load the app within the first 10 minutes, this would equate to an approximate load of 500 users per minute. The rest of your users working on other workflow or process apps may incur a slowdown on the network. They may only be filling in 100 apps on a regular day. This is a very low load and will be barely noticed by PerfectApps. |
You will need to predict how your load profile will look and then consider other factors that may affect your system performance, such as:
•Size of apps
•Form submissions
•Dashboard access load
•Reporting
•Notification load
|
The recommendations in the following sections are not performance guarantees, as there are numerous factors that affect performance which are beyond our control. |
See also: Disk Storage and RAID Levels, Client Side Requirements, Server Side System Requirements, Administering PerfectApps On-Premise
Return to PerfectApps On-Premise
