venus-os:extended
Differences
This shows you the differences between two versions of the page.
Both sides previous revisionPrevious revision | Next revisionBoth sides next revision | ||
venus-os:extended [2020-06-17 00:11] – [Appendix A - Repartitioning Venus GX flash memory] mvader | venus-os:extended [2020-06-23 15:52] – [3.2 CPU & Memory resources] mvader | ||
---|---|---|---|
Line 38: | Line 38: | ||
===== 3. Requirements ===== | ===== 3. Requirements ===== | ||
+ | |||
+ | ==== 3.1 GX Device compatibility ==== | ||
A compatible GX device: | A compatible GX device: | ||
Line 49: | Line 51: | ||
Venus OS extended is also available for certain RaspberryPi models. Installation files below, and installation & other raspberrypi specific instructions [[https:// | Venus OS extended is also available for certain RaspberryPi models. Installation files below, and installation & other raspberrypi specific instructions [[https:// | ||
+ | |||
+ | ==== 3.2 CPU & Memory resources ==== | ||
+ | |||
+ | Both SignalK as well as Node-red are rather resource intensive software applications to run on the GX Device. From a CPU usage point of view as well as RAM memory. | ||
+ | |||
+ | Ofcourse, how intensive depends on what kind of flows (node-red) or how many messages & handling of them (SignalK) happens in the system. | ||
+ | |||
+ | From a GX device point of view, from the support models the Venus GX is the one with the least resources. Running both SignalK and Node-RED at the same time will be " | ||
+ | |||
+ | Cerbo GX is already much faster, as it has a dual core CPU as well as much more RAM. | ||
+ | |||
+ | More details about CPU & RAM differences are in this document: https:// | ||
+ | |||
+ | When running out of RAM or CPU, the device will slow down. And eventually also reboot by itself due to the watchdog. | ||
===== 3. How to install ===== | ===== 3. How to install ===== |
venus-os/extended.txt · Last modified: 2021-01-06 22:04 by mvader