As I asked before .. how does Phoenix calculate local hashrate?
I observed that at aggression 7 I can get 430MH/sec, while at aggression 10 I can get only 405, but at this lower local hashrate I am able to finish succesfully more work shares than at aggression 7 (tested for half a day, card compared to card, etc.).
So, better aggression yields in hotter GPU and better yield, while the local hashrate is actually reported lower.
Topic: Phoenix - Efficient, fast, modular miner - page 38. (Read 760761 times)
I just downloaded this. When I open the application the cmd window just opens for a split second then closes. What did I do wrong?
As it is, any failed RPC operation will put Phoenix into "retry connection" mode, where it retries at 15 second intervals.
1.46 has been released which fixes the idle problem.
FYI, I'm going to reuse those 15 BTC in a new bounty to help close this bug and bring true persistent connections to Twisted's HTTP client.
Whoever helps the Twisted team to get that bug closed will get 15 BTC from me.
Whoever helps the Twisted team to get that bug closed will get 15 BTC from me.
You should open separate thread in marketplace or technical discussion - 15 BTC is going to be serious wealth 
and I'm sure there are some skilled programmers interested in getting their first bitcoins for some fun with Twisted... jedi95, I tested new version and works perfecly on my pool. Thanks a lot, 15 BTC on the way!
FYI, I'm going to reuse those 15 BTC in a new bounty to help close this bug and bring true persistent connections to Twisted's HTTP client.
Whoever helps the Twisted team to get that bug closed will get 15 BTC from me.
We have isolated the cause of the idle problem and corrected it. If nothing goes wrong in testing this will be released as 1.46 shortly.
version 1.45
2200+ accepted, 0 Rejected.
-k poclbm DEVICE=0 VECTORS BFI_INT AGGRESSION=10
2200+ accepted, 0 Rejected.
-k poclbm DEVICE=0 VECTORS BFI_INT AGGRESSION=10
So I am still using 1.3 on one of my machines since Its complicated to access the desktop right now. Am I missing out on anything (aside from the fastloop fix) on the newer versions?
It's probably best to avoid 1.45 until they fix the idling issue.
So I am still using 1.3 on one of my machines since Its complicated to access the desktop right now. Am I missing out on anything (aside from the fastloop fix) on the newer versions?
I am having idle problem with 1.45 as well. I am running a GTX 460 with -k poclbm vectors FASTLOOP AGGRESSION=4
ETA for CUDA? 
I think there is something wrong with 1.45. I get a "work is idle" error with slush's pool. Once this error comes up (I think it's happening at random or after a certain period of time) it won't resume hashing. With guiminer I have no problems.
same problemI can confirm, it start to idle after some time (but previously reported connection troubles are solved with this release).
I'm looking into this now.
I think there is something wrong with 1.45. I get a "work is idle" error with slush's pool. Once this error comes up (I think it's happening at random or after a certain period of time) it won't resume hashing. With guiminer I have no problems.
same problemI can confirm, it start to idle after some time (but previously reported connection troubles are solved with this release).
I think there is something wrong with 1.45. I get a "work is idle" error with slush's pool. Once this error comes up (I think it's happening at random or after a certain period of time) it won't resume hashing. With guiminer I have no problems.
same problem I think there is something wrong with 1.45. I get a "work is idle" error with slush's pool. Once this error comes up (I think it's happening at random or after a certain period of time) it won't resume hashing. With guiminer I have no problems.
That message works differently in Phoenix compared to other miners. With poclbm that message is displayed on the last line in the console window replacing the status bar. Phoenix just displays this as a normal log entry and sets the hashrate in the display to 0. Are you getting constant 0 hashrate when this happens or only the message in the log?
Would it be possible to show on the bottom line which OpenCL device is being used? I've got a 6990, which has 2 GPUs on one card. I run two instances of phoenix via batch file and can't tell them apart.
jedi95, I tested new version and works perfecly on my pool. Thanks a lot, 15 BTC on the way!
is there any possible downside to using fastloop with, say, aggression 12?
Well, the number of internal loop iterations is recalculated several times a second, which will always just be 1 at AGGRESSION=12. It won't decrease your hashrate but it will use extra CPU cycles. It's probably better to disable it since there will be 0 hashrate gain.
Also:
FASTLOOP is now on by default so you will need to specify FASTLOOP=false to disable it. The options are fairly flexible so false/FALSE/f/n/no are all accepted values for disabling it.
Jump to: