1.44. Now uses x restarts per y time to check. It can potentially result in a little longer down time compared to a method that immediately tells if server is down or not, but is a much better indicator than pinging.
Oh, and if you were checking if main server is up every minute or so, it's now probably a better idea to make that interval longer, like at least 15 minutes.
Topic: AOCLBF (was Phoenix Rising): Phoenix/POCLBM GUI With Built-In Overclock Tool - page 11. (Read 147076 times)
June 13, 2011, 04:08:44 PM
June 13, 2011, 02:06:21 PM
Barely Clocked: barebone clock/voltage tweaking.
Time to move back to working on the pool down thing then.
Time to move back to working on the pool down thing then.
June 13, 2011, 11:37:56 AM
I want the option to switch back to the back up MANUALLY also.
Today slush pool was in attack & miner can't able to connect. I already gave deepbit as backup. It doesn't even switch to deepbit, instead keep on restarting in slush server only. Since there is no manual way to switch to back up, i just ran guiminer by giving all the deepbit data for my 3 miners & mining in deepbit so far fine. for the past 3-4 hours.
PR badly needs manual override. Just waiting it to automatically to back up doesn't seems to work when the pools are in Ddos attack.coz the pool responds ping & so the miner believes, it doesn't have to switch to back up.
Manually switching to back up is needed.
You can add a single check box, which will allow all miners to mine in backup miner only. This is the easiest way when pools are in attack.
I agree at least as a temporary solution i think both an idle worker and manual override button are needed. But the most needed feature of all is donation address or link. Today slush pool was in attack & miner can't able to connect. I already gave deepbit as backup. It doesn't even switch to deepbit, instead keep on restarting in slush server only. Since there is no manual way to switch to back up, i just ran guiminer by giving all the deepbit data for my 3 miners & mining in deepbit so far fine. for the past 3-4 hours.
PR badly needs manual override. Just waiting it to automatically to back up doesn't seems to work when the pools are in Ddos attack.coz the pool responds ping & so the miner believes, it doesn't have to switch to back up.
Manually switching to back up is needed.
You can add a single check box, which will allow all miners to mine in backup miner only. This is the easiest way when pools are in attack.
June 13, 2011, 10:02:41 AM
I want the option to switch back to the back up MANUALLY also.
Today slush pool was in attack & miner can't able to connect. I already gave deepbit as backup. It doesn't even switch to deepbit, instead keep on restarting in slush server only. Since there is no manual way to switch to back up, i just ran guiminer by giving all the deepbit data for my 3 miners & mining in deepbit so far fine. for the past 3-4 hours.
PR badly needs manual override. Just waiting it to automatically to back up doesn't seems to work when the pools are in Ddos attack.coz the pool responds ping & so the miner believes, it doesn't have to switch to back up.
Manually switching to back up is needed.
You can add a single check box, which will allow all miners to mine in backup miner only. This is the easiest way when pools are in attack.
Today slush pool was in attack & miner can't able to connect. I already gave deepbit as backup. It doesn't even switch to deepbit, instead keep on restarting in slush server only. Since there is no manual way to switch to back up, i just ran guiminer by giving all the deepbit data for my 3 miners & mining in deepbit so far fine. for the past 3-4 hours.
PR badly needs manual override. Just waiting it to automatically to back up doesn't seems to work when the pools are in Ddos attack.coz the pool responds ping & so the miner believes, it doesn't have to switch to back up.
Manually switching to back up is needed.
You can add a single check box, which will allow all miners to mine in backup miner only. This is the easiest way when pools are in attack.
June 13, 2011, 08:39:17 AM
Damn, deepbit's down again. I definitely vote for this solution: switch to backup after two-three (or more) periods of idling. For example, if I have "Restart after an idle time of 30 seconds" option, switching will be executed after 1+ minutes of idle time.
If you don't like the idea, then I definitely vote for button that forces a client to switch from primary to backup or backup to primary, it was mentioned before by smackdaddy.
That's just too sad to lose 10 minutes of mining when you can lose only one
If you don't like the idea, then I definitely vote for button that forces a client to switch from primary to backup or backup to primary, it was mentioned before by smackdaddy.
That's just too sad to lose 10 minutes of mining when you can lose only one
June 13, 2011, 04:23:13 AM
The temperatures should be the core temperatures, at least they are for my 5850s.
And yeah, still not sure how device numbers are calculated. These numbers are assigned by the driver itself.
Does it at least report correct clock speeds and correct number of GPUs (counting 5970/6990 as 2)?
And yeah, still not sure how device numbers are calculated. These numbers are assigned by the driver itself.
Does it at least report correct clock speeds and correct number of GPUs (counting 5970/6990 as 2)?
June 13, 2011, 03:30:11 AM
Temperatures are not the same as msi afterburner (or rivatuner) is showing. It shows higher values, 74 & 68 respectively. Obviously it uses another gpu sensor. Guess it'd be the right choice for you to use these sensors too
Device numbers are not the right numbers (that are used in settings of your program), they should be 0 and 1, not 0 and 3
June 13, 2011, 02:41:30 AM
Sorry i didn't read through all 12 pages of this but is there a linux version? Ubuntu plz!
Autoit is, and always will be (I think), Windows only! Complain to the devs for that, I'm not good enough 
.Ninja'd a second version of 1.43 on, since I forgot to add the "fix" for the window activation "bug."
Going to ninja another version of 1.43 on
, since I forgot to reduce the refresh rate. June 13, 2011, 02:23:05 AM
Sorry i didn't read through all 12 pages of this but is there a linux version? Ubuntu plz!
June 13, 2011, 02:18:22 AM
http://www.mediafire.com/?ko6eydbeph5itm4
If anyone's feeling like being guinea pigs, run that from command line, and let me know the output, along with how many GPUs you are running (and which GPU # printed from the program corresponds with which GPU number in mining, if you happen to know them or wouldn't mind trying to figure it out). Single GPUs should work fine, but not sure about duals (5970/6990).
Right now, just retrieves clock and temperature info, but it's not too hard to make it an OC tool. If it's reading GPU info correctly, that is.
If anyone's feeling like being guinea pigs, run that from command line, and let me know the output, along with how many GPUs you are running (and which GPU # printed from the program corresponds with which GPU number in mining, if you happen to know them or wouldn't mind trying to figure it out). Single GPUs should work fine, but not sure about duals (5970/6990).
Right now, just retrieves clock and temperature info, but it's not too hard to make it an OC tool. If it's reading GPU info correctly, that is.
June 13, 2011, 01:00:39 AM
I vote share acceptance rate, after all that's the true measure of the value of the mining process.
So, if it's share acceptance rate and not network reachability, how do you decide when to switch back to the primary pool? Perhaps in that scenario of handling failover, you would be able to set a time until the primary is tried again (similar to the current setting), and a configurable period of time during which the primary must accept a share or it goes back to the secondary.
You know what I'd really really love more than anything else for this program? A simple button to force a client to switch from primary to backup or backup to primary. Right now, I do it by swapping ini files.
The other thing I would love would be if the program remembered where your OSDs live. Having to reposition them every time is frustrating.
If you guys are fine with that, then sure. The side effect is that it wouldn't be feasible to have it check if primary is up say every 5 minutes anymore.
I suppose that it's time I upload 1.43, where I fixed some stuff (forgot what, but I did fix them
) and made Save Settings button save current position of OSDs.Also, fun stuff
:
Oh, pretty much have everything in the ADL DLL figured out, finally. I should be able to throw together a very rough GPU clock tool soon.
1.43.
June 12, 2011, 04:20:52 PM
I guess that the problem is this: a pool is responsive to pings, but however (for any reason) it cannot offer you any mining work, so miner is idle. And your program decides to keep trying to mine here and not making an attempt to switch pools. Am I right on this?
Yeah, still can't figure out a better way of checking if pool is down or not. So, it's either ping or checking for share acceptance rate, unless someone comes up with a better idea, preferable one that doesn't need separate implementations for different pools.I vote share acceptance rate, after all that's the true measure of the value of the mining process.
So, if it's share acceptance rate and not network reachability, how do you decide when to switch back to the primary pool? Perhaps in that scenario of handling failover, you would be able to set a time until the primary is tried again (similar to the current setting), and a configurable period of time during which the primary must accept a share or it goes back to the secondary.
You know what I'd really really love more than anything else for this program? A simple button to force a client to switch from primary to backup or backup to primary. Right now, I do it by swapping ini files.
The other thing I would love would be if the program remembered where your OSDs live. Having to reposition them every time is frustrating.
June 12, 2011, 02:22:56 PM
Maybe it would be a nice idea to redraw the text when it actually needs to be redrawn (right now it redraws even without any needs)? When some stats have actually changed — accepted/rejected shares counter has increased or mhash/s performance has changed (with the given accuracy, like, 300 became 299 or so).
Yeah, I'll need to make another global constant then 
, which I really don't want to do. I'll just make it refresh every half/one second or something.I guess that the problem is this: a pool is responsive to pings, but however (for any reason) it cannot offer you any mining work, so miner is idle. And your program decides to keep trying to mine here and not making an attempt to switch pools. Am I right on this?
Yeah, still can't figure out a better way of checking if pool is down or not. So, it's either ping or checking for share acceptance rate, unless someone comes up with a better idea, preferable one that doesn't need separate implementations for different pools. June 12, 2011, 01:07:22 PM
Quote
The blinking part is when its redrawing the text. It might be hardware acceleration-prone, not sure. I can turn down the refresh rates a bit so the blinking isn't as severe.
Maybe it would be a nice idea to redraw the text when it actually needs to be redrawn (right now it redraws even without any needs)? When some stats have actually changed — accepted/rejected shares counter has increased or mhash/s performance has changed (with the given accuracy, like, 300 became 299 or so).Quote
If miner idles (hashrate~0 or phoenix hasn't sent out text updates, which it does every time it refreshes hashrate/accepted/rejected, etc.) more than the set time and not responsive to pings.
I'll eventually add an option to use x accepted shares in y minutes, unless someone has better ideas.
I guess that the problem is this: a pool is responsive to pings, but however (for any reason) it cannot offer you any mining work, so miner is idle. And your program decides to keep trying to mine here and not making an attempt to switch pools. Am I right on this? I'll eventually add an option to use x accepted shares in y minutes, unless someone has better ideas.
Quote
I did finally figure out how to initialize ADL (finally!).
Well, that's truly great June 12, 2011, 11:55:38 AM
Wow, what a great tool! Thank you!
Two things:
— There are some moments when OSD is constantly blinking almost every second (no matter is click-through on or off), which is kinda annoying. Didn't figure out what causes this. Windows 7, aero disabled.
— I'm sure you know that device finder doesn't really show the correct device numbers
And minor things:
— It would be good if password was stored like this: "*************".
— Maybe would be also good to let the user to hide OSD when he needs to. Like, some checkbox "show OSD" or something.
— Desktop lag is more significant compared to the usual phoenix with the same settings.
The blinking part is when its redrawing the text. It might be hardware acceleration-prone, not sure. I can turn down the refresh rates a bit so the blinking isn't as severe.Two things:
— There are some moments when OSD is constantly blinking almost every second (no matter is click-through on or off), which is kinda annoying. Didn't figure out what causes this. Windows 7, aero disabled.
— I'm sure you know that device finder doesn't really show the correct device numbers
And minor things:
— It would be good if password was stored like this: "*************".
— Maybe would be also good to let the user to hide OSD when he needs to. Like, some checkbox "show OSD" or something.
— Desktop lag is more significant compared to the usual phoenix with the same settings.
I'll get around to those eventually, still messing with ADL
.Or, and some more: is it possible not to switch focus to the new phoenix window? I mean, can it be done without losing focus to the application I'm currently in? Sorry for weird words, don't know how to correctly say that.
Yeah, it's not as seamless as I liked, even when launching phoenix without the cmd window ever showing. I can set it to retrieve last-active application, and reactivate that after launching though.Sorry for almost-quadruple-posting, but this is really important.
How long does it take to switch to the backup pool? I can't figure it out myself.
Considering some pools are experiencing ddos nowadays (especially deepbit), it becomes crucial to switch to another, backup pool at the right time.
Once I noticed that switching happened after one minute of idling. But now it takes much longer for some reason.
I would really appreciate if you, lvlrdka22, let users change this amount of time in settings.
If miner idles (hashrate~0 or phoenix hasn't sent out text updates, which it does every time it refreshes hashrate/accepted/rejected, etc.) more than the set time and not responsive to pings.How long does it take to switch to the backup pool? I can't figure it out myself.
Considering some pools are experiencing ddos nowadays (especially deepbit), it becomes crucial to switch to another, backup pool at the right time.
Once I noticed that switching happened after one minute of idling. But now it takes much longer for some reason.
I would really appreciate if you, lvlrdka22, let users change this amount of time in settings.
I'll eventually add an option to use x accepted shares in y minutes, unless someone has better ideas.
I did finally figure out how to initialize ADL (finally!).
June 12, 2011, 11:28:27 AM
Sorry for almost-quadruple-posting, but this is really important.
How long does it take to switch to the backup pool? I can't figure it out myself.
Considering some pools are experiencing ddos nowadays (especially deepbit), it becomes crucial to switch to another, backup pool at the right time.
Once I noticed that switching happened after one minute of idling. But now it takes much longer for some reason.
I would really appreciate if you, lvlrdka22, let users change this amount of time in settings.
How long does it take to switch to the backup pool? I can't figure it out myself.
Considering some pools are experiencing ddos nowadays (especially deepbit), it becomes crucial to switch to another, backup pool at the right time.
Once I noticed that switching happened after one minute of idling. But now it takes much longer for some reason.
I would really appreciate if you, lvlrdka22, let users change this amount of time in settings.
June 12, 2011, 07:21:41 AM
I think I've discovered the reason why Phoenix Rising has started to put out such low hashrates compared to before. Checking the PR.log file the default argument is now missing the VECTOR flag.
Manually adding VECTOR into the "other flag" field brought hashrate back up to its original levels. If you could have it automatically add that flag in the next version that'd be great. Or a check box?
I think he actually told about it a couple of times Manually adding VECTOR into the "other flag" field brought hashrate back up to its original levels. If you could have it automatically add that flag in the next version that'd be great. Or a check box?
Checkbox's good. Autovectors - not good, I think, because I would want to set all flags by myself.
June 12, 2011, 06:44:02 AM
I think I've discovered the reason why Phoenix Rising has started to put out such low hashrates compared to before. Checking the PR.log file the default argument is now missing the VECTOR flag.
Manually adding VECTOR into the "other flag" field brought hashrate back up to its original levels. If you could have it automatically add that flag in the next version that'd be great. Or a check box?
Manually adding VECTOR into the "other flag" field brought hashrate back up to its original levels. If you could have it automatically add that flag in the next version that'd be great. Or a check box?
June 12, 2011, 06:34:37 AM
Oh, and some more: is it possible not to switch focus to the new phoenix window? I mean, can it be done without losing focus to the application I'm currently in? Sorry for weird words, don't know how to correctly say that.
June 12, 2011, 04:16:59 AM
Wow, what a great tool! Thank you!
Two things:
— There are some moments when OSD is constantly blinking almost every second (no matter is click-through on or off), which is kinda annoying. Didn't figure out what causes this. Windows 7, aero disabled.
— I'm sure you know that device finder doesn't really show the correct device numbers
And minor things:
— It would be good if password was stored like this: "*************".
— Maybe would be also good to let the user to hide OSD when he needs to. Like, some checkbox "show OSD" or something.
— Desktop lag is more significant compared to the usual phoenix with the same settings.
Two things:
— There are some moments when OSD is constantly blinking almost every second (no matter is click-through on or off), which is kinda annoying. Didn't figure out what causes this. Windows 7, aero disabled.
— I'm sure you know that device finder doesn't really show the correct device numbers
And minor things:
— It would be good if password was stored like this: "*************".
— Maybe would be also good to let the user to hide OSD when he needs to. Like, some checkbox "show OSD" or something.
— Desktop lag is more significant compared to the usual phoenix with the same settings.
Jump to: