aboutsummaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorStefan Boberg <[email protected]>2024-01-30 18:27:42 +0100
committerGitHub <[email protected]>2024-01-30 18:27:42 +0100
commit65dd0ee532f699b7bc4a4544531eddab489b3655 (patch)
tree2d38ff834af19c1d3d3c03cc0b155ac637e2501e
parentUpdate README.md (diff)
downloadzen-65dd0ee532f699b7bc4a4544531eddab489b3655.tar.xz
zen-65dd0ee532f699b7bc4a4544531eddab489b3655.zip
Update README.md
-rw-r--r--README.md11
1 files changed, 7 insertions, 4 deletions
diff --git a/README.md b/README.md
index 5b3dc9b8e..8e01d984f 100644
--- a/README.md
+++ b/README.md
@@ -5,10 +5,13 @@ user machines either as a daemon or launched ad hoc as required during of editor
will use this service to manage local storage of secondary data such as the output from the cooker and local caches
used to accelerate data transformations (aka DDC).
-Zen server can also be deployed as a shared instance for use as a shared cache. It also supports upstream
-connectivity to cloud storage services as well as other Zen server instances. However, due to how
-propagation is handled this is not currently recommended as performance will be better if you use
-a hierarchical DDC graph in UE.
+Unreal Zen Storage Service can also be deployed as a shared instance for use as a shared cache. This is recommended
+for high load environments such as a build farm since we can handle significantly higher request rates compared to
+plain file share (SMB) and Cloud DDC.
+
+We also supports upstream connectivity to cloud storage services as well as other Zen server instances.
+However, due to how upstream/downstream propagation is handled this is not currently recommended as performance
+will be better if you use a hierarchical DDC graph in UE.
# Build Instructions