Go-ipfs: IPFS API not responsive if the repository size has a lot of objects

Created on 28 Jun 2018 · 6Comments · Source: ipfs/go-ipfs

Version information:

Siderus Orion 0.6.1
go-ipfs 0.4.15

Type:

Bug

Description:

Original thread: https://github.com/Siderus/Orion/issues/124

In the original 3d the issue is happening when we add a new file or when we simply open a new window. These two windows are using:

PIN list
Add a file

As we am using js-ipfs-api, we have noticed that the issue is caused by go-ipfs.
Probably this is a duplicate but I was not able to find a clone of this.

Source

koalalorenzo

Most helpful comment

Migrating to badger datastore is great but not what this issue is about. Could you tell us more about the repo? OS, size, nature of the content (i.e. tons of small objects, or large objects), how exactly is the API not responsive, is all of it unresponsive?

ghost on 28 Jun 2018

👍3

All 6 comments

have you tried using badgerds for your data store?

bonedaddy on 28 Jun 2018

That could be a solution for new repositories that we set up in the client.
In the original issue the owner of the repo decided to not use Siderus Orion repository but to use its own (which is its own go-ipfs instance running in background). We can suggest that to @NatoBoram

koalalorenzo on 28 Jun 2018

You can migrate from Flatts to badgers. Ah okay I would probably have him use your client instead of gos

bonedaddy on 28 Jun 2018

ghost on 28 Jun 2018

👍3

@lgierth The first piece of information I can give you is the issue https://github.com/Siderus/Orion/issues/124, which contains a few screenshots of the API in action.

Then, eh... I added multiple UIbuntu 18.04 ISOs flavours, and all Android P Developer Preview ZIPs, and I generally use IPFS whenever I have to share something. So... "there's stuff in there". I also use IPFS when I want to share images on Internet and I host them on my private node and sometimes mirror them on my public node.

I'm using Windows 10 with Go-IPFS running in a scheduled task on login.

With that, I think you might have a good idea of the nature of the node's content.