Riecoin Forum

Hello

I ve an old raspberry pi 3b that i was not using so i ve looked for a project that can be usefull.
And i ve discovered your project where i ve decides to mine:

Raspberry pi 3b config:
arm7 BCM2835
cpu 1.2g
ram 1G

Here is my configuration:
Threads = 4
PrimeTableLimit = 536870912
SieveWorkers = 1
SieveBits = 11
SieveIterations = 16

Logs:
Primorial Factor Max: 32768
Primorial Number: 121
Primorial: p121# = 661# = ~1.291504052453*10^278 (924 bits)
Primorial Offsets: 92
Prime index threshold: 3512
Estimated additional factors: 151130 (allocated per iteration: 10099)
Precomputing modular inverses...
Tables of 28192629 modular inverses generated in 17.5071 s (112771000 bytes).
Allocating 256 bytes for the primorial factors tables...
Allocating 98336 bytes for the primorial factors...
Allocating 646336 bytes for the additional primorial factors...
Done initializing miner.
Starting the miner's master thread...
Starting 4 miner's worker threads...
-----------------------------------------------------------
[0:00:00:00.0] Started Benchmark, difficulty 1024.000
[0:00:00:30.0] 1.67 c/s, r 25.00 ; (1-7t) = (2 0 0 0 0 0 0)
[0:00:01:00.0] 1.33 c/s, r 26.67 ; (1-7t) = (3 0 0 0 0 0 0)
[0:00:01:30.0] 1.57 c/s, r 35.25 ; (1-7t) = (4 0 0 0 0 0 0)
[0:00:02:00.0] 1.72 c/s, r 25.88 ; (1-7t) = (8 0 0 0 0 0 0)
[0:00:02:30.0] 1.76 c/s, r 24.00 ; (1-7t) = (11 0 0 0 0 0 0) | 82.603 y
[0:00:02:35.9] Block 2, average 156.0 s, difficulty 1024.000
[0:00:03:00.0] 1.49 c/s, r 24.36 ; (1-7t) = (11 0 0 0 0 0 0) | 108.480 y
[0:00:03:30.0] 1.57 c/s, r 27.42 ; (1-7t) = (12 0 0 0 0 0 0) | 235.575 y
[0:00:04:00.0] 1.48 c/s, r 29.58 ; (1-7t) = (12 0 0 0 0 0 0) | 424.922 y
[0:00:04:30.0] 1.55 c/s, r 26.19 ; (1-7t) = (16 0 0 0 0 0 0) | 172.507 y
[0:00:05:00.0] 1.63 c/s, r 25.68 ; (1-7t) = (19 0 0 0 0 0 0) | 143.667 y
[0:00:05:11.2] Block 3, average 155.6 s, difficulty 1024.000
[0:00:05:30.0] 1.49 c/s, r 25.95 ; (1-7t) = (19 0 0 0 0 0 0) | 167.999 y
[0:00:06:00.0] 1.45 c/s, r 23.77 ; (1-7t) = (22 0 0 0 0 0 0) | 93.614 y
[0:00:06:30.0] 1.50 c/s, r 25.52 ; (1-7t) = (23 0 0 0 0 0 0) | 148.519 y
[0:00:07:00.0] 1.55 c/s, r 27.12 ; (1-7t) = (24 0 0 0 0 0 0) | 220.921 y
[0:00:07:30.0] 1.58 c/s, r 28.48 ; (1-7t) = (25 0 0 0 0 0 0) | 304.434 y
[0:00:07:40.7] Block 4, average 153.6 s, difficulty 1024.000
[0:00:08:00.0] 1.50 c/s, r 26.63 ; (1-7t) = (27 0 0 0 0 0 0) | 200.931 y
[0:00:08:30.0] 1.46 c/s, r 27.67 ; (1-7t) = (27 0 0 0 0 0 0) | 268.488 y
[0:00:09:00.0] 1.49 c/s, r 27.83 ; (1-7t) = (29 0 0 0 0 0 0) | 274.046 y

Is anyone tried with Raspberry pi 3b ? Do you think the configuration is optimized? Or can it more accurated ?

Thks

Welcome!

[0:00:09:00.0]1.49 c/s, r 27.83 ; (1-7t) = (29 0 0 0 0 0 0) | 274.046 y

There is probably an issue with the configuration as more than 270 years to find a 7-tuple at Difficulty 1024 is orders of magnitudes too high. For reference, it is about 10 days for the RasbBerry Pi 4 in these conditions.
With good settings, you should be able to reach about 20-30 days.

Unfortunately, I don't have the 3B to make tests myself to find optimal values.

I don't have a 3B either, but my 4b does best at sieve bits = 22. My results are:
....
[13:48:05.2] 1501.17 c/s, r 17.09 ; Sh: 12/12 (100.0%) | 3.8 RIC/d
[13:48:08.6] 5-share found by worker thread 2
[13:48:35.2] 1472.08 c/s, r 17.07 ; Sh: 13/13 (100.0%) | 3.8 RIC/d
...

I think you should be getting about half this performance with a 3b.
If you aren't running 64 bit OS, you need to upgrade. Try increasing the sieve bit value.

My .conf file:

Threads = 0
PrimeTableLimit = 536870912
SieveWorkers = 1
SieveIterations = 0
SieveBits = 22

Good luck!