Skip to content

Change sntp update interval from 1 to 3 hour. #50

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

Closed
wants to merge 10 commits into from
Closed

Change sntp update interval from 1 to 3 hour. #50

wants to merge 10 commits into from

Conversation

CelliesProjects
Copy link
Contributor

Summary

Change sntp default update interval from 1 to 3 hours.

Impact

This PR aims at reducing the amount of requests sent to the (free as-in-beer and community run) ntp time servers.
The amount of requests for the ntp project should be a a lot less (per esp32) with this PR merged than with the current settings.

Rationale

Just from my home network with 5 esp32 controllers running, there are more than 100 ntp requests per day with the 1 hour update interval.
The ntp project is a community run service and open source projects should strive to minimize their impact on this service.

About this PR

This PR was started as espressif/arduino-esp32#5824 then moved here.

## Summary
Change sntp default update interval from 1 to 6 hours.

## Impact
This PR aims at reducing the amount of requests sent to the (free as-in-beer and community run) ntp time servers.
The amount of requests for the ntp project should be a a lot less (per esp32) than with the current settings. 

## Rationale
Just from my home network with 5 esp32 controllers there are more than 100 ntp requests per day with the 1 hour update interval. 
The [ntp project](http://www.ntp.org/) is a community run service and open source projects should strive to minimize their impact on this service.
@CelliesProjects CelliesProjects marked this pull request as ready for review November 1, 2021 14:41
@me-no-dev
Copy link
Member

Sorry for the late reply @CelliesProjects ! This PR somehow evaded me...

I can agree that we can change the interval to 3 hours, but why do the rest? The other two changes just limit the user. They can still define just 1 server, if that is what they need. Why do not allow them to have one over DHCP? Or define fallback? As you said, those are community servers, whose uptime is not 100% guaranteed.

@CelliesProjects
Copy link
Contributor Author

CelliesProjects commented Jun 13, 2022

@me-no-dev No idea what I was thinking. -too long ago-
Reverted those changes.
The only changed key now is CONFIG_LWIP_SNTP_UPDATE_DELAY.

@me-no-dev
Copy link
Member

as a side effect from time, the files no longer exist :) you would need to add that config value just once here

This pull request was closed.
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