Topic: Phoenix - Efficient, fast, modular miner - page 39. (Read 760839 times)
is there any possible downside to using fastloop with, say, aggression 12?
Works perfectly with bitcoinpool now. With 1.40 i got 8-10% rejects. Not a single reject so far. This just got awesomer. I guess the keep-alives really did the trick. Thanks alot.
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.
Donations
129ZQG33GmqYRVSCw2hw7zmDUCvvMsuGbC
http://blockexplorer.com/q/getreceivedbyaddress/129ZQG33GmqYRVSCw2hw7zmDUCvvMsuGbC says: 65.88207230129ZQG33GmqYRVSCw2hw7zmDUCvvMsuGbC
Not bad. Sent some more as thanks for BFI_INT.
Version 1.45 has been released.
Changes:
1. FASTLOOP modified to use dynamic number of internal loops (should be faster, and now works at any aggression without causing stale shares)
2. RPC now uses keep-alive (should resolve issues with Slush's pool)
FASTLOOP is now recommended at any AGGRESSION level for non-dedicated miners (any card outputting to a monitor that is used and not just a dummy plug)
Using it with dedicated miners at high AGGRESSION still won't improve performance, but it no longer causes stale shares. If for some reason you have a dedicated miner at low aggression then FASTLOOP should improve hashrate.
Changes:
1. FASTLOOP modified to use dynamic number of internal loops (should be faster, and now works at any aggression without causing stale shares)
2. RPC now uses keep-alive (should resolve issues with Slush's pool)
FASTLOOP is now recommended at any AGGRESSION level for non-dedicated miners (any card outputting to a monitor that is used and not just a dummy plug)
Using it with dedicated miners at high AGGRESSION still won't improve performance, but it no longer causes stale shares. If for some reason you have a dedicated miner at low aggression then FASTLOOP should improve hashrate.
one question, there is some way to "export" the hash rate to a .txt file?
[...]
Are you using the trunk version? The code in the trunk right now doesn't support http_proxy. 1.4 does (and 1.45 will) use
Twisted for the HTTP requests, which presumably supports http_proxy.
No I'm using version 1.4 .Are you using the trunk version? The code in the trunk right now doesn't support http_proxy. 1.4 does (and 1.45 will) use
Twisted for the HTTP requests, which presumably supports http_proxy.
Hmm how did you configure this?
Hello!
Is there a way to access a pool with phoenix.py through a local proxy client or a proxy?
Situation:
I am under Linux and I have access to a small proxy pool which is accessed through a local client listening on a port on my localhost.
When I test it with:
export http_proxy="127.0.0.1:" wget http:///
the proxy client shows traffic and all is fine.
But when I try
export http_proxy="127.0.0.1:" ./phoenix.py
then there is no traffic on the proxy client so I guess it is a direct connect to the server.
Is there a solution?
Is there a way to access a pool with phoenix.py through a local proxy client or a proxy?
Situation:
I am under Linux and I have access to a small proxy pool which is accessed through a local client listening on a port on my localhost.
When I test it with:
export http_proxy="127.0.0.1:
the proxy client shows traffic and all is fine.
But when I try
export http_proxy="127.0.0.1:
then there is no traffic on the proxy client so I guess it is a direct connect to the server.
Is there a solution?
Are you using the trunk version? The code in the trunk right now doesn't support http_proxy. 1.4 does (and 1.45 will) use
Twisted for the HTTP requests, which presumably supports http_proxy.
Hello!
Is there a way to access a pool with phoenix.py through a local proxy client or a proxy?
Situation:
I am under Linux and I have access to a small proxy pool which is accessed through a local client listening on a port on my localhost.
When I test it with:
export http_proxy="127.0.0.1:" wget http:///
the proxy client shows traffic and all is fine.
But when I try
export http_proxy="127.0.0.1:" ./phoenix.py
then there is no traffic on the proxy client so I guess it is a direct connect to the server.
Is there a solution?
Is there a way to access a pool with phoenix.py through a local proxy client or a proxy?
Situation:
I am under Linux and I have access to a small proxy pool which is accessed through a local client listening on a port on my localhost.
When I test it with:
export http_proxy="127.0.0.1:
the proxy client shows traffic and all is fine.
But when I try
export http_proxy="127.0.0.1:
then there is no traffic on the proxy client so I guess it is a direct connect to the server.
Is there a solution?
For one you are not using a high end NVidia card, but more importantly, you are not using an ATI/AMD card. For better or worse, the OpenCL used on Radeon cards (as opposed to CUDA on NVidia cards) is better suited to this type of calculation. Essentially it amounts to it taking a few more instructions to do the same work on an NVidia card. Personally, I prefer NVidia cards for gaming, but such is life when mining for bitcoins.
Make sure you are launching Phoenix as Administrator or you only get partial GPU access.
Make sure you are launching Phoenix as Administrator or you only get partial GPU access.
Thanks for the input, but this is irrelevant to my question. I know I'm not using a great mining card, but this is what I have, and it's better than nothing.
My question was to the concern of closing the console window via WM_CLOSE causes the video driver to basically cut performance in half, and requires a restart of the driver.
While simply terminating via Ctrl+C closes out cleanly. I'm a C++ dev, and not familiar with python, so I'm not sure if this is just an issue with the windows compiled binary, or if the cleanup code is missing something.
Either way, it's not an important issue (since I have the work-around method), but I do like to know 'why' stuff happens, not just that it does :-/
Thanks for your time.
Slightly confused here... Running a GTX260 (216 core) at about ~50Mhash/s on Windows 7 Professional 64bit.
If I close the console window, then relaunch the miner, my hash rate maxes around ~25Mhash/s (halves)
To fix this, I have to reboot (or, because I'm impatient, disable then re-enable the videocard via device manager.) I'm then back to full hash rate.
However, if I simply break execution of the program (via Ctrl+C), it seems to terminate properly and when relaunching I remain at the full hash rate.
Clearly, the simple answer is to always just terminate it via Ctrl+C... but I'm curious if anyone knows 'why' it seems to crash the video drivers by just closing the console window?
Thanks for any input :-/
If I close the console window, then relaunch the miner, my hash rate maxes around ~25Mhash/s (halves)
To fix this, I have to reboot (or, because I'm impatient, disable then re-enable the videocard via device manager.) I'm then back to full hash rate.
However, if I simply break execution of the program (via Ctrl+C), it seems to terminate properly and when relaunching I remain at the full hash rate.
Clearly, the simple answer is to always just terminate it via Ctrl+C... but I'm curious if anyone knows 'why' it seems to crash the video drivers by just closing the console window?
Thanks for any input :-/
For one you are not using a high end NVidia card, but more importantly, you are not using an ATI/AMD card. For better or worse, the OpenCL used on Radeon cards (as opposed to CUDA on NVidia cards) is better suited to this type of calculation. Essentially it amounts to it taking a few more instructions to do the same work on an NVidia card. Personally, I prefer NVidia cards for gaming, but such is life when mining for bitcoins.
Make sure you are launching Phoenix as Administrator or you only get partial GPU access.
Slightly confused here... Running a GTX260 (216 core) at about ~50Mhash/s on Windows 7 Professional 64bit.
If I close the console window, then relaunch the miner, my hash rate maxes around ~25Mhash/s (halves)
To fix this, I have to reboot (or, because I'm impatient, disable then re-enable the videocard via device manager.) I'm then back to full hash rate.
However, if I simply break execution of the program (via Ctrl+C), it seems to terminate properly and when relaunching I remain at the full hash rate.
Clearly, the simple answer is to always just terminate it via Ctrl+C... but I'm curious if anyone knows 'why' it seems to crash the video drivers by just closing the console window?
Thanks for any input :-/
If I close the console window, then relaunch the miner, my hash rate maxes around ~25Mhash/s (halves)
To fix this, I have to reboot (or, because I'm impatient, disable then re-enable the videocard via device manager.) I'm then back to full hash rate.
However, if I simply break execution of the program (via Ctrl+C), it seems to terminate properly and when relaunching I remain at the full hash rate.
Clearly, the simple answer is to always just terminate it via Ctrl+C... but I'm curious if anyone knows 'why' it seems to crash the video drivers by just closing the console window?
Thanks for any input :-/
I just moved over to Phoenix after finding too many share count misses with another miner. So far, this is fantastic! Hash rates are comparable. Great work and thank you. Donation sent.
it its posible to compile the phoenix miner for windows in some way that doest requiere VB2008/2005 libs? i heart it its posible using a static link.
I'm not sure if this info is on this thread already, but for you ubuntu users out there, if you're getting
from phoenix.py, you'll need:
Code:
File "/home/ethan/src/bitcoin/phoenix-miner/trunk/minerutil/RPCProtocol.py", line 24, in
from twisted.web2.client import http
ImportError: No module named web2.client
from twisted.web2.client import http
ImportError: No module named web2.client
from phoenix.py, you'll need:
Code:
e@u:~/src/bitcoin/phoenix-miner/trunk$ sudo aptitude install python-twisted-web2
Gentoo users may notice that twisted-web2 is not in Portage. You can find it in the sage-on-gentoo overlay.
I'm not sure if this info is on this thread already, but for you ubuntu users out there, if you're getting
from phoenix.py, you'll need:
-E
(1Jmn97kfJ6DBBCuft6Z1oW8e2Lwgheyr6s)
Code:
File "/home/ethan/src/bitcoin/phoenix-miner/trunk/minerutil/RPCProtocol.py", line 24, in
from twisted.web2.client import http
ImportError: No module named web2.client
from twisted.web2.client import http
ImportError: No module named web2.client
from phoenix.py, you'll need:
Code:
e@u:~/src/bitcoin/phoenix-miner/trunk$ sudo aptitude install python-twisted-web2
-E
(1Jmn97kfJ6DBBCuft6Z1oW8e2Lwgheyr6s)
Features
Download
Latest version: 1.4
Windows binaries
Source code/Linux release (requires Python, Twisted, and PyOpenCL)
SVN:
http://svn3.xp-dev.com/svn/phoenix-miner/
Donations
129ZQG33GmqYRVSCw2hw7zmDUCvvMsuGbC
Multiminer thread
MMP protocol specifications
Download
Latest version: 1.4
Windows binaries
Source code/Linux release (requires Python, Twisted, and PyOpenCL)
SVN:
http://svn3.xp-dev.com/svn/phoenix-miner/
Donations
129ZQG33GmqYRVSCw2hw7zmDUCvvMsuGbC
Multiminer thread
MMP protocol specifications
Is it ok to have a few rejected shares, like 2000 accepted and 50 rejected?
Yes. Its really good. For the 2050 shares u sent, 2000 accepted & 50 rejected (stale)
Its quite low actually.
Just FYI, I get a "wrong username/password" error message when I try to connect to deepbit.net. My username (email address) has a period in it and that's probably the source of the problem. I tried escaping the period to no avail.
I'm able to mine at slush's pool with no problems. I suppose I will have to register with a different email address at deepbit.net if I want to join that pool.
I'm able to mine at slush's pool with no problems. I suppose I will have to register with a different email address at deepbit.net if I want to join that pool.
You can use same email address to register in any number of pools.
First you login to deepbit.net with username & password.
Make sure, the worker username & password are correct, that is it is same as in miner.
If not change the worker name & password to reflect the worker name & password in deepbit.net.
You can create new worker & use that.
Oops, I was using a period instead of "_" before the worker ID number.
Fixed and now running well.
...
Thanks for you answer, I have moved it to
https://bitcointalksearch.org/topic/windows-7-64-bit-dual-5970-rig-question-7389
Just FYI, I get a "wrong username/password" error message when I try to connect to deepbit.net. My username (email address) has a period in it and that's probably the source of the problem. I tried escaping the period to no avail.
I'm able to mine at slush's pool with no problems. I suppose I will have to register with a different email address at deepbit.net if I want to join that pool.
I'm able to mine at slush's pool with no problems. I suppose I will have to register with a different email address at deepbit.net if I want to join that pool.
You can use same email address to register in any number of pools.
First you login to deepbit.net with username & password.
Make sure, the worker username & password are correct, that is it is same as in miner.
If not change the worker name & password to reflect the worker name & password in deepbit.net.
You can create new worker & use that.
Jump to: