, please . 
Topic: CCminer(SP-MOD) Modded NVIDIA Maxwell / Pascal kernels. - page 630. (Read 2347641 times)
Epsylon3 you give a miner also to holders of nvidia, even slower than what you are using , please .
, please . Wolfo released it for free, he was payed very well i presume?
Looking at how amd does against nvidia wolf wasn't payed so well.
Yeah! Sure there is a much faster amd miner for private from Wolf ))
Wolfo released it for free, he was payed very well i presume?
Looking at how amd does against nvidia wolf wasn't payed so well.
Wolfo released it for free, he was payed very well i presume?
0.1 btc was too much? And 6 x 1070 is cheap?
Ok, i close the crowfunding for some days... stop sending me tips 
i reached the reasonable goal of 1 BTC
Each new donation reduce the overall possible profit... hard choice to do but the best way i found to reduce the hype effect over mining rewards
will maybe do another round for a smaller donation this week end
open source should be available during july (after the 20th july)
- mode accountant off -
i reached the reasonable goal of 1 BTCEach new donation reduce the overall possible profit... hard choice to do but the best way i found to reduce the hype effect over mining rewards
will maybe do another round for a smaller donation this week end
open source should be available during july (after the 20th july)
- mode accountant off -
yeah the hashrate is already increasing too much, better to limit it for the time being
and no i'm not even mining it
my dream was always to see a very high profitable coin that will remain profitable forever, no dumped to the ground after 1 week/month/etc...
Ok, i close the crowfunding for some days... stop sending me tips i reached the reasonable goal of 1 BTC
Each new donation reduce the overall possible profit... hard choice to do but the best way i found to reduce the hype effect over mining rewards
will maybe do another round for a smaller donation this week end
open source should be available during july (after the 20th july)
- mode accountant off -
i reached the reasonable goal of 1 BTCEach new donation reduce the overall possible profit... hard choice to do but the best way i found to reduce the hype effect over mining rewards
will maybe do another round for a smaller donation this week end
open source should be available during july (after the 20th july)
- mode accountant off -
Small request to developers, please show the intensity on GPUs when your miner is running somewhere. You shouldn't need to request the intensity for a GPU so you can tweak it. Saves both parties a extra step.
That would be nice, unfortunately the default intensity of an algo is set inside that algo-specific file and is not store anywhere, so there is no nice way of doing it.
To do it the right way, there should be an algo structure holding default intensities for the various cards, so that it is initialised with either the user supplied one or the default, and printed at the beginning.
To be fair, sgminer doesn't even have algo-specific (let alone device-specific) default intensities, AFAIK.
Anyways it's pretty easy to spot them, just look at the file named as the algo plus ".cu", near the beginning you will see the code which sets intensities (throughput).
It's already implemented in SP_MOD v80.
Small request to developers, please show the intensity on GPUs when your miner is running somewhere. You shouldn't need to request the intensity for a GPU so you can tweak it. Saves both parties a extra step.
That would be nice, unfortunately the default intensity of an algo is set inside that algo-specific file and is not store anywhere, so there is no nice way of doing it.
To do it the right way, there should be an algo structure holding default intensities for the various cards, so that it is initialised with either the user supplied one or the default, and printed at the beginning.
To be fair, sgminer doesn't even have algo-specific (let alone device-specific) default intensities, AFAIK.
Anyways it's pretty easy to spot them, just look at the file named as the algo plus ".cu", near the beginning you will see the code which sets intensities (throughput).
When it's mining it could simply do like (i-20) or (intensity 20) in the command line or when it first starts, show it next to each GPU it's winding up.
Yeah, I remember tweaking SGminer for intensity back when I mined with AMD.
Small request to developers, please show the intensity on GPUs when your miner is running somewhere. You shouldn't need to request the intensity for a GPU so you can tweak it. Saves both parties a extra step.
That would be nice, unfortunately the default intensity of an algo is set inside that algo-specific file and is not store anywhere, so there is no nice way of doing it.
To do it the right way, there should be an algo structure holding default intensities for the various cards, so that it is initialised with either the user supplied one or the default, and printed at the beginning.
To be fair, sgminer doesn't even have algo-specific (let alone device-specific) default intensities, AFAIK.
Anyways it's pretty easy to spot them, just look at the file named as the algo plus ".cu", near the beginning you will see the code which sets intensities (throughput).
Small request to developers, please show the intensity on GPUs when your miner is running somewhere. You shouldn't need to request the intensity for a GPU so you can tweak it. Saves both parties a extra step.
sorry to post that here, but lbry cuda miner preview (binaries with sources) is on sale for 0.1 BTC... :p
PM me
will maybe get a tip from sp this time ? :p who know ?
tested working without issues on all cuda arch (3.0 to 6.1) on windows and linux
What about 970 and 750ti? PM me
will maybe get a tip from sp this time ? :p who know ?
tested working without issues on all cuda arch (3.0 to 6.1) on windows and linux
Code:
GPU #0: Gigabyte GTX 1080, 270.14 MH/s
GPU #1: GeForce GTX 1070, 192.61 MH/s
accepted: 339/339 (diff 0.115), 462.73 MH/s yes!
Stratum difficulty set to 16 (0.06250)
lbry block 11086, diff 9152.967
GPU #0: Gigabyte GTX 1080, 270.92 MH/s
accepted: 340/340 (diff 1.919), 462.74 MH/s yes!
GPU #1: GeForce GTX 1070, 192.61 MH/s
accepted: 339/339 (diff 0.115), 462.73 MH/s yes!
Stratum difficulty set to 16 (0.06250)
lbry block 11086, diff 9152.967
GPU #0: Gigabyte GTX 1080, 270.92 MH/s
accepted: 340/340 (diff 1.919), 462.74 MH/s yes!
)) 1080 crazy profitable 
bu iHaven't any o them. 
( Still wating for rx 470's sorry to post that here, but lbry cuda miner preview (binaries with sources) is on sale for 0.1 BTC... :p
PM me
will maybe get a tip from sp this time ? :p who know ?
tested working without issues on all cuda arch (3.0 to 6.1) on windows and linux
PM me
will maybe get a tip from sp this time ? :p who know ?
tested working without issues on all cuda arch (3.0 to 6.1) on windows and linux
Code:
GPU #0: Gigabyte GTX 1080, 270.14 MH/s
GPU #1: GeForce GTX 1070, 192.61 MH/s
accepted: 339/339 (diff 0.115), 462.73 MH/s yes!
Stratum difficulty set to 16 (0.06250)
lbry block 11086, diff 9152.967
GPU #0: Gigabyte GTX 1080, 270.92 MH/s
accepted: 340/340 (diff 1.919), 462.74 MH/s yes!
GPU #1: GeForce GTX 1070, 192.61 MH/s
accepted: 339/339 (diff 0.115), 462.73 MH/s yes!
Stratum difficulty set to 16 (0.06250)
lbry block 11086, diff 9152.967
GPU #0: Gigabyte GTX 1080, 270.92 MH/s
accepted: 340/340 (diff 1.919), 462.74 MH/s yes!
How long is it going to be in 'preview' phase before you release it?
sorry to post that here, but lbry cuda miner preview (binaries with sources) is on sale for 0.1 BTC... :p
PM me
will maybe get a tip from sp this time ? :p who know ?
tested working without issues on all cuda arch (3.0 to 6.1) on windows and linux
PM me
will maybe get a tip from sp this time ? :p who know ?
tested working without issues on all cuda arch (3.0 to 6.1) on windows and linux
Code:
GPU #0: Gigabyte GTX 1080, 270.14 MH/s
GPU #1: GeForce GTX 1070, 192.61 MH/s
accepted: 339/339 (diff 0.115), 462.73 MH/s yes!
Stratum difficulty set to 16 (0.06250)
lbry block 11086, diff 9152.967
GPU #0: Gigabyte GTX 1080, 270.92 MH/s
accepted: 340/340 (diff 1.919), 462.74 MH/s yes!
that is the hashrate?
how much libry with one 1070? it look very profitable
- deleted - dont send me money anymore please
sorry to post that here, but lbry cuda miner preview (binaries with sources) is on sale for 0.1 BTC... :p
PM me
will maybe get a tip from sp this time ? :p who know ?
tested working without issues on all cuda arch (3.0 to 6.1) on windows and linux
PM me
will maybe get a tip from sp this time ? :p who know ?
tested working without issues on all cuda arch (3.0 to 6.1) on windows and linux
Code:
GPU #0: Gigabyte GTX 1080, 270.14 MH/s
GPU #1: GeForce GTX 1070, 192.61 MH/s
accepted: 339/339 (diff 0.115), 462.73 MH/s yes!
Stratum difficulty set to 16 (0.06250)
lbry block 11086, diff 9152.967
GPU #0: Gigabyte GTX 1080, 270.92 MH/s
accepted: 340/340 (diff 1.919), 462.74 MH/s yes!
BTC to address in your Sig?
EDIT: Read to fast. I just noticed the pm you.
sorry to post that here, but lbry cuda miner preview (binaries with sources) is on sale for 0.1 BTC... :p
PM me
will maybe get a tip from sp this time ? :p who know ?
tested working without issues on all cuda arch (3.0 to 6.1) on windows and linux
PM me
will maybe get a tip from sp this time ? :p who know ?
tested working without issues on all cuda arch (3.0 to 6.1) on windows and linux
Code:
GPU #0: Gigabyte GTX 1080, 270.14 MH/s
GPU #1: GeForce GTX 1070, 192.61 MH/s
accepted: 339/339 (diff 0.115), 462.73 MH/s yes!
Stratum difficulty set to 16 (0.06250)
lbry block 11086, diff 9152.967
GPU #0: Gigabyte GTX 1080, 270.92 MH/s
accepted: 340/340 (diff 1.919), 462.74 MH/s yes!
Contribute to this developer, as he has worked very hard on this miner for lbry, contact me or him https://bitcointalksearch.org/topic/lbryio-dicussion-thread-1541268
sorry to post that here, but lbry cuda miner preview (binaries with sources) is on sale for 0.1 BTC... :p
PM me
will maybe get a tip from sp this time ? :p who know ?
tested working without issues on all cuda arch (3.0 to 6.1) on windows and linux
EDIT (14 July) : dont send me money anymore please !
PM me
will maybe get a tip from sp this time ? :p who know ?
tested working without issues on all cuda arch (3.0 to 6.1) on windows and linux
Code:
GPU #0: Gigabyte GTX 1080, 270.14 MH/s
GPU #1: GeForce GTX 1070, 192.61 MH/s
accepted: 339/339 (diff 0.115), 462.73 MH/s yes!
Stratum difficulty set to 16 (0.06250)
lbry block 11086, diff 9152.967
GPU #0: Gigabyte GTX 1080, 270.92 MH/s
accepted: 340/340 (diff 1.919), 462.74 MH/s yes!
EDIT (14 July) : dont send me money anymore please !
From my experience 1.1x core/memory clock usually results in slightly less than 1.1x rev. and 1.2x power. The optimal operating point is therefore when 20% of power costs less than 10% of rev. If everything's ideal it's not until power cost reaches 0.5x rev. when one might consider throttling.
I recently heard that 1.1x core/memory clock would result in 1.3x power but I couldn't find the source any more. In that case throttle when power cost = 0.3x rev.
However power efficiency is quite something for us who live in apartments. The rig cannot draw more than x kwh from the wall and we often have more than enough BTCBTCBTC to invest. Building rigs that would get the most profit given x kwh requires quite a bit of down clocking.
I recently heard that 1.1x core/memory clock would result in 1.3x power but I couldn't find the source any more. In that case throttle when power cost = 0.3x rev.
However power efficiency is quite something for us who live in apartments. The rig cannot draw more than x kwh from the wall and we often have more than enough BTCBTCBTC to invest. Building rigs that would get the most profit given x kwh requires quite a bit of down clocking.
If you can get higher clocks at the same voltage, it's practically free performance.
No: even at the same voltage, higher clock speed will use more power:
"
There are several factors contributing to the CPU power consumption; they include dynamic power consumption, short-circuit power consumption, and power loss due to transistor leakage currents.
The dynamic power consumption originates from the activity of logic gates inside a CPU. When the logic gates toggle, energy is flowing as the capacitors inside them are charged and discharged. The dynamic power consumed by a CPU is approximately proportional to the CPU frequency, and to the square of the CPU voltage.
"
so it's linear but in practice it's more than that because of leakage currents and increased fan speed.
And I already mentioned that, but you snipped it out. The amount of hashrate you get out is much higher proportionally to the amount of power use. It's almost negligible, baring overvolting.
It's definitely not a linear relationship. In overclocking higher clock speeds will definitely need a lot more power then lower clock speeds. If it was linear, efficiency would be identical across all clocks as efficiency is a multiplicative relationship.
Fan power usage is next to nothing and temps are more so directly related to operating voltage then clock speeds. At a certain threashold +/- 5% that can be made up simply by chip binning (getting a more efficient chip).
My best results are almost always a combination of overclocking + undervolting. It's just a bit of a pain to find what are the fastest stable settings for each algorithm (and even between releases, as the performance/stress for a given algorithm changes).
This is really no different then overclocking at stock voltage. You're trying to raise the frequency to the highest possible with the current operating voltage. Undervolting lowers that. Overclocking is definitely quite efficient at getting every last ounce of performance out at a certain power envelope and uses very little power comparatively to going up and down the voltage ladder.
Jump to: