Excessive thread creation about go-libp2p HOT 3 CLOSED

Especially since it creates a whole thread.

It creates a goroutine, which is much lighter weight than a thread. E.g., if you look at the go standard library, the HTTP library will create a new goroutine per request.

However, I do generally agree. This kind of situation is why we introduced the event bus. The correct fix here is to:

1. Remove the notifee system entirely. Well, likely deprecate it for now then remove it later.
2. Emit an event using the host.

from go-libp2p.

See #1221.

from go-libp2p.

I just deleted the "go" in my Libp2p and continued writing code.
And your Libp2p still has the creation of goroutine. And other discovery modules do not have goroutine creation, when passing peer.
Your Libp2p code is not fixed, but mine is. It's my role to tell you about the problem. But I noticed you don't listen to me at all. It's my duty to give you a chance. How you use it is up to you.

from go-libp2p.