-
Notifications
You must be signed in to change notification settings - Fork 0
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
Vestigial variable DataUpload::lastConnectTime #133
Comments
According to the docs the limit is now "Maximum of 10,000 requests every 5 minutes". |
So this corresponds to 33 requests per second across the entire fleet. We can probably incur many connect/disconnect events in rapid succession per device, but we want to avoid this anyhow to conserve energy. So we want to probably implement a per device limit. I think it will probably suffice to do a limitation of one publish per second, and an exponential back off for connect from once per second to once every 6 hours on connection failure. Probably want to do a connection timeout of 1 second or so, that way the system isn't sitting there churning, maybe an exponential gain of 2 or 3? |
This should probably go into a decision log |
Sleep recommendations from particle docs:
Also from same page: "Particle Device OS is not intended to handle very short sleep cycles. Practically speaking, the minimum is about 10 seconds." |
smartfin-fw3/src/cellular/dataUpload.hpp
Line 48 in 91b5bb9
In smartfin-fw, there was a limitation that we could not connect to the Particle network more than once a second. There was some logic to rate limit the number of connections made.
DataUpload
andsf::cloud
consolidates network connections to minimize churn on network state.The text was updated successfully, but these errors were encountered: