|
Are you sure the prepared sql statement in pushpoold's server.json is for the db structure of mining farm?
|
|
|
|
|
I see quite a lot of rejects from the cpu. So it means that in a few hours it did find something
|
|
|
|
This is Korea. This kind of crazy rain lasts about 45 days straight.
Are you korean? I think i can use you in the future to translate me manhwa. |
|
|
|
I know this seems like a dumb question but I am a bit confused. About a month ago, I checked out the Wiki page ( here) regarding the comparison of GPU hardware. I went out, bought me a cheap, but decent card and through it in a computer that I have. After, installing various drivers and ATI/AMD SDKs, I never could get the thing to work. Then, I think I realized the problem. It appears that just because you buy a GPU with one of the listed ATI processors, it doesn't mean that the card is OpenCL compatible. WTF! What should I be looking for in a graphics card? I know that most of the Sapphire brands seem to be guaranteed to work, but what are the specific specs on a card that make in compatible with the OpenCL drivers? Mind telling us the card you bought? |
|
|
|
Yes i know, it is mining at half of the speed but it still uses 90% of the cpu power....
After you have specified the number of threads, set(if possible use task manager) the cpu affinity to be at core X or whichever you choose. And that's basically it. I have already set the affinity from the guiminer. There's a slight possibility it's not working via guiminer. Do it via Task Manager. Also, how many cores do you have? Only 2 cores. Then what did you expect? I have a quad core, so if i use one thread that's only 25% of my CPU. For you, it will be 50%. Basically, that is why you have the so called "high cpu usage" |
|
|
|
1.5.0 works well. I see you're using an approach similar to what I had suggested for the CPUminer. The numbers are looking far more stable now and it's completing the work far more efficiently as predicted. Kudos on getting the darn thing working.
Hehe, if you are talking about the split nonces, that was me who suggested it. |
|
|
|
shoot right up with the Mh/s count when you start it, then drop back down ?!? always catches me out, i boot up and im like wow ! then it goes to its regular value lol  My 1st opinion: heat problem Heat has nothing to do with this. It's a bug. |
|
|
|
shoot right up with the Mh/s count when you start it, then drop back down ?!? always catches me out, i boot up and im like wow ! then it goes to its regular value lol It's the power of python. (sarcasm intended) |
|
|
|
Yes i know, it is mining at half of the speed but it still uses 90% of the cpu power....
After you have specified the number of threads, set(if possible use task manager) the cpu affinity to be at core X or whichever you choose. And that's basically it. I have already set the affinity from the guiminer. There's a slight possibility it's not working via guiminer. Do it via Task Manager. Also, how many cores do you have? |
|
|
|
|
Why is it that i am seeing that the faster miner i.e 446 mhash/s has waay less shares than the slower miner?
|
|
|
|
No, cpuminer does not check for hash < target.
Oops, i meant the *miner_thread which is for CPU mining. And more specifically, the 4way algorithm. This is, of course, if you enable the fulltest function in util.c to return "rc". |
|
|
|
Orly? How about checking the code in the gpuminer_thread or findnonce.c and tell me where you see a check for hash < target or even where the target is derived from?
You claimed that cgminer would break with a different difficulty. cgminer and its ancestor, cpuminer, will push all H==0 solutions. This is not the same thing. Your income remains the same, either way. Ok, if not break, then it will have a tad bit more rejects, cause it will submit every H==0 because it does not check for hash < target. Only the cpuminer does. |
|
|
|
Yes i know, it is mining at half of the speed but it still uses 90% of the cpu power....
After you have specified the number of threads, set(if possible use task manager) the cpu affinity to be at core X or whichever you choose. And that's basically it. |
|
|
|
Are you people serious? That's like "I chose the wrong lottery ticket". It's probability, luck, chance, fate, whatever. Your solo performance has absolutely nothing to do with your pool record.
I found 3 blocks on slush's pool. I got angry about that, went solo right away, and 8 hours later, boom, i found a block. 11 days later another one. With just a SINGLE 5850 doing 275mhash/s back then. |
|
|
|
Now, open up msg.c and head down to the check_hash function, specifically the return of better_hash. It looks like it is checking a hard coded 40 bits of 0's. Won't I need to change this spot too? What should I change this to based on the 10, 50, 100 scenarios?
Correct. In addition to changing EASY_TARGET, you must update check_hash. IMHO the bounty should go to the person submitting a patch that makes difficulty variable, without recompiling the source code! Well no, cause then cgminer will be broken perhaps. No, that will not break cgminer. All miners are built to handle any difficulty. You're just confused. Orly? How about checking the code in the gpuminer_thread or findnonce.c and tell me where you see a check for hash < target or even where the target is derived from? |
|
|
|
Ufasofft i was wondering if you could make an build that uses only half of the power that computer has, like if it has 2 CPS to use just 1 or so?
I would like this low build because it will allow you're computer to do other things when you are using the miner whitout any lag or so.
You can already do this using CPU AFFINITY if you are using Guiminer as a front end. I am using guiminer as frontend but it doesn't matter if i select only 1 cpu afinitty, it still uses all the power of the proccesor and is still mining at the same rate like i am mining with all the cpus.... That's why the -t switch was invented. -t 1-X number of threads, which means cores. By default, it uses all. Specify this in the arguments, say -t 1 and it will use one core. Consider donating if you found this useful : 16kFZCjtaQELi4Zipf6RcBM8VBQ5tNavnU |
|
|
|
The timestamp field is correct as far as i can see, as for the ID field..yeah, that's not. But i am going to let you fix it yourself and help you learn where you were wrong.
You're going to need to enlighten me. I realize the username field (must be) unique, but I can't envision developing a system where I want to look at a table or a couple of tables and associate only on something like username. Integer lookup is just better. Associating two tables with ID numbers is normal, why is this different? And, in the code included with mining farm there is, in fact, an ID column in the pool_worker table. Two of em. So how is it wrong? I honestly didn't think you were smart enough to use table association, i give you that. For the latter, cause it needs to be auto_increment, but most importantly, should NOT have a default value. |
|
|
|
adding an id is wrong?
or a timestamp?
for what reason?
The timestamp field is correct as far as i can see, as for the ID field..yeah, that's not. But i am going to let you fix it yourself and help you learn where you were wrong. Also, not to brag, but i was the one who gave the table structure to xenland when he first started developing "miningFarm". Altho, this one, you posted differs.
Man that brings back memories of me staying up for 10 hours up into the morning trying to "crack" the un-documented pushpoold database...... Thanks Diki!  |
|
|
|
|
If the devs want Bitcoin to succeed, they need to make it to start right away. I mean, if i need to pay for something _now_ that means now!! not 5 minutes later.
|
|
|
|
|
Show Posts
