Quote from: BiticaMan on July 30, 2022, 04:50:20 PM

Quote from: jack1cryptotalk007 on July 30, 2022, 11:36:54 AM

Quote from: kurutoga on July 29, 2022, 06:55:56 PM

For reference, I'm running three sticks on a pi with the following metrics:

Stick 1: 335 MHz (38:19)
Stick 2: 400 MHz (32:16)
Stick 3: 400 MHz (32:16)

My first time hearing about this setting, so I am also curious if it's a problem that the computer can't process a task within the USB's task time? Or if I am understanding that correctly. What is a use case for the numbers?

It just indicates the performance issue, which process (hashing out) less block header data within the expectation of usb stick's capability. Then, chance to hit a BTC is reduced. (32:16) indicate, it took 32 milliseconds average time to process a header data. (8:16) indicate, it took 8 milliseconds average time for hashing process (sub tasks: check status of usb stick and process, obtain header data, format data, write data to usb stick, etc). Sometime, checking usb status cost time when usb stick does not work well.

cgminer is an multiple threads program. More usb sticks are used, more process threads will be created and running there, which compete limited system resources. You can test if a PI 4 computer can handle how many of compacf sticks without impact the performance of whole system to achieve (8:16).

Can you get to 8:16 with 400mhz?

I see that when I increase the mhz this value 28:14 is decreased, however the lower the mhz this value gets higher.
If so, it's not the system alone that leaves this value lower, but how much mhz you can leave in your compacF?

Yes. my one is (5:21) for compac f stick. I post a screenshot here on this link https://postimg.cc/HjNM70bK