CPU and MEM high!!!

[ronnierry]

start

root 8469 1 99 12:37 pts/0 08:22:42 ./geth --datadir ./mainnet --rpc --rpcaddr 0.0.0.0 --rpcport 8081 --identity ethereum ipc --rpcapi web3,eth,net,personal,db,admin

problem

System information

Geth version:

Version: Linux

Commit hash : (if develop)

log

Expected behaviour

Actual behaviour

Steps to reproduce the behaviour

Backtrace

[backtrace]

[hashfury42]

hi, ronnierry
This issue may help you
[https://github.com//issues/16377]

[hapsody]

Same issue here.

Server
AWS t3.medium(64bit - ubuntu 16.04, 2core, 4GB Ram, 8GB Swap memory)
version : 1.8.1-stable, 1.8.16-stable
fast and light syncmode both.

geth --rinkeby --rpc --rpcaddr "0.0.0.0" --rpcvhosts=* --rpcport "8545" --rpccorsdomain "neojuneELB-1439772252.ap-northeast-2.elb.amazonaws.com" --rpcapi "eth,net,web3,personal,admin" --syncmode "light" --cache "64"

It also have been occurred. I can't see out of memory error form geth i think that because of using "--cache" flag and setting swap memory.
but new problem is here increasing slowly high cpu and mem usage problem
what am i suppose to do?

[karalabe]

@ronnierry Geth on mainnet will want to use by default (latest release at least) 4GB of RAM for caching + will probably consume more, maybe 6-7. As for the slow blocks, do you have SSD or HDD? Regarding high CPU use, I saw that you have your RPC open to the public internet, so you might have random remote machines trying to brute force your accounts (causing high memory and CPU use), never expose RPC to the internet.

@hapsody You ran Geth with 64MB of cache allowace, that's unusable on mainnet. Mainnet nowadays needs a lot of memory. Also don't bother with Swap, that just kills performance altogether. Same re RPC, never open publicly.