Skip to content

Commit 00ef26d

Browse files
committed
Improve LH's Readme
1 parent 2cc53d5 commit 00ef26d

File tree

1 file changed

+13
-0
lines changed

1 file changed

+13
-0
lines changed

charts/longhorn/README.md

Lines changed: 13 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -30,3 +30,16 @@ Workloads can run on nodes without LH as long as LH is not restricted to specifi
3030
Note: There is an [ongoing bug](https://github.com/longhorn/longhorn/discussions/7312#discussioncomment-13030581) where LH will raise warnings when workloads run on nodes without LH. However, it will still function correctly.
3131

3232
Source: https://longhorn.io/kb/tip-only-use-storage-on-a-set-of-nodes/
33+
34+
### Adding new volumes to (PVs that rely on) LH
35+
36+
Monitor carefully whether LH is capable of handling new volumes. Test the new volume under load (when many read/write operations occur) and ensure LH does not fail due to insufficient resource capacities (e.g., network or CPU). YOu can also consider LH's performance section from this Readme.
37+
38+
LH's minimum recommended resource requirements:
39+
* https://longhorn.io/docs/1.8.1/best-practices/#minimum-recommended-hardware
40+
41+
### LH's performance
42+
43+
Insights into LH's performance:
44+
* https://longhorn.io/blog/performance-scalability-report-aug-2020/
45+
* https://github.com/longhorn/longhorn/wiki/Performance-Benchmark

0 commit comments

Comments
 (0)