|
I've been monitoring the progress and the most i've lost is 4-5 shares less than usual. Sometimes i actually get a few more.
|
|
|
|
|
The GPU is the GPU. it's the program i am referring to as a miner(cause it it's the one doing to job more or less) which on my case is poclbm(GUI)
|
|
|
|
|
I have just one 5850. It pulls ~273 Mhash/s at stock speeds. Now, i know that solo is near impossible even with dual 5970 and will be even more so, however do you think that the chance of finding a block increases if you have multiple instances of a miner running? I have 4 currently on my 5850 and the speed is somewhat divided for every miner.
Assuming that a quad 5970 uses the same method, don't you think the probability get's increased by a small fraction that you will find a block faster than with one miner? I mean it's basically the same thing with pools. Every worker requests new works, increasing the chance of the bitcoind sending the winning hash.
|
|
|
|
|
Sorry for the double post, but is it me, or has the reward column on the Stats page disappeared?
Also, the frontend is loading slowly and i am getting Communication errors on my client. DDoS?
|
|
|
|
hi,
i'm new here, so maybe this is a very stupid question. i've got on old, very slow computer, with an athlon xp 3000+ cpu (2.16 ghz) and and an amd radeon 7000. At the moment it's mining only the cpu at about 750 khash/s. As far i know, the graphic card doesn't support opencl.
my question is: is it worth continueing mining with this hardware? thanks
That speed? Not even close to worth it. |
|
|
|
|
Plug a monitor to the second card!
|
|
|
|
well, i really don't mind to "..see idle warnings/RPC errors from time to time..", but check this out. and that's only 4hours No idea what the problem is on that one. We've still got about a thousand workers running which aren't experiencing anything close to it. I am also getting quite the idle miner warning. EDIT: 2011-05-27 15:13:50: Listener for "btcguild": 27/05/2011 15:13:50, Problems communicating with bitcoin RPC
2011-05-27 15:13:54: Listener for "btcguild": 27/05/2011 15:13:54, warning: job finished, miner is idle
2011-05-27 15:15:48: Listener for "btcguild": 27/05/2011 15:15:48, warning: job finished, miner is idle
2011-05-27 15:17:51: Listener for "btcguild": 27/05/2011 15:17:51, Problems communicating with bitcoin RPC
2011-05-27 15:21:02: Listener for "btcguild": 27/05/2011 15:21:02, warning: job finished, miner is idle
2011-05-27 15:21:02: Listener for "btcguild": 27/05/2011 15:21:02, Problems communicating with bitcoin RPC
2011-05-27 15:21:55: Listener for "btcguild": 27/05/2011 15:21:55, Problems communicating with bitcoin RPC
2011-05-27 15:23:46: Listener for "btcguild": 27/05/2011 15:23:46, long poll: new block 00000961bf8290e0
2011-05-27 15:24:00: Listener for "btcguild": 27/05/2011 15:24:00, Problems communicating with bitcoin RPC
|
|
|
|
|
@Banks
Why post crap, if you yourself don't know what you want to write??
|
|
|
|
Yes, totally normal.
The standard node client isn't impressed unless you've got a valid hash that meets the current difficulty target. For most people, this will be never.
The pools, however, accept hashes that only meet a much easier target, so that they can allocate shares to the miners.
The pool does not allocate shares. You do them. If they meet the needed criteria they get inserted in the database as a valid share(bit might not meet the target). |
|
|
|
|
Depending on the database. Are you using mysql? If so, is it on? Since pushpoold need's to get the workers from somewhere.
|
|
|
|
In order to optimize. our_result and upstream_result must be enum 'y','n'. |
|
|
|
|
I like all them GPUs, but you will increase the diff a lot dude. Think about the other users.
|
|
|
|
|
Zomg, no offense, but this has to be the lamest thing ever. You have basically done nothing.
|
|
|
|
|
I am specifically requesting a payout button for the "confirmed rewards". As i set my threshold to 4.60 while my unconfirmed reward was 4.62. But i never even imagined that we would get an invalid block. So, every one of my rewards got confirmed, but never crossed the threshold.
Now i can't withdraw it. And i have switched to another pool for for a bit thus i can't mine. And even if i do, waiting for 100 confirms which could take more than 12 hours is....
Nvm, fixed.
|
|
|
|
|
New OS.. And yes that is the file. It must be stickied somewhere for everyone to see it.
|
|
|
|
|
You think i have the time or patience to wait for them to download? There is simply no time...
|
|
|
|
|
I've been browsing google like crazy trying to find it. Where is it?
|
|
|
|
|
And the CPU is? Bottlenecking is also a factor.
|
|
|
|
When will people learn that difficulty is not the same thing as demand? Never, because people keep telling themselves and each other that they are the same thing when it comes to bitcoin. Economic rules of the past somehow doesn't apply to bitcoin economy in this imaginary world where we are all bitcoin millionaires. Oh we can dream can't we?
Many of us need to get over the fact that we are not early adopters. Remember the difficulties were in single digits and didn't increase for a long time. The big dogs are already making their fortune from going from .01 and less to 8x usd as it recently has. They are the ones that want more and more people to raise the value and difficulty more so than the new ones. Trying to raise the price from 8 to 10 is merely a 20% increase in value and is laughable compared to what's already been done to the btc value as a whole.
Then...i demand that people sell higher! |
|
|
|
Security Request:
Please change the cookies you are storing to be "session" cookies - they will expire at the end of the browser session instead of at a specific date. This will close a security hole where someone that has access to a person's PC can access and change the bitcoin address without authenticating.
I hate websites that log me out when i close my browser or navigate away from the page. |
|
|
|
|
Show Posts
