Basic Enterprise Application Realm

Basic Enterprise Application Realm Documentation
  • 1 About BEAR
  • 2 Release Notes
  • 3 Developer Toolkit
  • 4 Installation & Upgrades
    • 4.1 Installation Steps
    • 4.2 Network Requirements
    • 4.3 Application Server Initialization (First Run)
    • 4.4 Uninstallation
  • 5 Backend Adminitration
    • 5.1 Introduction
    • 5.2 Common Commands
    • 5.3 Application Server Commands
    • 5.4 Resource Monitor Commands
    • 5.5 Sharepoint Commands
    • 5.6 Database Commands
  • 6 Frontend Adminitration
    • 6.1 User Management
    • 6.2 Package Management
    • 6.3 Installing Documentation Packages
    • 6.4 Application Storage
    • 6.5 Resource Monitoring
    • 6.6 Resource Scaling
    • 6.7 Starting & Stopping BEAR
    • 6.8 Security
      • 6.8.1 TLS
    • 6.9 Physical Storage
      • 6.9.1 RAID
      • 6.9.2 File Systems
      • 6.9.3 Viewing the Storage Summary
      • 6.9.4 Decommissioning (wiping) Disks
      • 6.9.5 Storage Management
    • 6.10 Event Distribution
    • 6.11 Hostnames & Ports

6.6 Resource Scaling

July 6th, 2025

RBAC required: BEAR: HTTP controls

Scaling controls the number of application server processes and threads per process to handle connections from users. However, this may not be the best way to scale every application. Although scaling consumes additional CPU and memory resources, how that translates to overall resource utilisation under high connection loads depends on the requirements the running application. Some applications may require intensive memory footprints to handle relatively few connections while others may have small footprints to handle a large number of connections. Therefore, setting this, and then adjusting as necessary based on observations in the Logs & Monitoring panel is important. Also consider the total bandwidth ceiling of the network connection. Scaling up here will not help if the bandwidth is already saturated.

At some point, better scaling will be achieved by clustering multiple application servers.

6.6.1 Scaling Values

The settings make changes to how the web server service handles resources for concurrent connections in the following ways.

Scale Connections Requests Notes
Tiny 10 10,000 Minimal resource footprint. Suitable for admin hosts that service no actual users other than one or two system administrators. This is suitable for hosts with 4 GiB or less of memory.
Small 64 256,000 Very small resource footprint. Suitable for small home or office usage where there are likely to be less than forty users. This is suitable for hosts with 4 GiB or less of memory.
Medium 128 640,000 Moderate resource footprint. Suitable for hosting low traffic public web sites or internal web services in medium sized organisations where there may be up to 4,000 users. This is suitable for hosts with 16GiB or less of memory and a 1g network.
Large 256 2,560,000 Big resource footprint. Suitable for hosting medium traffic public web sites or internal web services to large organisations where there may be up to 100,000 users. This is suitable for hosts with 128 GiB or less of memory and dedicated 10g networks or better.
Massive 1,024 10,240,000 Huge resource footprint. Suitable for hosting high traffic public web sites or internal webservices for the largest organisations with over 200,000 users. This is suitable for hosts with between 128 GiB and 1 TiB of memory and dedicated 10g networks or better.

6.6.2 Scaling Configuration Steps

  1. From the admin Tools menu, select HTTP Control and open the Scaling tab.

scaling

  1. Select the scale factor desired.
  2. Click Apply.

Remember, the scale factor will not take effect until BEAR is restarted (see Starting & Stopping BEAR).

previous: Resource Monitoring next: Starting & Stopping BEAR