I'm averaging just around 29 points per hour with this cpu. Full resources committed .. running Linux .. at 4.5Ghz. My newer Ryzen 5700's produce considerably more, over 52. Are there optimizations (SSE,AVX, etc) missing with the i7 which explains the considerable difference?

The differences aren't nearly as pronounced in other projects like TN-Grid or Universe.

I'm averaging just around 29 points per hour with this cpu. Full resources committed .. running Linux .. at 4.5Ghz. My newer Ryzen 5700's produce considerably more, over 52. Are there optimizations (SSE,AVX, etc) missing with the i7 which explains the considerable difference?

The differences aren't nearly as pronounced in other projects like TN-Grid or Universe.

My R9 3900 averages about 40 so that sounds about right.

My R9 3900 averages about 40 so that sounds about right.

Right, within project. But with TN-Grid or Universe the difference is at most 10% to 15%. What makes SiDock so different?

My R9 3900 averages about 40 so that sounds about right.

Right, within project. But with TN-Grid or Universe the difference is at most 10% to 15%. What makes SiDock so different?

40 credits an hour seems to be normal across the projects I work. Sometimes better when a new type of task is introduced but there or thereabouts.

40 credits an hour seems to be normal across the projects I work. Sometimes better when a new type of task is introduced but there or thereabouts.

In looking back at previous work for this project .. before the long work units .. the production with this hardware was considerably more. I would like to ask the developer what has changed, possibly with optimizations, to explain the reduced point awards. Also, I encourage others that have similar hardware to look back using something like boincstats to either confirm or deny what I'm seeing.

Hello! Algorithm for credit estimation and granting have not changed.

The i7 hasn’t completed anywhere near as many tasks as the Ryzens, so its measured processing rate for the new “long tasks” application version is still lagging (4.1 GFLOPS vs. 7.3, at the time of writing). The moving average from which credit is calculated is quite heavily filtered, so it will take several weeks to stabilise.

As a wise person counselled in the other thread about credit consistency:

People just need to exercise a bit of patience.

The i7 hasn’t completed anywhere near as many tasks as the Ryzens, so its measured processing rate for the new “long tasks” application version is still lagging (4.1 GFLOPS vs. 7.3, at the time of writing). The moving average from which credit is calculated is quite heavily filtered, so it will take several weeks to stabilise.

As opposed to stabilization which took under 5 days in your disingenuous apples vs oranges comparison versus the roughly 35 days which has already elapsed (add 2 more weeks according to you) running the newer units due to inherent optimizations either missing or not utilized which reduces the data set?

Don't quote me about patience.