libp2p/go-libp2p-resource-manager
1
0
Fork 0
mirror of https://github.com/libp2p/go-libp2p-resource-manager.git synced 2025-03-10 17:20:39 +08:00
Code Issues Projects Releases Wiki Activity

Nits

Browse Source
This commit is contained in:
Marco Munizaga 2022-08-09 12:53:28 +02:00
parent d81430f88a
commit c50151cb05
1 changed files with 2 additions and 2 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

4
README.md
View File

@ -29,7 +29,7 @@ computational time) at the system level. They are also a scarce
resource, as typically (unless the user explicitly intervenes) they resource, as typically (unless the user explicitly intervenes) they
are constrained by the system. Exhaustion of file descriptors may are constrained by the system. Exhaustion of file descriptors may
render the application incapable of operating (e.g. because it is render the application incapable of operating (e.g. because it is
unable to open a file), most importantly for libp2p because most unable to open a file), this is important for libp2p because most
operating systems represent sockets as file descriptors. operating systems represent sockets as file descriptors.
### Connections ### Connections
@ -301,7 +301,7 @@ anamoly.
Sometimes disabling all limits is useful when you want to see how much Sometimes disabling all limits is useful when you want to see how much
resources you use during normal operation. You can then use this information to resources you use during normal operation. You can then use this information to
define your initial limits. define your initial limits. Disable the limits by using `InfiniteLimits`.
### Debug "resource limit exceeded" errors ### Debug "resource limit exceeded" errors