Quote from: 3DPass on August 15, 2024, 06:40:25 AM

Quote from: chum_yum on August 07, 2024, 02:23:32 PM

I'd like to share a few tricks that might help someone adjust the miner velocity to the Node performance, which wasn't apparent at the beginning.

That's what I figure out dealing with that during my experiment:
--
Embedded miner:

I changed the limits in the miner.js this way:
https://github.com/3Dpass/3DP/blob/1c696ee89ce4acc3274209aab8bc7ec597bfc4f5/miner.js#L17

Code:

const MIN_INTERVAL = 100;
const MAX_INTERVAL = 10000;
const ADJUSTMENT_PERCENT = 10;

If you need to load your machine even greater, just decrease the MIN_INTERVAL value to 10 mSec/object or smaller. Like this:

Code:

const MIN_INTERVAL = 10;
const MAX_INTERVAL = 10000;
const ADJUSTMENT_PERCENT = 10;

Making adjustments on the max limit (ex. MAX_INTERVAL = 100000 sets up the miner velocity at 100 sec/object)

---
Another miner

In order to adjust this good old miner https://github.com/3Dpass/miner
Just set up fix interval manually:

Code:

yarn miner --interval 10

Could you share any result? Increasing on CPU performance can help to some extent, but there is a memory bottleneck..

It's not as impressive, ~ x1.5, I think. What is the purpose for the bottleneck to exist, btw?