RFC29_Optimize Nano Setup by Removing Unused Services #41
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
The current setup for the Nano includes 11 services:
following
,ftpd
,httpd
,inference
,mongodb
,pilot
,rosnode
,teleop
,vehicle
,wireguard
, andzerotier
. When all these services are active, the CPU and memory are nearly fully utilized even when idle. This results in performance bottlenecks, especially when resource-intensive services likeFOL
(Following) orINF
(Inference) are running.To address this, we are removing services that are not currently needed, such as Wireguard and ROS. This change aims to optimize resource usage and improve the overall performance of the Nano during operations. While a hardware upgrade may be necessary in the future, this update focuses on improving efficiency with the existing setup.
Changes
Wireguard
andROS
services from the Nano's setup.Impact