Skip to content

Commit d76782d

Browse files
committed
Improve storage growth definition
1 parent d2c8342 commit d76782d

File tree

1 file changed

+11
-4
lines changed

1 file changed

+11
-4
lines changed

content/deployment/reference/server-specifications.md

Lines changed: 11 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -13,12 +13,19 @@ The minimum server specifications are:
1313

1414
Approximately 750 MB of storage is required for the engine itself, with the remaining space allocated for data generated by the engine. Storage capacity should be calculated based on the scope and expected lifetime of the collection.
1515

16-
## Storage growth
16+
## Storage
1717

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:
18+
Recommended storage: 10 GB, with resizable partitioning to enable growth over time.
1919

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
20+
Storage usage typically grows at a rate of 0.5 MB per tracked terms per month on average for latin scripts. This growth rate varies depending on the type of service being tracked:
21+
22+
- Services with large legal teams and heavy website layouts: ~1 MB per terms per month
23+
- Smaller services: ~0.1-0.3 MB per terms per month
24+
25+
### Examples
26+
27+
- Tracking 5 very large social media platforms on their 5 most common terms types (such as Terms of Service, Privacy Policy, Trackers Policy, Developer Agreement, Community Guidelines) would require approximately 300 MB of additional storage per year.
28+
- Tracking a sample of 200 platforms on an average of 4 common terms types would require approximately 5 GB of additional storage per year.
2229

2330
## Operating system
2431

0 commit comments

Comments
 (0)