Topic: Phoenix - Efficient, fast, modular miner - page 28. (Read 760839 times)

Thanks!

Using: -k phatk DEVICE=0 VECTORS BFI_INT FASTLOOP=false WORKSIZE=256 AGGRESSION=13 on a single 5830 and get 312MH/sec
 

I started using the latest command line version of poclbm on Windows 7 x64 and I am getting about the same performance, but it is known to reconnect more reliably [although when I used it with GUIMiner, it didn't always reconnect using the version from late March when I tested it and had the issue] and I am getting FAR fewer stale shares than with phoenix.  I have command scripts to allow me to switch miners and pools at will.  I was seeing 1.0 - 1.5% rejected shares with phoenix (more when there were pool problems) while I am seeing about 0.5% using poclbm with a relatively small share sample (about 1200 so far).  I am pretty sure it is the long polling code in phoenix that is causing the additional stale shares and it is certainly causing the recent crashes [why did that suddenly start in the last few days and not before ... I was using 1.48 since it was released but only saw the LP crash for the first time this morning on both machines at the same time (about 2:30AM CDT with deepbit.net).

I like the way phoenix is configured better and I like the command line output that shows the cumulative accepted/rejected counts better, so I really would prefer to use phoenix, but unfortunately, I cannot do so right now.  

Any word on when a new version is out that has been tested with multiple pools long polling?  I would love to test, but with only two machines [one GPU each], I can't afford to have a miner drop while I am away or sleeping [I work from home a lot, so I can test then easily enough ... I am not sure that up to a 16 hour run is sufficient though].

When phoenix comes around, I will be back with it  Just curious about any progress.  

Thank you.

phoenix is not able to reconnect properly most of the time, right now im using my own programs to monitor it and restart it if the connection is down, and i even implemented a pool switch method too in case if the pool has been down for some time, the nly problem? i need to have thee stats on a plain text file, right now thats a nightmare, the file gets well over 3gb in size after just 24 hours, i need to try to do that phoenix mod ive attemped few days ago to export only stats to a .txt file again.

i am now getting these errors every time i try to run phoenix.  any idea what this means?

This is triggered by something that a few of the pools have done [at least deepbit and BTCMine].  I am sick of waking up to finding that hours have gone by with my miners down [and my GPU sitting at 40%].  I am hooked up to BTC Guild right now and maybe I will have more luck.  However, if this happens again, I am going to have to tweak my machines for pclbm and never look back [too much effort already tweaking machines to run optimally and stably].

I'm mining with a GTS 250 and I get about 28-29m on poclbm but when I use phoenix, I can't get above 23m.  Has anyone else experienced this?  Is phoenix just less efficient with Nvidia cards?

This would work great on Linux. I could even make most of it work on my Windows miner using Cygwin. However, I don't have an equivalent to aticonfig on Windows. Anyone know a good way of getting GPU load into Python (or any scripting language) on Windows/Cygwin?

I got that error too.

Hi again,

After some stracing, I found the bug. It isn't with special chars but rather with long usernames in the URL. phoenix is base64 encoding using some encode function but that function is dropping a newline (\n) character into the base64 stream. That needs to come out else we are sending invalid HTTP headers.

I just saw the error for the first time this morning.  I am very hesitant to change miners since my dedicated machine is now very finely tuned and when I have tried to use GUI Miner I have managed to topple the machine.  I have seen the connection problem referred to above only once.  For me, Phoenix usually recovers even after 10 minutes or so [I had my router down for a bit the other night and all miners resumed when full Internet access was restored.

I get this one every now and again, usually at about 4am in the morning knowing my luck

After few hours of mining on deepbit I get usually the following error msg:

Mine too. Never gets reconnected after pool network failures.

Is there any way to further enhance the reconnecting of phoenix to a pool?
I saw improvements in version 1.48, but if the pool is down for several minutes it seems to never reconnect.

I just found a bug in the long polling code.

It seems that LP fails to work properly if the long polling URL uses a query string (e.g. http://localhost:8332/example?longpoll=example).

Here is the fix:

Just tried to connect to deepbit.net and tada..


It got right back to track just a second after the error..

[719 Accepted] [56 Rejected]

Is this normal?

FASTLOOP is enabled by default in recent Phoenix versions and one must specify FASTLOOP=false in order to disable it.

Open a command window and execute phoenix from a command line and you will see the error it is giving you.

Here is what I use for my workstation that must be responsive (remove FASTLOOP and boost aggression to 11 or 12 for a dedicated machine):


Note that I leave pools that I use commented out so that I can change from one to the other if I want too [for testing or because one is down, or whatever reason].  I should probably pass an argument to "start" so that the original command window doesn't popup, but it doesn't bother me enough to change it.

Hello,
Is there any way to include special characters in the http username string. In poclbm --user "x;y" works but "http://x;y@hostname/" does not. I also tried "http://x%3by@hostname/" but no luck there either.