- 2 Minutes à lire
- Impression
- PDF
Hardware Requirements
- 2 Minutes à lire
- Impression
- PDF
Global Architecture
Hardware Server Requirements
Hardware
iObeya software is scalable, so system requirements vary based on the projected usage of the iObeya environment being run. The maximum number of users that a server can support is constrained by both the server hardware specifications and the network bandwidth available to that server.
Server administrators should use this guide during the pilot period to evaluate their server hardware requirements. Since server load is difficult to predict, live testing is the best way to determine what hardware an instance requires in a production environment.
Server load is primarily driven by the number of concurrent users:
CPU load primarily depends on the general activity (number of rooms loaded simultaneously, frequency of concurrent modification in a room.
Memory load primarily depends on the number of concurrent users connected to the server at any given time.
Storage requirements varies depending on how many boards and pictures you wish to use in your iObeya rooms. If some use cases involve from the users to upload many high definition pictures on their boards, then the space required may increase.
Note:
iObeya performs best when used on a high performance dedicated server where no other applications are hosted. Therefore we highly recommend to use a dedicated server, either physical or virtual, to host iObeya on your production environment.
Increasing hardware and network specifications will improve overall application performance for end users. However, after upgrading any hardware or network specifications, the default settings of your application server, database server and iObeya may need to be updated to take benefit of the new hardware capabilities.
Hardware Requirements
As an example, running iObeya optimally on a dedicated application server that hosts five virtual iObeya rooms with a maximum potential of 50 concurrent users (5 rooms with 10 concurrent users per room), the application server would need to meet the following minimum requirements:
2 CPUs @ 2.5GHz (Intel(R) Xeon(R) or equivalent)
8GB RAM
10GB dedicated disk space for iObeya data (200Mo per rooms on average)
Examples of Hardware Specifications
These are examples of hardware specifications for real customer iObeya instances. These examples may be used as guidelines to size your hardware requirements based on the estimated number of rooms and potential concurrent users you may have on your iObeya instance.
Warning:
If you are running iObeya on virtual machines, the hardware specifications should be allocated and dedicated to the virtual machines.
For large scale deployment we highly recommend to host the application server and the database server on two separate servers hosted on the same network.
Examples:
Rooms | Declared Users | Concurrent Users | Server CPUs | Server Memory | Database CPUs | Database Memory |
---|---|---|---|---|---|---|
0-20 | <500 | <50 | 2 | 8GB (Xmx= 4827M) | 2 | 2GB |
20-100 | <1000 | <100 | 4 | 16GB (Xmx= 10600M) | 2 | 4GB |
100-500 | >1000 | <150 | 8 | 32GB (Xmx= 21268M) | 2 | 8GB |
>500 | >1000 | <300 | 36 | 72GB (Xmx= 46895M) | 4 | 16GB |
>500 | >1000 | >300 <600 | 48 | 96GB (Xmx= 63021M) | 8 | 32GB |
Client Requirements
Desktop, Laptop and tablet PCs
Hardware requirements
2 GHz dual-core processor or faster
2 GB of RAM
Screen resolution
1280x800px or higher
Note:
The screen resolution recommended provides the best user experience if iObeya is used in full-screen mode. In addition to screen resolution, the size of the web browser viewport can impact the user experience.
Network Requirements
As the bandwidth requirements vary depending on the load of the virtual rooms and boards (which is difficult to predict), user experience is estimated to be good when 1Mbps of network bandwidth is allocated per user account, and satisfactory with 256 Kbps per user.
iObeya software performance is satisfactory when at least 256 Kbps of network bandwidth on your server is allocated per remote participant. For example, with a 100Mbps bandwith connection to your server, you can estimate to have up to 100 concurrent remote participants with good performance and 400 concurrent remote participants with satisfactory performance.
Note:
If you want to use high-resolution pictures on your boards, we suggest increasing the bandwidth allocation to maintain satisfactory performance.