Partner Experience: update platform server prerequisites (#143) #170
Conversation
|
Preview is available here: |
|
Something went wrong with PR preview build please check |
|
Preview is available here: |
5 similar comments
|
Preview is available here: |
|
Preview is available here: |
|
Preview is available here: |
|
Preview is available here: |
|
Preview is available here: |
urvisavla
force-pushed
the
143/horizon-prerequisites
branch
from
602e66b to
5e1f0d5
Compare
|
Preview is available here: |
|
|
||
| In this scenario, the hardware specifications are more demanding than what is necessary for the day-to-day operation of real-time ingestion, but catch-up only needs to occur once. | ||
| **_PostgreSQL database server compute instance:_** |
There was a problem hiding this comment.
this is currently a placeholder, we will state min compute requirements for postgres here correct? This seems like good place to also stipulate the postgres server version requirements, such as from team discussion. Just for consideration, maybe we relocate the low level postgres server configs mentioned in Configuring, inline here instead, to keep all postgres/vendor specifics about the db here in one place, then rest of docs just refer to postgres more generically as the database.
CC'ing @tamirms for postgres context
There was a problem hiding this comment.
We run postgres v 12.13 in prod
|
Preview is available here: |
| | **Database** | **CPU**: 16 cores (min: 8)<br/>**RAM**: 64 GB (min: 32GB)<br/>**Storage**: 2 TB<br/>**IOPS**: 20K (min: 15K) | **CPU**: 16 (12)<br/>**RAM**: 128 GB (64)<br/>**Storage**: 4 TB<br/>**IOPS**: 20K (15K) | **CPU**: 64 (32)<br/>**RAM**: 512 GB (256)<br/>**Storage**: 10 TB<br/>**IOPS**: 20k (15k) | | ||
| | **Storage**<br/>(all same) | | **SSD** (NVMe, Direct Attached Storage preferred) | | | ||
| | **AWS**<br/>(reference) | **Captive Core**: `m5.2xlarge`<br/>**Database**: `r5.2xlarge` | **Captive Core**: `m5.4xlarge`<br/>**DB**: `r5.4xlarge` | **Captive Core**: `c5.2xlarge` (x2)<br/>**DB**: `r5.16xlarge` (ro)<br/>`r5.8xlarge` (rw) | | ||
| To achieve high availability, redundancy, and high throughput, explore the [scaling](./scaling.mdx) strategy. It provides detailed prerequisites and guidelines to determine the appropriate [number of Horizon instances](./configuring.mdx#multiple-instance-deployment) to deploy. |
There was a problem hiding this comment.
hmm, do we need to update scaling.mdx, it hasn't been touched as of the rest of partner experience tickets, maybe it falls under the purview of prerequisites?
There was a problem hiding this comment.
Ok, I'll take a look at the scaling doc.
Update docs/run-platform-server/prerequisites.mdx Co-authored-by: shawn <[email protected]> Update docs/run-platform-server/prerequisites.mdx Co-authored-by: shawn <[email protected]> Update docs/run-platform-server/prerequisites.mdx Co-authored-by: shawn <[email protected]> Update docs/run-platform-server/prerequisites.mdx Co-authored-by: shawn <[email protected]> Update docs/run-platform-server/prerequisites.mdx Co-authored-by: shawn <[email protected]> Update docs/run-platform-server/prerequisites.mdx Co-authored-by: shawn <[email protected]> Addressing review comments
urvisavla
force-pushed
the
143/horizon-prerequisites
branch
from
d3eb316 to
f8f7f73
Compare
|
Preview is available here: |
Co-authored-by: shawn <[email protected]>
|
Preview is available here: |
Co-authored-by: shawn <[email protected]>
|
Preview is available here: |
What
Update platform server prerequisites.
Hardware requirements largely remain the same as the current specifications of real-time private instance, except for updated disk space to accommodate on-disk captive-core mode and reduced history retention. These specifications reflect minimums due to a lack of benchmarks for API instances.
Why
#143