Eventeum config for reducing load on GETH

Hello, We are using Eventeum for monitoring transactions, our contracts, and ERC20 Tokens too. When we tried to add 20+ token into Eventeum our Ethereum node started struggling. Currently, we have 8c/16Gb server config and CPU load is 95-100% and for this reason, flowable and subscriptions are restarting and we are losing sync state. Can you help us configuring Eventeum to lower the load on the node or if config is well organized can you tell us minimum requirements for the server to serve our purpose without any downtime. In regard to that our system will grow to 100+ ERC20 tokens.

server:
  tomcat:
    uri-encoding: UTF-8
  port: 8060

logging:
  level:
    org.springframework.web: ERROR
    net.consensys: DEBUG
    net.consensys.configs: ERROR
  pattern:
    console: "%d{yyyy-MM-dd HH:mm:ss.SSS} [%t] %-5p %c: %M - %m%n"
    file: "%d{yyyy-MM-dd HH:mm:ss.SSS} [%t] %-5p %c: %M - %m%n"
  file: /logs/application.log

ethereum:
  nodes:
    - name: default
      url: ${ETHEREUM_NODE_URL:http://127.0.0.1:8545}
      blockStrategy: POLL
      syncingThreshold: 100
      healthcheckInterval: 3000
  healthcheck:
    pollInterval: 2000
  blockStrategy: POLL

ether:
  node:
    url: http://127.0.0.1:8545
eventStore:
  type: DB
  url: http://localhost:8081/api/rest/v1
  eventPath: /event
  latestBlockPath: /latestblock

database:
  type: MONGO

broadcaster:
  type: KAFKA
  cache:
    expirationMillis: 6000000
  event:
    confirmation:
      numBlocksToWait: 1
      numBlocksToWaitForMissingTx: 100
      numBlocksToWaitBeforeInvalidating: 2
  multiInstance: false
  enableBlockNotifications: true

# For Kafka
zookeeper:
  address: ${ZOOKEEPER_ADDRESS:localhost:2181}
kafka:
  bootstrap:
    addresses: ${KAFKA_ADDRESSES:localhost:9092}
  topic:
    contractEvents: contract-events
    blockEvents: block-events
    eventeumEvents: eventeum-events
    transactionEvents: transaction-events

    partitions: 1
    replicationSets: 1

management:
  endpoints:
    web.base-path: /monitoring
    enabled-by-default: false
    web.exposure.include: "*"
  endpoint:
    health:
      enabled: true
      show-details: always
    metrics:
      enabled: false
    prometheus:
      enabled: false
  metrics:
    export:
      prometheus:
        enabled: false

[hacks1ash]

We have changed the brach to development merged with our code It is working without any problem. We have 10% usage on CPU and also RAM is doing well. Is there any problem using development Version? We are seeing orphan blocks is that problem? Is there any problem not saving contractEventDetails cause we have another way to save the transactions for our own purpose?

[craigwilliams84]

Node load should be significantly reduced with release 0.9.0…please feel free to open again if you are still having issues.