Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Added one minute throttling to NodeDB save to disk #3648

Merged
merged 6 commits into from
Apr 18, 2024
Merged

Conversation

thebentern
Copy link
Contributor

@thebentern thebentern commented Apr 16, 2024

This is to prevent the hammering of the file system on large meshes (public mqtt included). I ran a test earlier on the msh/US root and experienced 13 nodedb saves to disk within about a one minute period. It is likely responsible for some of the issues with nodes "loosing settings".

I have plans for a more uses of the generic throttle methods. A follow up PR to refactor smart position will utilize it.

thebentern added a commit to meshtastic/artifacts that referenced this pull request Apr 16, 2024
Copy link
Member

@GUVWAF GUVWAF left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Looks good, I like the modular approach.
Another low-hanging fruit would be to just don't save new nodes anymore when the NodeDB is full.

@thebentern thebentern merged commit 425a715 into master Apr 18, 2024
71 checks passed
@IMMORTAL0018
Copy link

Can the throttling be responsible for some position jumping while doing live tracking using mesh network with LoRa. During my test i found some jumping in the position of nodes while tracking. I have attached the video ..

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants