Skip to content

Commit 09d1939

Browse files
authored
Add server specifications (#164)
2 parents d45eb41 + e8025ff commit 09d1939

File tree

2 files changed

+35
-0
lines changed

2 files changed

+35
-0
lines changed
Lines changed: 4 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,4 @@
1+
---
2+
title: Reference
3+
weight: 2
4+
---
Lines changed: 31 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,31 @@
1+
---
2+
title: Server specifications
3+
weight: 1
4+
---
5+
6+
# Server specifications
7+
8+
The minimum recommended server specifications are:
9+
10+
- 2GB RAM
11+
- 1CPU @ 2GHz
12+
- 10GB storage
13+
14+
Approximately 750MB of storage is required for the engine itself, with the remaining space allocated for data generated by the engine.
15+
16+
## Storage growth
17+
18+
Storage requirements typically grow at a rate of less than 0.5MB per tracked terms per month on average. This growth rate varies depending on the type of service being tracked:
19+
20+
- Very large online platforms with large legal teams and heavy layouts: ~1MB per terms per month
21+
- Standard collections: ~0.1-0.3MB per terms per month
22+
23+
## Operating system
24+
25+
Supported operating systems:
26+
- Ubuntu 20.04 or higher
27+
- Debian 11 or higher
28+
29+
## Location
30+
31+
Servers should be physically located in geographic regions that align with the jurisdiction the collection targets to ensure to [obtain documents like a user would]({{< relref "concepts/design-principles#3-obtain-documents-like-a-user-would" >}}). This is crucial because some services deliver different versions of documents based on the location of the request, even when the documents are supposed to be identical.

0 commit comments

Comments
 (0)