The runtime will be changed more in the middle. My test is taking around 16min on RX5500XT and 15min in the next range.

I have noticed that credit has jumped up to 1,700 we are processing work in the range of 73– 74_698–709M. Interestingly though these tasks are running for around 51 seconds which was the same as the last lot of work I ran which I think was awarding 1,600 credit unfortunately I cannot remember what range was. I was expecting credit to go down not up especially because it is the same roughly the same amount of runtime & credit has increased. Certainly not a criticism just a observation

Before 1800cr now 1700cr, Iam testing after some time the runtime of a WU on my card, it was a bit lower now thats why the credits were adjusted.

Hello.
I would like to report a problem with the incorrect recalculation of my TF sample(s) from 03/16/2023. I did an experiment with iGPU (Radeon) + dGPU (Radeon). At least one sample has too short a conversion time, and I have incorrectly calculated a score. In my opinion, this is a mistake. Could an admin fix this? At the same time, I warn against such experimentation.

Tasks with the following 74-75_202-207M in their names are giving 10,000 credits. For me they are running for just over 5 minutes however I have a high-end card RTX 3080.
Unfortunately I don't have any tasks so I am not able to get the name credit drop seems to be 2,500 tasks were giving 12,500 credits from memory runtime was around 5 minutes 15 seconds

Tasks with the following 74-75_202-207M in their names are giving 10,000 credits. For me they are running for just over 5 minutes however I have a high-end card RTX 3080.
Unfortunately I don't have any tasks so I am not able to get the name credit drop seems to be 2,500 tasks were giving 12,500 credits from memory runtime was around 5 minutes 15 seconds

Looks different, my RX5500XT test got around 57min while we are now in the next range. Always testing the last number in batch (207M instead of 202M)

Interesting you mention about the credits because I was thinking it was a "large" drop in credit for around 15 seconds of runtime

I have just completed TF_74-75_202-207M_wu_62361_0 Runtime of 301 seconds i think this is the same range as I completed this morning 202 – 207M and not sure how you mean "you refer the runtime from the last batch" unfortunately all of my old results have been deleted,

Yes I understand in regards to purging
I don't recall seeing any tasks from 196 – 202M maybe this took place overnight while my computer was off. Are you able to let me know what the end work unit number is in the batch like "62,361" I am aware the Workunit numbers do not have a, in then

Has been some time since I have given an update on what credit as being given for tasks. We are currently processing tasks in the following range. TF_74-75_366-376M On a high-end RTX 3080 tasks are running between 2 minutes and 53 seconds and 3 minutes and 4 seconds and being given 5,700 credits.

Hello,

I would like to know the reason why all of the WU “TF” disappeared, as well as their validation during the night of this Saturday this Sunday.
In fact, I had 80 WU “TF” to calculate and validate and I found myself with a counter at “0”.

Looking forward to your return, I hope you have a good day.

Sincerely,