Topic: DiabloMiner GPU Miner - page 71. (Read 866596 times)
Update: I've added mtrlt's bat script for Windows. No longer do you have to run the whole Java command by hand.
Does DiabloMiner support the Long Polling protocol that DeepBit has introduced? If not, do you have any plans to implement it?
I don't see value in the long polling protocol. Its much easier to just use a dedicated Websockets protocol. I plan on introducing this in the future.
Does DiabloMiner support the Long Polling protocol that DeepBit has introduced? If not, do you have any plans to implement it?
Hi diablo, thanks for the prompt reply. I have a plan now and that is to mix my dual 6990 with the 5850 + 5970. Hopefully windows will recognise both as opencl and no need to run xfire. =P
Thanks diablo I guess I will have to make do with the hash rate till amd comes out with the new sdk for 6990. Thanks for your great miner, I am using it for the dual 6990. It hovers around 1ghash/s and its at -f 7777777. Hahah I tested and the numbers seem to slow down the hash rate when its lesser than -f 17 but anything more it hits 1ghash/s constant. Which is nice =)
GPU Max at 93% with powerplay maxed out
GPU Max at 93% with powerplay maxed out
It generally maxes out at your OS's kernel's scheduler's timeslice length. Generally, this is 100hz or 1000hz. Higher than -f 1000 makes no sense. Not only that, my miner has an automatic lower limit as to not send too little work to the GPU. The actual -f maximum may be much lower.
Wait I dont quite get the part OS kernel scheduler timeslice length. What I do face is a huge drop in hash/s when i go lower than -f 15, at -f 2 its almost 600mhash/s so thats why i up the -f number to go it to run at 1ghash
Basically, the GPU babysitting threads go to sleep between OpenCL executions. The OS's kernel can only change threads so fast. Thus, having OpenCL executions that are shorter than the length of one timeslice means the GPU is waiting for the babysitting threads to catch up. However, as I said, the minimum kernel length is tuned to your hardware, it doesn't seem you can ever reach the timeslice length.
As for -f 1 looking slower, its because at extremely long execution lengths, it tends to screw over the OS's clock in as that it jumps large periods to catch up to the real world. This is why, when using -f 1, you use the second number my miner outputs and run it for 10 minutes before you trust the number.
Linux doesn't suffer this nearly as much as Windows does.
Thanks diablo I guess I will have to make do with the hash rate till amd comes out with the new sdk for 6990. Thanks for your great miner, I am using it for the dual 6990. It hovers around 1ghash/s and its at -f 7777777. Hahah I tested and the numbers seem to slow down the hash rate when its lesser than -f 17 but anything more it hits 1ghash/s constant. Which is nice =)
GPU Max at 93% with powerplay maxed out
GPU Max at 93% with powerplay maxed out
It generally maxes out at your OS's kernel's scheduler's timeslice length. Generally, this is 100hz or 1000hz. Higher than -f 1000 makes no sense. Not only that, my miner has an automatic lower limit as to not send too little work to the GPU. The actual -f maximum may be much lower.
Wait I dont quite get the part OS kernel scheduler timeslice length. What I do face is a huge drop in hash/s when i go lower than -f 15, at -f 2 its almost 600mhash/s so thats why i up the -f number to go it to run at 1ghash
Thanks diablo I guess I will have to make do with the hash rate till amd comes out with the new sdk for 6990. Thanks for your great miner, I am using it for the dual 6990. It hovers around 1ghash/s and its at -f 7777777. Hahah I tested and the numbers seem to slow down the hash rate when its lesser than -f 17 but anything more it hits 1ghash/s constant. Which is nice =)
GPU Max at 93% with powerplay maxed out
GPU Max at 93% with powerplay maxed out
It generally maxes out at your OS's kernel's scheduler's timeslice length. Generally, this is 100hz or 1000hz. Higher than -f 1000 makes no sense. Not only that, my miner has an automatic lower limit as to not send too little work to the GPU. The actual -f maximum may be much lower.
Thanks diablo I guess I will have to make do with the hash rate till amd comes out with the new sdk for 6990. Thanks for your great miner, I am using it for the dual 6990. It hovers around 1ghash/s and its at -f 7777777. Hahah I tested and the numbers seem to slow down the hash rate when its lesser than -f 17 but anything more it hits 1ghash/s constant. Which is nice =)
GPU Max at 93% with powerplay maxed out
GPU Max at 93% with powerplay maxed out
Hi diablo I have the dummy plugs in both graphics card. And if I were to disable xfire the cards will not be recognised by the diablo software. Same goes with poclbm.
That shouldn't happen. However, leaving Crossfire on could explain your lost speed.
Hi diablo I have the dummy plugs in both graphics card. And if I were to disable xfire the cards will not be recognised by the diablo software. Same goes with poclbm.
Hi diablod3 I am facing some issues using this miner with dual 6990. With -f 1 the hash rates drop to a whooping 600000 low. I tested out different flags and found that -f 17 to 20 is the best with the highest at 1ghash/s. This is very stable compared to poclbm which fluctuates from 800mhash to 1.2ghash. I am using 11.3 + 2.4 sdk like u recommend. The preview 11.4 drivers + 2.4 sdk yield the same results. I am using windows 7 64 bit. And the only way to get the software to recognise the dual 6990 is to crossfire them. Any advice u could give me?
Thank you =)
Thank you =)
On Windows, due to stupidity on Microsoft's part, you usually need a dummy plug to make cards that don't have monitors plugged in to them turn on (this doesnt apply to Linux, nor Crossfired cards). -f controls the length of a kernel (1/n seconds, where -f 1 is a full second), and you'll only see changes at large multiples or divisors of 60 (ie, 1, 15, 30, 60, 120, 240, etc).
-f 1 tends to largely skew the realtime clock used by the OS. So, to test with -f 1, you need to run for about 10 minutes and only rely on the second number (pocblm does not provide a second number, so you can't accurately watch it).
That said, the numbers tell me you should get about 1.2 ghash total instead of 1 (or about 17% slower). I suspect a driver bug. Make absolutely sure you've turned off Crossfire and that my miner lists 4 devices.
Yeap both with dummy plugs attached. both diablo2d and poclbm will refuse to start without crossfire enabled.
I am stuck btw a fluctuating hash rate ~1.3ghash to 700mhash (poclbm) and a 1ghash hash rate diablo3d
I am stuck btw a fluctuating hash rate ~1.3ghash to 700mhash (poclbm) and a 1ghash hash rate diablo3d
Hi diablod3 I am facing some issues using this miner with dual 6990. With -f 1 the hash rates drop to a whooping 600000 low. I tested out different flags and found that -f 17 to 20 is the best with the highest at 1ghash/s. This is very stable compared to poclbm which fluctuates from 800mhash to 1.2ghash. I am using 11.3 + 2.4 sdk like u recommend. The preview 11.4 drivers + 2.4 sdk yield the same results. I am using windows 7 64 bit. And the only way to get the software to recognise the dual 6990 is to crossfire them. Any advice u could give me?
Thank you =)
Thank you =)
you need a dummy plug in the 2nd card to make the os see it
Hi diablod3 I am facing some issues using this miner with dual 6990. With -f 1 the hash rates drop to a whooping 600000 low. I tested out different flags and found that -f 17 to 20 is the best with the highest at 1ghash/s. This is very stable compared to poclbm which fluctuates from 800mhash to 1.2ghash. I am using 11.3 + 2.4 sdk like u recommend. The preview 11.4 drivers + 2.4 sdk yield the same results. I am using windows 7 64 bit. And the only way to get the software to recognise the dual 6990 is to crossfire them. Any advice u could give me?
Thank you =)
Thank you =)
You can use bitcoin -server instead of bitcoind. I'm not sure if the OSX binaries build bitcoind.
Pardon my ignorance, but how do I run bitcoin with the -server option? Terminal doesn't recognize it. Do I need to build from source and run that?
I don't understand your question. You download the OSX binaries from the Bitcoin website, unzip them, open up Terminal, cd to the directory, and then ./bitcoin -server & exit
You can use bitcoin -server instead of bitcoind. I'm not sure if the OSX binaries build bitcoind.
Pardon my ignorance, but how do I run bitcoin with the -server option? Terminal doesn't recognize it. Do I need to build from source and run that?
Please note: I screwed up testing on SDK 2.4. It does fix the CPU use bug 2.2/2.3 introduced, but I get about 71 mhash/sec on my 4850 out of 76. This puts it at the same speed as 2.3, but without the CPU use.
So, I am still recommending 10.9 through 10.11 + SDK 2.1 for 4xxx/5xxx mining, but I'm recommending 11.3 + SDK 2.4 for 6xxx.
So, I am still recommending 10.9 through 10.11 + SDK 2.1 for 4xxx/5xxx mining, but I'm recommending 11.3 + SDK 2.4 for 6xxx.
so in a terminal you run: ./bitcoind [from the bitcoin directory - skip the GUI; go with the daemon]
i'm assuming your mvn install on DiabloMiner went ok?
i'm assuming your mvn install on DiabloMiner went ok?
Here is my problem: I don't appear to have bitcoind on my computer. Even as a hidden file. I have neither a .bitcoin folder nor a bitcoin/bin folder. Where would it be otherwise on a Mac?
I didn't install DiabloMiner, I just ran the shell from Terminal. I don't know what mvn means - ?
Thanks again for your help.
You can use bitcoin -server instead of bitcoind. I'm not sure if the OSX binaries build bitcoind.
and then: *******@minty64 ~/DiabloMiner/Diablo-D3-DiabloMiner-d758eef $ ./DiabloMiner-Linux.sh -w 128 -f 1 -u ******* -p ********
?
i'm assuming your mvn install on DiabloMiner went ok?
?
i'm assuming your mvn install on DiabloMiner went ok?
You shouldn't use -w 128 unless for some strange reason it is, indeed, faster than you. -w 64 is whats recommended by AMD themselves.
Also, you only use mvn to build from source. If you download the binary zip, you don't (and can't) use this.
so in a terminal you run: ./bitcoind [from the bitcoin directory - skip the GUI; go with the daemon]
i'm assuming your mvn install on DiabloMiner went ok?
i'm assuming your mvn install on DiabloMiner went ok?
Here is my problem: I don't appear to have bitcoind on my computer. Even as a hidden file. I have neither a .bitcoin folder nor a bitcoin/bin folder. Where would it be otherwise on a Mac?
I didn't install DiabloMiner, I just ran the shell from Terminal. I don't know what mvn means - ?
Thanks again for your help.
ah, sorry - you need a mac person... seems to work just fine on macs tough, if you set it up right.
Jump to: