I was running
ipfs daemon on a university server for research until the process was shut down by its administrator due to excess consumption of CPU and RAM. To run again, I’ll need to give an estimate of CPU and RAM usage.
How much CPU and RAM does
ipfs daemon typically consume in a set amount of time?
How do I measure resource consumption for
Hm, are you running version older than v0.4.12? Try upgrading to v0.4.13.
Older versions were missing connection closing logic, which is known to cause problems you described:
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?
Note: It’ll still consume a fair amount of CPU/memory. If you want, you can reduce some CPU usage by not acting as a DHT node (pass
--routing=dhtclient to the daemon). That should reduce the CPU usage to a reasonable amount (I run it on my laptop without issue).
I’m using verion 0.4.13 on a VPS with 512MB of RAM and the daemon is killed out of memory every hour.
Would be very nice to have an option to limit the number of peers and that way limite the memory consuption.
Yestarday in a discussion with
@stebalien on Github, he told me about a new configuration introduced on version 0.4.13 to limit the numbers of peers that a daemon can connect to.
This link provides information about the configuration:
This file has been truncated.
# The go-ipfs config file
The go-ipfs config file is a JSON document located at `$IPFS_PATH/config`. It
is read once at node instantiation, either for an offline command, or when
starting the daemon. Commands that execute on a running daemon do not read the
config file at runtime.
Configuration profiles allow to tweak configuration quickly. Profiles can be
applied with `--profile` flag to `ipfs init` or with the `ipfs config profile
apply` command. When a profile is applied a backup of the configuration file
will be created in `$IPFS_PATH`.
The available configuration profiles are listed below. You can also find them
documented in `ipfs config profile --help`.
Disables local host discovery, recommended when
I’ve just set new values on one of my nodes running on a DO VPS with 512MB of RAM and hope it helps to stop get killed by out of memory errors.
Below the github link.
04:35AM - 15 Aug 17 UTC
11:38PM - 29 Jul 19 UTC
ipfs version --all
go-ipfs version: 0.4.10-
Repo version: 5
System version: amd64/linux
Golang version: go1.8.3
My server configuration is 1 core, 512M memory
But when i...
Hope it helps.