deso-protocol / deso-protocol/backend

CPU issues with running TESTNET backend/scripts/nodes/n0_test

Open
#91 3 comments 0 reactions 0 assignees View on GitHub
Dominant language
Go
Stars
139
Forks
84
PR merge metrics
No merged PRs in 30d

Description

Running this `n0_test` script is great. I get new blocks produced quickly, don't have to wait for a full MAINNET to sync and free money!

I'm able to use the `starter-bitclout-seed` words to post new messages as it has plenty of clout available. But my CPU is pegged. It makes too many blocks and gives me too much free money.

Is there anyway to run it with a max CPU setting? I don't want it to take any significant resources from my dev machine.

Contributor guide

No contributing guide indexed for this repository

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.