will there be an update for other coins like boostcoin?
remember the 5 ecc(sry your nick is too long to be remembered lol), is tweaking the 11 algo of the x13
Topic: [ANN][X11] X11/Darkcoin Gpu Miner - updated to use leaked binaries - even faster - page 8. (Read 102473 times)
May 28, 2014, 04:50:31 AM
remember the 5 ecc(sry your nick is too long to be remembered lol), is tweaking the 11 algo of the x13
May 28, 2014, 04:43:48 AM
will there be an update for other coins like boostcoin?
remember the 5 ecc(sry your nick is too long to be remembered lol), is tweaking the 11 algo of the x13
May 28, 2014, 04:40:13 AM
i have only 400-900Kh/s with 7790 and 260X on BAMT 1.6.2 (same on SMOS 1.2). On windows 8.1 i had 1200Kh/s. Why so different? 
"intensity" : "17", - up or dawn is reduces hashrate
"kernel" : "x11mod", - same darkcoin no effect
"lookup-gap" : "2", - no effect
"gpu-threads" : "1", - if 2, then rise hashrate to 1100Kh/s for 7790 (260X no effect), but some GPU is turning off
"gpu-engine" : "1100", - if gpu-thread=1, then no effect
"gpu-memclock" : "1500"
http://prntscr.com/3nbyot
P.S. What difference between x11-sgminer-bamt-build2.tgz and x11-sgminer-linux-32bit-build1.tgz?
"intensity" : "17", - up or dawn is reduces hashrate
"kernel" : "x11mod", - same darkcoin no effect
"lookup-gap" : "2", - no effect
"gpu-threads" : "1", - if 2, then rise hashrate to 1100Kh/s for 7790 (260X no effect), but some GPU is turning off
"gpu-engine" : "1100", - if gpu-thread=1, then no effect
"gpu-memclock" : "1500"
http://prntscr.com/3nbyot
P.S. What difference between x11-sgminer-bamt-build2.tgz and x11-sgminer-linux-32bit-build1.tgz?
May 28, 2014, 03:46:45 AM
will there be an update for other coins like boostcoin?
May 28, 2014, 03:02:34 AM
it's possible to optimize the jackpoint algo for amd? there is too much difference between nvidia and amd there(2MH/ vs 4MH/s)
In the past this was because AMD was much more efficient with integer operations whereas Nvidia excelled at Floating point stuff.so nothing can be done? sad...
May 28, 2014, 03:00:32 AM
I think it's time for girino to release his source code as promised.
done. (added zip with code to the shared dropbox folder).
I'm more interested in an explanation why it's so much faster!
Your crack and Lasybear's work are "sufficient" enough to copy what he has done, but CL-code itself is 100% identical and doesn't explain the speed boost..... Only thing different is the way CL-functions are called, and the use of an additional memory-block (plus pointers instead of arrays).
Still like to learn what Girino's breakthrough was and his line of thought archiving this (this knowledge, our community can use for further improvements).
Your crack and Lasybear's work are "sufficient" enough to copy what he has done, but CL-code itself is 100% identical and doesn't explain the speed boost..... Only thing different is the way CL-functions are called, and the use of an additional memory-block (plus pointers instead of arrays).
Still like to learn what Girino's breakthrough was and his line of thought archiving this (this knowledge, our community can use for further improvements).
There are many things that make it faster.
GPU's have very little "private" memory, and all declared local variables are allocated in "private" memory space, that quickly fills up and is then cached into global (yes, global) memory. So big functions with lots of variables are REALLY BAD for GPU. Breaking up the functions the way i did can give you huge speed improvements. Sequencial accesses to global memory are quite fast as they are cached in local memory by the compiler, so the use of global memory to store the intermediate hashes is still fast enough for the improvements to be worth it.
Thank you for the zip and the information, Girino !
I will try to optimize it some more with your hints about Global-mem.
May 28, 2014, 01:24:42 AM
I think it's time for girino to release his source code as promised.
done. (added zip with code to the shared dropbox folder).
I'm more interested in an explanation why it's so much faster!
Your crack and Lasybear's work are "sufficient" enough to copy what he has done, but CL-code itself is 100% identical and doesn't explain the speed boost..... Only thing different is the way CL-functions are called, and the use of an additional memory-block (plus pointers instead of arrays).
Still like to learn what Girino's breakthrough was and his line of thought archiving this (this knowledge, our community can use for further improvements).
Your crack and Lasybear's work are "sufficient" enough to copy what he has done, but CL-code itself is 100% identical and doesn't explain the speed boost..... Only thing different is the way CL-functions are called, and the use of an additional memory-block (plus pointers instead of arrays).
Still like to learn what Girino's breakthrough was and his line of thought archiving this (this knowledge, our community can use for further improvements).
There are many things that make it faster.
GPU's have very little "private" memory, and all declared local variables are allocated in "private" memory space, that quickly fills up and is then cached into global (yes, global) memory. So big functions with lots of variables are REALLY BAD for GPU. Breaking up the functions the way i did can give you huge speed improvements. Sequencial accesses to global memory are quite fast as they are cached in local memory by the compiler, so the use of global memory to store the intermediate hashes is still fast enough for the improvements to be worth it.
in your experience it is possible to optimize even more? maybe a 20% more hashrate?
May 27, 2014, 11:30:24 PM
sgminer.exe -o stratum+tcp://stratum-eu.suchpool.pw:3325 -u Sglasio.1 -p x --thread-concurrency 8193 -g 4 -I 18 -w 128 --gpu-memclock 1500 --gpu-powertune 20 --gpu-engine 1150 --gpu-fan 50-100 --shaders 2048 --lookup-gap 2
Intensity can 19 or 18 for youre choice
Get 3.3 Mhs
Temp is ok
Intensity can 19 or 18 for youre choice
Get 3.3 Mhs
Temp is ok
May 27, 2014, 11:19:08 PM
I think it's time for girino to release his source code as promised.
done. (added zip with code to the shared dropbox folder).
May 27, 2014, 09:48:53 PM
finally i installed it on my pimp
here is manual
in terminal type
pmupdate or pimpupdate
after run it again
and choose 13 to install mod x11 miner
after choose 1 to update poolmanager
and done
enjoy
here is manual
in terminal type
pmupdate or pimpupdate
after run it again
and choose 13 to install mod x11 miner
after choose 1 to update poolmanager
and done
enjoy
I did this and it installed the xllmod and then I update pool manager and it has a new look. But no longer has all the different option for mining...just "default" which was scrypt. I revert back to old andit has all the other options "dark,jackpot,scyprpt,jane.-n,etc....but not xllmod?
May 27, 2014, 09:31:21 PM
I think it's time for girino to release his source code as promised.
done. (added zip with code to the shared dropbox folder).
I'm more interested in an explanation why it's so much faster!
Your crack and Lasybear's work are "sufficient" enough to copy what he has done, but CL-code itself is 100% identical and doesn't explain the speed boost..... Only thing different is the way CL-functions are called, and the use of an additional memory-block (plus pointers instead of arrays).
Still like to learn what Girino's breakthrough was and his line of thought archiving this (this knowledge, our community can use for further improvements).
Your crack and Lasybear's work are "sufficient" enough to copy what he has done, but CL-code itself is 100% identical and doesn't explain the speed boost..... Only thing different is the way CL-functions are called, and the use of an additional memory-block (plus pointers instead of arrays).
Still like to learn what Girino's breakthrough was and his line of thought archiving this (this knowledge, our community can use for further improvements).
There are many things that make it faster.
GPU's have very little "private" memory, and all declared local variables are allocated in "private" memory space, that quickly fills up and is then cached into global (yes, global) memory. So big functions with lots of variables are REALLY BAD for GPU. Breaking up the functions the way i did can give you huge speed improvements. Sequencial accesses to global memory are quite fast as they are cached in local memory by the compiler, so the use of global memory to store the intermediate hashes is still fast enough for the improvements to be worth it.
May 27, 2014, 05:58:20 PM
Tried running this with the new 14.6 amd drivers and it showed a hashrate of more then 4mh with 280x. However, I got nothing besides HW errors.
Made a thread about it here:
https://bitcointalksearch.org/topic/new-amd-drivers-146-possible-speed-increase-627142
Need someone else to give it a try and reprt back. trying to work out if it's somnething i have done or the drivers/sgminers thats having problems.
Made a thread about it here:
https://bitcointalksearch.org/topic/new-amd-drivers-146-possible-speed-increase-627142
Need someone else to give it a try and reprt back. trying to work out if it's somnething i have done or the drivers/sgminers thats having problems.
legendary
Activity: 1862
Merit: 1011
Reverse engineer from time to time
May 27, 2014, 03:57:32 PM
it's possible to optimize the jackpoint algo for amd? there is too much difference between nvidia and amd there(2MH/ vs 4MH/s)
In the past this was because AMD was much more efficient with integer operations whereas Nvidia excelled at Floating point stuff. May 27, 2014, 03:56:25 PM
it's possible to optimize the jackpoint algo for amd? there is too much difference between nvidia and amd there(2MH/ vs 4MH/s)
legendary
Activity: 1862
Merit: 1011
Reverse engineer from time to time
May 27, 2014, 03:39:27 PM
I think it's time for girino to release his source code as promised.
I'm more interested in an explanation why it's so much faster!
Your crack and Lasybear's work are "sufficient" enough to copy what he has done, but CL-code itself is 100% identical and doesn't explain the speed boost..... Only thing different is the way CL-functions are called, and the use of an additional memory-block (plus pointers instead of arrays).
Still like to learn what Girino's breakthrough was and his line of thought archiving this (this knowledge, our community can use for further improvements).
May 27, 2014, 03:36:45 PM
I think it's time for girino to release his source code as promised.
I'm more interested in an explanation why it's so much faster!
Your crack and Lasybear's work are "sufficient" enough to copy what he has done, but CL-code itself is 100% identical and doesn't explain the speed boost..... Only thing different is the way CL-functions are called, and the use of an additional memory-block (plus pointers instead of arrays).
Still like to learn what Girino's breakthrough was and his line of thought archiving this (this knowledge, our community can use for further improvements).
legendary
Activity: 1862
Merit: 1011
Reverse engineer from time to time
May 27, 2014, 02:40:35 PM
I think it's time for girino to release his source code as promised.
May 27, 2014, 02:18:13 PM
finally i installed it on my pimp
here is manual
in terminal type
pmupdate or pimpupdate
after run it again
and choose 13 to install mod x11 miner
after choose 1 to update poolmanager
and done
enjoy
Where is manual? here is manual
in terminal type
pmupdate or pimpupdate
after run it again
and choose 13 to install mod x11 miner
after choose 1 to update poolmanager
and done
enjoy
if you cant see the manual, better read it again, if you dont get it, read it again.
May 27, 2014, 01:10:47 PM
finally i installed it on my pimp
here is manual
in terminal type
pmupdate or pimpupdate
after run it again
and choose 13 to install mod x11 miner
after choose 1 to update poolmanager
and done
enjoy
Where is manual? here is manual
in terminal type
pmupdate or pimpupdate
after run it again
and choose 13 to install mod x11 miner
after choose 1 to update poolmanager
and done
enjoy
May 27, 2014, 05:05:29 AM
is it possible to mine jackpotcoin with this miner?
Jump to: