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

IPNS publish very slow #6236

Closed
kubatial opened this issue Apr 19, 2019 · 2 comments
Closed

IPNS publish very slow #6236

kubatial opened this issue Apr 19, 2019 · 2 comments
Labels
kind/bug A bug in existing code (including security flaws) status/duplicate This issue or pull request already exists

Comments

@kubatial
Copy link

Version information:

go-ipfs version: 0.4.18-
Repo version: 7
System version: amd64/linux
Golang version: go1.11.1

Type:

-"bug", "feature"

Description:

I am running an IPFS node on a standard Ubuntu machine in AWS as part of an app I am developing. As part of the app I also have to regularly generate keys for my node and then do an ipfs name publish. The problem is that whenever I try publishing, it generally takes a long time (2-3min on average, occasionally 5min or longer). Anything above 1 min would basically make my app unusable. I have tried running the daemon with --enable-namesys-pubsub, but without any noticeable improvements. I was wondering if there is some easy way I might have missed which would get the publishing time down to under 1min. Maybe a setting which might make the publishing faster locally at first and propagate it through the network later?

Thanks in advance

@Stebalien
Copy link
Member

Unfortunately, no. At the moment, IPNS publishing is just really slow due to some issues with our DHT and scaling.

Dup of #3860.

@Stebalien Stebalien added status/duplicate This issue or pull request already exists kind/bug A bug in existing code (including security flaws) labels Apr 19, 2019
@momack2 momack2 added this to Done in ipfs/go-ipfs May 9, 2019
@ec1oud
Copy link

ec1oud commented Dec 12, 2020

It's still slow by default. For the ipfs client it should be instantaneous, because it's up to the daemon to do the actual work, and there's nothing for the client to wait for. It seems we need the --offline option for that, but since there's nothing to wait for, why wait for it by default?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/bug A bug in existing code (including security flaws) status/duplicate This issue or pull request already exists
Projects
No open projects
Development

No branches or pull requests

3 participants