You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We have carried out a detailed study on the Republish and Expiration intervals for Provider Records in IPFS. Our results suggest that:
the Republish Interval can be increased to 22hrs (at least), and
the Expiration Interval can be increased to 48hrs.
Increasing those values will reduce significantly (by ~100%) the overhead of content providers, as they now have to republish their records at a much lower frequency (every 22hrs, compared to every 12hrs).
when done, we need to switch kubo to release with the above
lidel
changed the title
Implement new defaults for the Provider Record Republish and Expiration Intervals
New defaults for the Provider Record Republish and Expiration (22h/48h)
Dec 8, 2022
Checklist
Description
We have carried out a detailed study on the Republish and Expiration intervals for Provider Records in IPFS. Our results suggest that:
Increasing those values will reduce significantly (by ~100%) the overhead of content providers, as they now have to republish their records at a much lower frequency (every 22hrs, compared to every 12hrs).
You can read the detailed study here: https://github.com/protocol/network-measurements/blob/master/results/rfm17-provider-record-liveness.md
The changes have been implemented in the following PRs:
The relevant libp2p specs have also been updated in this spec PR: libp2p/specs#451
cc: @cortze
The text was updated successfully, but these errors were encountered: