Quote Originally Posted by Fire$torm View Post
No, the code is open source so you are correct. The thing is DA is in the process of eliminating the possibility of being able to add an alternate credit schema to the code by making other various essential elements of the code dependent on the CreditNew code.

Bottom line: In the near future if a project does not want to use CreditNew then they will have to do some serious rewrite of a good portion of the server code. Since many projects do not have the time/patience/skill to do that, CreditNew will be the de-facto standard.
For Collatz, I just let all the creditNew code run right before it updates the database, I change the credit value. The project thinks it is running the creditNew, but it actually uses the fixed credit. Unless DA changes it so that all credit is stored centrally, I don't think there is anything he can do to stop that from working. Projects that award credit according to GFLOPS and not some type of fixed credit will require a lot more code since DA has removed some of the estimated and client reported GFLOPS values returned with the workunits. The creditNew uses the time crunched along with the benchmarks to calculate the credit. Grabbing the GFLOPS from the database for that host and calculating the GFLOPS by using the compute time would work, but would be messy and require quite a few code changes.

Since AMD has stated that CAL/Brook will no longer work in future releases even though OpenCL favors nVidia, Collatz will need to support OpenCL even though OpenCL performance sucks compared to CAL. OpenCL either runs 50% slower, uses 100% CPU even when doing asynchronous calls, or both. OpenCL support will require upgrading to the latest server code, so I'll find out then how hard it is to still bypass creditNew at that time.