Except ... it isn't correct.
There IS wasted hashing power.
The problem is not P2Pool specifically, but rather that people believe it is OK to get a high crappy reject rate (9%) because someone here said it was OK to be that high rate while they were getting a much lower rate.
If you use a good miner program and configure it correctly you will not get a high crappy 9% reject rate.
The cause is actually that the miners are not by default configured to handle the ridiculously high share rate (10 seconds)
So P2Pool is the cause, but the solution is simply to configure your miner to handle that issue.
Aside: if you have one or more BFL FPGA Singles, you cannot mine on P2Pool without wasting a large % of your hash rate.
Except reject rate means nothing, delta of average reject rate is what you need to pay attention to. Also, BFL's firmware is broken, they won't return shares until its done 2^32 hashes, and any attempts to force it to update on long polll dumps valid shares. BFL needs to fix their shit before they sell any more FPGAs. |
|
|
|
There is no such thing as "wasting hashing power". You either find a block or the share is worthless. If some of the worthless shares get orphaned how much have you lost? p2pool doesn't show any higher (~1% of main fork) orphan rate ON BLOCKS. p2pool could function with a 99.999% SHARE orphan rate but the variance and unfairness of that would cause PR (not technical) problems. 10 second LP is a compromise between share orphans and difficulty. The thing that seems hard for people to understand is shares have ABSOLUTELY NO VALUE. They aren't progress towards a block they are completely worthless. We simply use them because it is a cheat proof mechanism to fairly split rewards. Nothing more, nothing less. So if 10% of worthless shares are lost how much value/blocks/work is lost? .... Nothing. 10% of 0 is still 0.  Only DOA affect the rate blocks are found. DOA are bad/stale/invalid shares before they even get broadcast to p2pool network. Thus even if they were blocks they are worthless because Bitcoin network (not just p2pool) would find them worthless even if they met target requirements for a block. I would assume that any hashing graph is using post DOA hashrates. Still DOA looks to only be about 2% of the network. All of this so goddamned much. |
|
|
|
|
No, the guy shut down, sadly.
|
|
|
|
Yeah, I think its 8332. Also, forget what I said, I forgot I removed the code that ignores port 80, it should in fact work.
Ok. Can you improve selecting different port in multipool configuration? Why? It already allows nearly unlimited pools. I think you made a different mistake, such as not providing comma separated -u and -p as well. |
|
|
|
DiabloMiner automatically rewrites 80 to the default port to prevent user error.
I'm confused. Default port is 8332 ? With option -r 8332,8332 miner never connected to pool.metabank.ru, and switching to pit.deepbit.net automatically. Possible my miner is older verion. In network monitor connections on port 80 is established:  Yeah, I think its 8332. Also, forget what I said, I forgot I removed the code that ignores port 80, it should in fact work. |
|
|
|
You can't use port 80 with DiabloMiner. Also, it will still emit the error, but it still switches to the next.
Why can't use? My rigs normally works with pool.metabank.ru and sends block to port 80 without errors. Problem only with switch to port 8332 of secondary pool. DiabloMiner automatically rewrites 80 to the default port to prevent user error. |
|
|
|
That is detailed in the op post: just use commas in the arguments.
Tested with sample: -o pool.metabank.ru,pit.deepbit.net -r 80,8332
With different ports, secondary not worked if primary fails. Error is "Read timeout" You can't use port 80 with DiabloMiner. Also, it will still emit the error, but it still switches to the next. |
|
|
|
If your entire batch is so small (like asian penis...) when there are LOTS of people like me who would spend 5 grand or so on MORE ... to just close it out like this ... not smart.
He could be making a LOT more money.
Stop sucking his balls.
Wussy.
Okay, look, if this shit continues I'm just going to just start _paying_ Theymos to ban people. I'm pretty sure I could get some sort of bulk deal for 1BTC a person. |
|
|
|
Hi! How set secondary pool in failover configuration? Can miner works with several pools simultaneously?
That is detailed in the op post: just use commas in the arguments. |
|
|
|
I am selling them for private reasons, so please don't ask. Wife found out? Just kidding. That said, if your present deal falls through, I am definitely interested in purchasing them. I have a "Web of Trust" rating, too, though it's been a long while since I've used it. I also have a post history that will probably convince you it'd be a bad idea to let me have your Icarus boards. I kind of got screwed out of the "last 50 batch", I went on vacation for 3 days and when I came back they had made a new thread and sold out already. Yeah, this is a pretty stupid way of marketing. But what do you expect from some little Chinese dude. And you think you're not going to get banned from this forum why? |
|
|
|
In my sig. Didn't Captain Jack Sparrow kill you? |
|
|
|
Hi, folks. I'm experimenting with using my 6770 for mining using DiabloMiner. I love how easy this software is to set up, but there's one commandline switch I don't understand...
What does the -g switch do?
I'm getting a respectable 185-190 MH with my current configuration, but I'd like to improve my efficiency and keep the other miners in the pool happy. Will setting -g higher (or lower?) help me achieve that? (FYI, I have a good Internet connection and no issues connecting to the server for the pool.)
-g sets how often it pulls new work; however, it is completely ignored on any pool that does long poll and/or sets an expiry time. The default value of -g is whats recommended for solo miners. |
|
|
|
An update.
I did all the proper steps and modifications to try and get this working on my reference ATI 5870s.
Will post back later with some results but on first sight the VRM temps are too low to be real and probably just core temps.
Runeks fork was even worse and did not even show anything other than "supported device".
Again, 100% reference ATI branded 5870s here ...
Some VRMs are higher quality and are around GPU temps: say, GPU temp is around 85c, VRMs could be around both 120c for older/shittier VRMs (and be within the spec for the VRMs too), and 85c for newer/less shitty VRMs. |
|
|
|
To have coil whine you need a coil and those are in your PSU.
Except not all PSUs have VRMs that use coils, nor are PSUs the only thing that use VRMs. |
|
|
|
Or just hook your local git clone up to a cronjob. |
|
|
|
12.1 and up install the runtime, you should never install the SDK on top of Catalyst anymore.
What arguments did you give DM?
Funny you should say that, because I just finished doing a complete uninstall and reinstall of 12.2 and it seems to be working now. However, now I'm having a problem with the machine locking up while mining. I suspect my power supply is sketchy, and could be the issue. Thanks for the quick replies! Either PSU sucks, wall power sucks, you're overclocking and/or undervolting too far, or GPU temp is over 85c (or less if the card is a shitty brand). I'm leaning towards the PSU being the culprit. Wall power is clean, only overclocking to 950core/333mem, no voltage adjustments, GPU temp hasn't gone over 70c that I've seen so far. Try no overclocks and see if it still locks up. If it doesn't, then you overclocked too far. |
|
|
|
12.1 and up install the runtime, you should never install the SDK on top of Catalyst anymore.
What arguments did you give DM?
Funny you should say that, because I just finished doing a complete uninstall and reinstall of 12.2 and it seems to be working now. However, now I'm having a problem with the machine locking up while mining. I suspect my power supply is sketchy, and could be the issue. Thanks for the quick replies! Either PSU sucks, wall power sucks, you're overclocking and/or undervolting too far, or GPU temp is over 85c (or less if the card is a shitty brand). |
|
|
|
Hi guys, need a little help here.
I just got my second mining rig up and (kinda) running, but I'm having some troubles.
When I try to run Diablo, I get the following messages:
"Using AMD parallel processing OpenCL 1.1 AMD-App (851.4)
error: OpenCL platform AMD parallel processing OpenCL contains no devices
error: No OpenCL devices found
Diablominer: An error occurred while starting the application.
I'm running 12.3 catalyst on XP Pro SP3, and everything looks fine on the desktop side.
It seems like there's no SDK installed, but I tried installing it manually and there's no difference.
Thoughts?
Which Radeon? Oops! 5830, sorry forgot to put that in. 12.1 and up install the runtime, you should never install the SDK on top of Catalyst anymore. What arguments did you give DM? |
|
|
|
Hi guys, need a little help here.
I just got my second mining rig up and (kinda) running, but I'm having some troubles.
When I try to run Diablo, I get the following messages:
"Using AMD parallel processing OpenCL 1.1 AMD-App (851.4)
error: OpenCL platform AMD parallel processing OpenCL contains no devices
error: No OpenCL devices found
Diablominer: An error occurred while starting the application.
I'm running 12.3 catalyst on XP Pro SP3, and everything looks fine on the desktop side.
It seems like there's no SDK installed, but I tried installing it manually and there's no difference.
Thoughts?
Which Radeon? |
|
|
|
(OT: Hell, not long ago I bought standby-killers to turn TV off over night instead of letting it consume 5W in standby-mode, now I'm burning kWatts 24/7  , different story). New TVs typically use a watts or less on standby, which you exchange for instant on and less wear on the parts. Disabling standby will just kill your TV faster which is more expensive than the electricity it is "wasting". |
|
|
|
|
Show Posts
