IPFS daemon is eating up all the resources on my computer, what is happening?

I’m evaluating IPFS for more than a month now. It worked quite well initially, but nowadays things went crazy.

Whenever I dare to start the daemon it will “spin up” within a hour and consumes 100% CPU, 3-4 GB RAM, and have 2040 peers connected, and the deamon cannot stop spewing error messages about “too many open files”.

It’s started recently, what is happening?

2 Likes

This is due to unexpected growth from about ~1k to ~6k nodes (as of today).
Performance improvements are being actively developed, but these things take time.

We just need to be patient :slight_smile:

6 Likes

Note: We’ll likely have connection closing/limiting support in the next release so it should get significantly better.

4 Likes

growth from about ~1k to ~6k nodes

What a great problem to have! Any idea what caused this sudden incredible growth?

1 Like

My guess:

And the publicity it created.

4 Likes