Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

EOP-126: Review of Momentum tech specs #762

Merged
merged 10 commits into from
May 28, 2024
5 changes: 3 additions & 2 deletions .github/workflows/labeller.yml
Original file line number Diff line number Diff line change
Expand Up @@ -6,9 +6,10 @@ on:
jobs:
triage:
runs-on: ubuntu-latest
runs:
using: 'node16'
steps:
- uses: actions/setup-node@v4
with:
node-version: '16.x'
- uses: actions/labeler@v2
with:
repo-token: '${{ secrets.GITHUB_TOKEN }}'
51 changes: 25 additions & 26 deletions content/momentum/4/hardware-config.md
Original file line number Diff line number Diff line change
@@ -1,43 +1,42 @@
---
lastUpdated: "03/26/2020"
lastUpdated: "05/01/2024"
title: "Hardware Deployment Configuration"
description: "The Single Node Lab system is designed to support multiple functions in your environment including development testing staging and other non production roles The system deploys to a single server supporting all Momentum functionality The Single Node Lab System should not be used for performance testing nor is it recommended..."
description: "The Single Node Lab system is designed to support multiple functions in your environment including development testing staging and other non production roles"
---

The Single Node Lab system is designed to support multiple functions in your environment, including development, testing staging, and other non-production roles. The system deploys to a single server supporting all Momentum functionality. The Single Node Lab System should not be used for performance testing, nor is it recommended for production use due to its lack of redundancy.
The Single Node Lab system is designed to support multiple functions in your environment, including development, testing staging, and other non-production roles. The system deploys to a single server supporting all Momentum functionality. The Single Node Lab System should not be used for performance testing, nor it is recommended for production use due to its lack of redundancy.

<a name="single_node_lab_hw_reqs"></a>
### <a name="single_node_lab_hw_spec"></a> Hardware Specifications


| Resource | Minimum Specification |
| Resource | Specification |
| --- | --- |
| CPU | 8 x 2.5 GHz Cores (Min Speed) |
| Memory | 32 GB RAM |
| Network Interface | 1 GB NIC |
| CPU Cores | 8 |
| CPU Speed | 3.2 GHz (min. 2.5 GHz) |
| Memory | 32 GiB (min. 16 GiB) RAM |
| Network Interface | 1 Gbps NIC |

<a name="single_node_lab_storage_array"></a>
__NOTE:__ If running in cloud environments, CPU-optimized instances are recommended over general-purpose and memory-optimized instances.

### <a name="single_node_lab_storage_array"></a> Storage Configuration

| Array | Configuration | Mount Points and Notes |
| Array | Mount Points | Configuration |
| --- | --- | --- |
| All Storage | 4 x 150 GB 15k RPM HDD |   |
| Message Spools | 2 x 150 GB in RAID1 |

/var/spool/ecelerity

Note: This array should be dedicated to the spools.

|
| OS, App Binaries, Logs, Platform DB, Analytics DB | 2 x 150 GB in RAID1 |
| All Storage |   | 4 x 150 GiB 15k RPM HDD |
| Message Spools* | `/var/spool/ecelerity` | 2 x 150 GiB in RAID1 |
| OS<br>App Binaries<br>Logs<br>Platform DB<br>Analytics DB | `/` (root)<br>`/opt/msys`<br>`/var/log/ecelerity`<br>`/var/db/cassandra`<br>`/var/db/vertica` | 2 x 150 GiB in RAID1 |

* OS - / (root)
(*) _This array should be dedicated to the spools._

* Logs - /var/log/ecelerity
### <a name="single_node_lab_ref_meas"></a> Reference Measurements

* App Binaries - /opt./msys
With the hardware specifications above, the system was able to sustain an ESMTP injection rate of:

* Platform DB - /var/db/cassandra
- 1.8 M messages/hour
- 100 kiB each message

* Analytics DB - /var/db/vertica
with:

|
- CPU Usage: __65%__ (5-6 cores out of 8)
- Memory usage:
- Virtual: __2.2 GiB__
- Resident: __500 MiB__
Loading
Loading