Okay, I understand that perfectly and thank you for these clear and precise explanations.
Sincerely,
/ 
Reply
Quote
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.
Looks like in the last day or so we had switched to a higher range number? "74-75_262-405M" On my high-end card these are running for 3 minutes 52 seconds and we are receiving 5400 credits.
In the post I have quoted I was receiving 300 more credits for roughly 60 seconds less runtime. Not criticising just pointing out
/ Reply
Quote
We are currently processing tasks in the following range. TF_74-75_517-532M On a high-end RTX 4080 tasks are running 1 minute and 18 seconds and being given 3,900 credits. Perhaps it's too early to ask, I am curious how far away we are before credits will increase again/moving back to a higher range?
/ Reply
Quote
rebirtherVolunteer moderator
Project administrator
Project developer
Project tester
Project scientist
Send message
Joined: 2 Jan 13
Posts: 7431
Credit: 42,730,867
RAC: 0
We are currently processing tasks in the following range. TF_74-75_517-532M On a high-end RTX 4080 tasks are running 1 minute and 18 seconds and being given 3,900 credits. Perhaps it's too early to ask, I am curious how far away we are before credits will increase again/moving back to a higher range?
only in next bitlvl, the higher the range the lower the credits = less runtime
/ Reply
Quote
only in next bitlvl, the higher the range the lower the credits = less runtime
Yes sorry I mean when we move to lower range which means higher the credits = more run time. Do you know how many bits levels we have got to go before going to a lower range & any idea how far away the next bit level is?
/ Reply
Quote
rebirtherVolunteer moderator
Project administrator
Project developer
Project tester
Project scientist
Send message
Joined: 2 Jan 13
Posts: 7431
Credit: 42,730,867
RAC: 0
only in next bitlvl, the higher the range the lower the credits = less runtime
Yes sorry I mean when we move to lower range which means higher the credits = more run time. Do you know how many bits levels we have got to go before going to a lower range & any idea how far away the next bit level is?
If we are reaching 900M+ range.
/ Reply
Quote
only in next bitlvl, the higher the range the lower the credits = less runtime
Yes sorry I mean when we move to lower range which means higher the credits = more run time. Do you know how many bits levels we have got to go before going to a lower range & any idea how far away the next bit level is?
If we are reaching 900M+ range.
Thank you, we have a way to go
/ Reply
Quote
74-75_562-577M taking 1 minute 13 seconds 3,600 credits
/ Reply
Quote
74 – 75_622 – 637M taking 1 minute 09 seconds 3,400 credits
/ Reply
Quote
74-75_682-697M taking 1 minute 03 seconds 3,000 credits
/ Reply
Quote
74-75_758-773M taking 58 seconds 2,900 credits
/ Reply
Quote
74-75_799-810M taking 54 seconds 2,700 credits
/ Reply
Quote
74-75_868-885M & 74-75_885-904M taking 50 seconds 2,500 credits
/ Reply
Quote
75-76_136-141M taking 8 minutes 59 seconds 26,500 credits
/ Reply
Quote
75-76_139-147Mtaking 8 minutes 32 seconds 26,500 credits
/ Reply
Quote
75-76_144-149Mtaking 8 minutes 25 seconds 26,500 credits
/ Reply
Quote
75-76_149-153Mtaking 8 minutes 14 seconds 26,500 credits
/ Reply
Quote