docs: add recommended RAM size #4278
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
✅ Deploy Preview for teslamate ready!
To edit notification comments on pull requests, go to your Netlify site configuration. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Successor of #4250
1GB of Ram is sufficient for installation. I personally have been running TeslaMate on a Raspberry Pi 3B+ with 1 GB Ram for 5 years without any problems. And yes, this does require some background knowledge, such as how to set up ZRAM.
Nevertheless, in this day and age it is advisable to have at least 2 GB Ram.
In version 1.30.1, we have increased the performance of a dashboard by a factor of 100. The next version will include further performance improvements and the dashboards run smoothly on a Raspberry Pi3 B with 1 GB Ram (there is only one value that takes a long time to load in a dashboard, but we will fix that too). In addition, we have improved the background load that occurs, e.g. to add missing elevation data etc. by a factor of 900.