Oops, we have two threads. Better use the other one: https://bitcointalksearch.org/topic/1050-th-bitmintercom-1-pplnspays-txfees-mergedminingstratumgbtvardiff-27062
To answer your question: Yep, more stats are coming.
Topic: Old BitMinter thread (use the other one) (Read 7411 times)
Pool backend updated: Faster block change detection. Better cheat protection. Some changes to scale better.
Seems to be running fine.
Regarding source code: The miner, pool backend and web application are all closed source. At least for now. If you prefer open source or a command-line miner, then DiabloMiner seems to me like a good alternative. But all miners should work with the pool.
Seems to be running fine.
Regarding source code: The miner, pool backend and web application are all closed source. At least for now. If you prefer open source or a command-line miner, then DiabloMiner seems to me like a good alternative. But all miners should work with the pool.
The hashrate is still quite low. And I still haven't programmed in an estimated hashrate for the pool - but it's coming soon!
Sorry about connection issues. While I was working on the server I lost all connectivity with it. I got things running again as soon as I was able to reconnect.
As for hashing speed of BitMinter: I made a couple optimizations the other day. I can't remember if I put those up on bitminter.com friday or saturday. Then I tested it on radeon 6990 and geforce gtx 580. Both GPUs ran faster on BitMinter than DiabloMiner and Phoenix w/phatk. Although with DiabloMiner the difference was barely 1%. That was on Catalyst 11.6 though. I'll have to try on Catalyst 11.7.
The OpenCL kernel is compiled at runtime so different drivers can definitely make a difference there.
The vectors thing seems a little random. For me manual vectors help a lot on radeon 6990, but makes geforce gtx580 run much slower. The GTX580 usually runs faster with vectors with other miners, though. Must be a weirdness with my kernel.
Sorry about connection issues. While I was working on the server I lost all connectivity with it. I got things running again as soon as I was able to reconnect.
As for hashing speed of BitMinter: I made a couple optimizations the other day. I can't remember if I put those up on bitminter.com friday or saturday. Then I tested it on radeon 6990 and geforce gtx 580. Both GPUs ran faster on BitMinter than DiabloMiner and Phoenix w/phatk. Although with DiabloMiner the difference was barely 1%. That was on Catalyst 11.6 though. I'll have to try on Catalyst 11.7.
The OpenCL kernel is compiled at runtime so different drivers can definitely make a difference there.
The vectors thing seems a little random. For me manual vectors help a lot on radeon 6990, but makes geforce gtx580 run much slower. The GTX580 usually runs faster with vectors with other miners, though. Must be a weirdness with my kernel.
What's the hashrate of your pool so far?
Btw, Catalyst 11.7 with SDK 2.5 gave me huge increases to DiabloMiner and Phatk but only about 1% on your miner.
DiabloMiner 82MHash/s
Phoenix Phatk 80Mhash/s
BitMiner 81Mhash/s
And downclocked to 500 Mhz because my GPU runs at 110C
DiabloMiner 59Mhash/s
Phoenix Phatk 56Mhash/s
BitMiner 57Mhash/s
The kernel for phatk compiled differently under SDK 2.5 and I assume the same for DiabloMiner. Are you including a precompiled kernel with BitMiner or is it compiled at run time?
I also have manual vectors and BFI disabled on your miner. BFI isn't supported on a 4850 so enabling it won't do anything, but weirdly, manual vectors run slower on BitMinter but vectors run faster on Phatk/DiabloMiner as long as worksize is <= 128. Actually, on SDK 2.5 DiabloMiner runs faster with worksize = 128 while on SDK 2.4 it was worksize = 64. Phatk is still worksize = 64. And for BitMinter worksize = 64 is optimal as well.
Edit: And..I can't connect now.
Btw, Catalyst 11.7 with SDK 2.5 gave me huge increases to DiabloMiner and Phatk but only about 1% on your miner.
DiabloMiner 82MHash/s
Phoenix Phatk 80Mhash/s
BitMiner 81Mhash/s
And downclocked to 500 Mhz because my GPU runs at 110C
DiabloMiner 59Mhash/s
Phoenix Phatk 56Mhash/s
BitMiner 57Mhash/s
The kernel for phatk compiled differently under SDK 2.5 and I assume the same for DiabloMiner. Are you including a precompiled kernel with BitMiner or is it compiled at run time?
I also have manual vectors and BFI disabled on your miner. BFI isn't supported on a 4850 so enabling it won't do anything, but weirdly, manual vectors run slower on BitMinter but vectors run faster on Phatk/DiabloMiner as long as worksize is <= 128. Actually, on SDK 2.5 DiabloMiner runs faster with worksize = 128 while on SDK 2.4 it was worksize = 64. Phatk is still worksize = 64. And for BitMinter worksize = 64 is optimal as well.
Edit: And..I can't connect now.
Cool, OCedHrt, good to hear you are getting good performance. Adding "average speed" to my TODO list - good idea!
And... First block created!
And... First block created!
Getting better performance than phatk on my 4850. Up to 80Mhash/s vs 77Mhash/s.
Would be nice to have an average mint speed because my card runs at 110C so the driver down clocks every 5 seconds.
Would be nice to have an average mint speed because my card runs at 110C so the driver down clocks every 5 seconds.
Yes, you really need manual vector handling on AMD. Their auto vectorization isn't very good.
I made some changes to vectors. Appreciate it if you could try again. BFI_INT on and off are different kernels, so might yield different results.
I made some changes to vectors. Appreciate it if you could try again. BFI_INT on and off are different kernels, so might yield different results.
I disabled "manual vectors" and the minter software started working
however, it's not as fast as poclbm on my machine
poclbm gives 138mh/s with -w128 -v -f30
however, it's not as fast as poclbm on my machine
poclbm gives 138mh/s with -w128 -v -f30
Quick update:
- New statistics page listing generated blocks. Not much to see before we mine some blocks.
- Number of proofs of work delivered by each machine(worker) listed under "my account"
- Mails less likely to be rejected as spam. If you never got your email confirmation link, go to "my account" and enter your email address again.
Now fixed so poclbm works - thanks iopq! (my pool backend wasn't including "error":null in getwork responses - somehow the miners I tested so far didn't mind)
jdebunt: Not sure what the problem is. Do other WebStart programs work on your machine? Here's a quick one to test:
http://www-pw.physics.uiowa.edu/das2/javaPlatformTest.jbf.html
jdebunt: Not sure what the problem is. Do other WebStart programs work on your machine? Here's a quick one to test:
http://www-pw.physics.uiowa.edu/das2/javaPlatformTest.jbf.html
tried bitminter in poclbm:
poclbm.exe --user=username_worker --pass=password -o mint.bitminter.com -p 8332 --device=1 --platform=0 --verbose -v -w128 -f30
2011-06-27 09:12:48: Listener for "bitminter": 27/06/2011 09:12:48, Unexpected error:
2011-06-27 09:12:48: Listener for "bitminter": Traceback (most recent call last):
2011-06-27 09:12:48: Listener for "bitminter": File "BitcoinMiner.pyo", line 167, in mine
2011-06-27 09:12:48: Listener for "bitminter": File "BitcoinMiner.pyo", line 210, in getwork
2011-06-27 09:12:48: Listener for "bitminter": File "BitcoinMiner.pyo", line 237, in request
2011-06-27 09:12:48: Listener for "bitminter": KeyError: 'error'
poclbm.exe --user=username_worker --pass=password -o mint.bitminter.com -p 8332 --device=1 --platform=0 --verbose -v -w128 -f30
2011-06-27 09:12:48: Listener for "bitminter": 27/06/2011 09:12:48, Unexpected error:
2011-06-27 09:12:48: Listener for "bitminter": Traceback (most recent call last):
2011-06-27 09:12:48: Listener for "bitminter": File "BitcoinMiner.pyo", line 167, in mine
2011-06-27 09:12:48: Listener for "bitminter": File "BitcoinMiner.pyo", line 210, in getwork
2011-06-27 09:12:48: Listener for "bitminter": File "BitcoinMiner.pyo", line 237, in request
2011-06-27 09:12:48: Listener for "bitminter": KeyError: 'error'
If you prefer a different miner, connect it to mint.bitminter.com:8332. The username must be in the form "myname_mymachine", where "myname" is your user name and "mymachine" is the name of one of your registered machines/workers.
This doesnt work. Failed to connect.
This doesnt work. Failed to connect.
I haven't tested with all miners yet, so I'm not 100% they will all work. Which miner are you using?
Remember that username, workername and password are all case sensitive.
I just tried it with DiabloMiner:
> ./DiabloMiner-Linux.sh -u DrHaribo_Smurf -p MyPassWord -l http://mint.bitminter.com:8332/
[27.06.11 13:52:07] Started
[27.06.11 13:52:07] Connecting to: http://mint.bitminter.com:8332/
[27.06.11 13:52:08] Using NVIDIA CUDA OpenCL 1.0 CUDA 4.0.1
[27.06.11 13:52:08] Added GeForce 9400 GT (#1) (2 CU, local work size of 512)
mhash 2,7/2,7 | accept: 0 | reject: 0 | hw error: 0
(No, the Smurf is not a kick-ass machine)
OpenID login problems: The easiest way to log in is to click one of the shortcuts instead of typing in your OpenID provider manually. If you have a google or gmail account, just click the little google logo. If you can't see it - turn on javascript. Sorry, no Facebook login yet - I may add that later but since they don't support OpenID it will take some extra work.
Oldminer: The problem you are having with "splash: recv failed" is due to Java not being able to access the server. I should probably add some help pages with solutions for things like that. It may be due to a firewall. For the built-in Windows firewall, I think the first time a Java program tries to access the network, Windows will ask whether to allow it and you just click yes. For other firewalls, things may work differently.
If you need to use a proxy for web access, you can set that up in the Java settings. You can find Java in Control Panel if using Windows. Alternatively, and this works on any operating system, run the command "javaws -viewer". You can run it from the command line on Linux or Mac. Easiest in windows is to hit the start button and type it in there. It opens two windows, just close the "Java Cache Viewer". The other window "Java Control Panel" is where the proxy settings are: under the "General" tab hit the "Network Settings..." button. You can type in your proxy info there. If webpages work in your browser, you may want to just choose "Use browser settings", to let Java access the network the same way.
iopq: Sadly I have not had a chance to test the miner on a Juniper GPU before. It works fine on Cayman and many NVIDIA GPUs. It's weird that the same OpenCL code would compile on some GPUs and not on others. I'll look into it. Would be cool if people who get it running on their GPU could state which GPU they are using and what kind of speed they are getting. You may get slightly higher speed if you hit the button in the lower right of the window, which hides all the fancy gauges so the GPU can focus on actual work.
Oldminer: The problem you are having with "splash: recv failed" is due to Java not being able to access the server. I should probably add some help pages with solutions for things like that. It may be due to a firewall. For the built-in Windows firewall, I think the first time a Java program tries to access the network, Windows will ask whether to allow it and you just click yes. For other firewalls, things may work differently.
If you need to use a proxy for web access, you can set that up in the Java settings. You can find Java in Control Panel if using Windows. Alternatively, and this works on any operating system, run the command "javaws -viewer". You can run it from the command line on Linux or Mac. Easiest in windows is to hit the start button and type it in there. It opens two windows, just close the "Java Cache Viewer". The other window "Java Control Panel" is where the proxy settings are: under the "General" tab hit the "Network Settings..." button. You can type in your proxy info there. If webpages work in your browser, you may want to just choose "Use browser settings", to let Java access the network the same way.
iopq: Sadly I have not had a chance to test the miner on a Juniper GPU before. It works fine on Cayman and many NVIDIA GPUs. It's weird that the same OpenCL code would compile on some GPUs and not on others. I'll look into it. Would be cool if people who get it running on their GPU could state which GPU they are using and what kind of speed they are getting. You may get slightly higher speed if you hit the button in the lower right of the window, which hides all the fancy gauges so the GPU can focus on actual work.
managed to sign up after all, downloading software
edit : when executing the java applet, i see my java loading but nothing else happens....anything i'm doing wrong?
edit : when executing the java applet, i see my java loading but nothing else happens....anything i'm doing wrong?
If you prefer a different miner, connect it to mint.bitminter.com:8332. The username must be in the form "myname_mymachine", where "myname" is your user name and "mymachine" is the name of one of your registered machines/workers.
This doesnt work. Failed to connect.
This doesnt work. Failed to connect.
I was able to sign up, trying out your miner:
2011.06.27 [02:41] Device [Juniper (#1)] unable to start: Compilation error (code -11 = CL_BUILD_PROGRAM_FAILURE) on Juniper (#1)
2011.06.27 [02:41] Device [Juniper (#1)] unable to start: Compilation error (code -11 = CL_BUILD_PROGRAM_FAILURE) on Juniper (#1)
still getting •OpenID Failure: 0x704: I/O transport error: here
Ok I'm signed up
Hmm getting the following error when I click 'start'
Hmm getting the following error when I click 'start'
Sorry guys! Bug fixed in signup code. Also fixed a potential issue with OpenID handling.
Tried signing up but got same - Something unexpected happened while serving the page at /signup
Jump to: