Requirements
Our platform's hardware and system requirements.
General
This topic outlines the hardware and system requirements for installing Bytesaige.
It may not always be feasible to provision a server with precisely the right capacity—especially in environments where indexing demands grow over time due to the addition of new data sources. While performing an upfront sizing analysis is helpful, it's even more critical to ensure that your Bytesaige server can scale as needed. To fully take advantage of the Bytesaige architecture, plan for scalability along the following dimensions:
-
Vertical scaling: Add more RAM or CPU to individual nodes as needed.
-
Horizontal scaling: Not currently supported.
-
Storage scaling: Ensure that disk volumes can be resized to accommodate growing data needs (see the guidelines below for recommended disk configurations).
Hardware
The hardware requirements in the table below are estimates based on typical deployment environments and load profiles. Actual requirements may vary depending on your specific use case. The estimates for each column are based on the following assumptions:
Minimum node specifications:
- CPU and RAM must be dedicated exclusively to Bytesaige.
- CPU power-saving features must be disabled.
- CPUs must run at a minimum clock speed of 2 GHz.
- The host must have at least 32 GB of RAM allocated.
Sizing
Node type | Min CPU | Min RAM | Min GPU | Min Storage | Relevant metrics |
---|---|---|---|---|---|
Standard | 4 vCPUs | 32 GB | - | 300 GB | - |
Examples
Storage
System
This topic outlines the operating system requirements for installing Bytesaige. For hardware requirements, see the section above.
- A dedicated host is required. This host must not run other CPU- or memory-intensive services, or any services that use ports required by Bytesaige.
- A 64-bit Linux distribution is required (see the list of supported distributions below). Installation is supported on both physical and virtualized hosts. Container-based installation is not supported.
- Ensure that firewall settings are configured appropriately (see below).
- Bytesaige installs locale-aware libraries. To ensure correct rendering of text and symbols, set the system locale to an English option (e.g.,
LANG=en_US.UTF-8
).
Operating systems
Operating system | Supported versions | CPU architectures |
---|---|---|
RHEL | 8.8, 8.10, 9.2, 9.4, 9.5 | x86-64 |
Debian | 10, 11, 12 | x86-64 |
Outbound traffic
All server nodes must be able to communicate with external endpoints to receive installation packages, software updates, and support services.
Note: The GitLab and GitLab CDN endpoints are planned for removal and will be replaced by the Bytesaige domain requiring this the only domain to be whitelisted.
- GitLab (planned removal):
gitlab.com
- GitLab CDN (planned removal):
cdn.registry.gitlab-static.net
To enable support functionality, all server nodes should be able to reach the Bytesaige backend at the following address:
- Bytesaige domain:
ops.bytesaige.com
The Bytesaige backend is currently hosted on Google Cloud Platform, U.S. regions.
Internal node ports
Bytesaige requires configuration of network ports to operate and to serve pages.
Be sure to configure your network and firewall so that all ports listed below are accessible. Note that ports should be opened for bi-directional communication. For a typical deployment, we recommend that all ports be open between the cluster nodes.
Incoming ports
Port 443 must remain open to access the Bytesaige UI without port forwarding.
Port | Used by | Notes |
---|---|---|
443 | Bytesaige UI | - |
13300 | Bytesaige UI (internal) | Replaced by 443, does no longer need to be open |
13000 | Grafana | Used for self-monitoring |