You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: README.md
+21-1Lines changed: 21 additions & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -75,12 +75,32 @@ A Web Interface is available to monitor which frames are pending for which devic
75
75

76
76
77
77
78
+
# Sizing
79
+
80
+
For the docker deployment, container should have the following sizing :
81
+
82
+
- CPU : 1 Core
83
+
- RAM : 256 MB
84
+
- Network : 1 Mbps
85
+
- Disk space : No disk usage. Everything is stored in-memory
86
+
78
87
# Test
79
88
89
+
Tests dependencies are listed in the `requirements.txt` file under `tests` folder.
80
90
Tests should always be run inside the `tests` folder for proper initialization.
81
91
92
+
93
+
# Limitation
94
+
95
+
Stress tests shows the following :
96
+
- At very high load (thousands of different devEUI over a minute) :
97
+
- Monitor interface can fail because the `frame_buffer` object is being rendered to front-end and modified in same time.
98
+
- Self-hosted MQTT broker can crash (mosquitto process)
99
+
- For a very high number of pending fragment (100k different devEUI) : Monitor interface can take up to 1 mn to fully load, because everything is displayed in the front-end.
100
+
101
+
82
102
# Roadmap
83
103
84
104
- HTTP Input/Output
85
105
- Do some modularization to allow interfacing multiple decoders
86
-
-Tests
106
+
-Multi-stage docker to remove NPM dependencies (which add few hundreds of MB to the image size)
0 commit comments