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.

Sign up for GitHub

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

Jump to bottom

New defaults for the Provider Record Republish and Expiration (22h/48h) #9389

Closed
6 tasks done
Tracked by #9417
yiannisbot opened this issue Nov 8, 2022 · 3 comments
Closed
6 tasks done
Tracked by #9417

New defaults for the Provider Record Republish and Expiration (22h/48h) #9389

yiannisbot opened this issue Nov 8, 2022 · 3 comments
Labels
kind/enhancement A net-new feature or improvement to an existing feature

Comments

@yiannisbot
Copy link
Member

yiannisbot commented Nov 8, 2022 •
edited by lidel
Loading

Checklist

  • My issue is specific & actionable.
  • I am not suggesting a protocol enhancement.
  • I have searched on the issue tracker for my issue.

Description

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).

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
@yiannisbot yiannisbot added the kind/enhancement A net-new feature or improvement to an existing feature label Nov 8, 2022
@lidel lidel moved this to 🥞 Todo in IPFS Shipyard Team Nov 8, 2022
@BigLep BigLep mentioned this issue Dec 5, 2022
Closed
@BigLep BigLep moved this from 🥞 Todo to 🔎 In Review in IPFS Shipyard Team Dec 7, 2022
@lidel
Copy link
Member

lidel commented Dec 8, 2022 •
edited
Loading

quick status update (cc @BigLep):

@lidel 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
This was referenced Dec 8, 2022
Merged
Closed
@lidel
Copy link
Member

lidel commented Dec 11, 2022 •
edited
Loading

Released remaining work with https://github.com/libp2p/go-libp2p-kad-dht/releases/tag/v0.20.0 and opened PR to bubble this up to Kubo: #9491

@lidel lidel mentioned this issue Dec 11, 2022
Merged
@BigLep
Copy link
Contributor

BigLep commented Dec 12, 2022

@lidel : I'm closing because of 3a3a971 . Please reopen if there is remaining work.

@BigLep BigLep closed this as completed Dec 12, 2022
Repository owner moved this from 🔎 In Review to 🎉 Done in IPFS Shipyard Team Dec 12, 2022
@lidel lidel mentioned this issue Mar 27, 2023
Merged
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
kind/enhancement A net-new feature or improvement to an existing feature
Projects
No open projects
IPFS Shipyard Team
Archived in project
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

feat: go-libp2p-kad-dht with expiration 48h ipfs/kubo
3 participants
@BigLep @lidel @yiannisbot