# Rewards vs plotts-size bug

**URL:** <https://forum.autonomys.xyz/t/rewards-vs-plotts-size-bug/1488>\
**Category:** Support\
**Tags:** gemini-3d\
**Created:** [May 10, 2023, 9:34pm UTC](https://forum.autonomys.xyz/t/rewards-vs-plotts-size-bug/1488 "2023-05-10T21:34:43Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![user7](https://yyz1.discourse-cdn.com/flex011/user_avatar/forum.autonomys.xyz/user7/32/257_2.png) [@user7](https://forum.autonomys.xyz/u/user7)\
**Post date:** [May 10, 2023, 9:34pm UTC](https://forum.autonomys.xyz/t/rewards-vs-plotts-size-bug/1488/1 "2023-05-10T21:34:43Z")

</div>

## Issue Report

As promised earlier, here are some bugs.

1. This is really true, tested on different configurations. The main problem is large plotts. The reward for rafts larger than ±130Gb drops a lot. It gets to the point where 100G rafts yield more than 200G rafts. This feature was noticed on the following configurations:

- 2\*2696v3/128Gb/first disk - nvme (OS + node), second disk - nvme (plotts only)
- 2\*2696v3/128Gb/first disk - nvme (OS + node), second disk - ssd-sata (plotts only)
- 2\*2696v3/128Gb/first disk - nvme (OS), second disk - ssd-sata (node), third disk - nvme (plotts only)
- 2\*2696v3/128Gb/first disk - nvme (OS), second disk - ssd-sata (node), third disk - ssd-sata (plotts only)
- ryzen 9 5950x/128Gb/first disk - nvme (OS + node), second disk - ssd-nvme (plotts only)
- ryzen 9 5950x/128Gb/first disk - nvme (OS + node), second disk - ssd-sata (plotts only)
- xeon e3-1280v5/16Gb/first disk - nvme (OS + node), second disk - ssd-sata (plotts only)
- i7-3660qm/8Gb/first disk - ssd-sata (OS+node), second disk - ssd-sata
- i3-7320/40Gb DDR4/ssd-nvme (OS+node+plotts)  
Ubuntu 20.04-22.04 installed everywhere.  
All internet lines have speeds of at least 100 megabits per second, the number of peers ± the same, but there is such a peculiarity. It does not depend on client version: cli or advanced - it does not matter.

1. CLI - version, in startup mode “subspace-cli farm --verbose”. First the node is synchronized, then the farmer MUST START synchronizing. But if you don’t restart the process, farmer synchronization doesn’t start.

Best regards

---

<div class="post-metadata">

**Author:** ![ImmaZoni](https://yyz1.discourse-cdn.com/flex011/user_avatar/forum.autonomys.xyz/immazoni/32/7_2.png) [@ImmaZoni](https://forum.autonomys.xyz/u/ImmaZoni)\
**Post date:** [May 11, 2023, 4:23pm UTC](https://forum.autonomys.xyz/t/rewards-vs-plotts-size-bug/1488/2 "2023-05-11T16:23:02Z")

</div>

Thanks for the feedback and testing results!

@nazar-pc tagging in case any of this is helpful with large plots

@user7 in regards to the cli issue, is this on the latest 4.1 version?

---

<div class="post-metadata">

**Author:** ![nazar-pc](https://yyz1.discourse-cdn.com/flex011/user_avatar/forum.autonomys.xyz/nazar-pc/32/6_2.png) [@nazar-pc](https://forum.autonomys.xyz/u/nazar-pc)\
**Post date:** [May 11, 2023, 4:43pm UTC](https://forum.autonomys.xyz/t/rewards-vs-plotts-size-bug/1488/3 "2023-05-11T16:43:43Z")

</div>

I think this is related to audit performance, if audit doesn’t complete in time, reward can’t be claimed.  
Things will be different in upcoming Gemini 3e, we’ll revisit this then.