parallelvirtualcluster
/
docs
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity

Fix image link

This commit is contained in:
Joshua Boniface 2023-09-21 22:39:00 -04:00
parent 1673448228
commit 9168792e51
1 changed files with 1 additions and 1 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
docs/architecture/georedundancy.md
View File

@ -44,7 +44,7 @@ PVC clusters are quite network-intensive, as outlined in the [hardware requireme
The storage write process for PVC is heavily dependent on network latency.
[![Ceph Write Process](images/ceph-write-process.png)](images/ceph-write-process.png)
[![Ceph Write Process](images/pvc-ceph-write-process.png)](images/pvc-ceph-write-process.png)
As illustrated in this diagram, a write will only be accepted by the client once it has been successfully written to at least `min_copies` OSDs, as defined by the pool replication level (usually 2). Thus, the latency of network communications between the client and another node becomes a major factor in storage performance for writes, as the write cannot complete without at least 4x this latency (send, ack, recieve, ack). Significant distances and thus latencies (more than about 3ms) begin to introduce significant performance degredation, and latencies above about 5ms can result in a significant drop in performance.