|
Nvidia owners please help.
What miner are you using.
Tried spreadminer last version and receiving "share does not validate on CPU" on all my rigs with 1060/1070/1080/1080ti
Tried stock clocks - doesn't help. Tried VC2010, VC2010SP1 - doesn't help/a
How do you mine?
|
|
|
|
I think some diff_set algo started to work. Now 2 small rigs received 256diff, not 409.6 as a big one.
looks like stratum was restarted again. same thing happened yesterday. stratum was restarted and all the worker diff went back to normal, but after it ran for a while the diff climbed again. last night i had a 6xgpu rig and 1xgpu rig all running at the same diff of 409, which is just insanely high for a single or 2x gpu rigs. i'm guessing that it's this runaway high diff that was at least partially responsible for that terrible run of luck the pool had last night. Still 256diff on small rig and 409 on big one. Better be 150 on small, but better than 409. Manual setting would be great. Or division by 1.5 of current one |
|
|
|
|
I think some diff_set algo started to work. Now 2 small rigs received 256diff, not 409.6 as a big one.
|
|
|
|
You can't dual mine Skein+Eth. Since you have two cards, you could use one to mine Skein, and the other to mine Eth.
Technically, the one that you mine Eth could dual mine one of the compatible coins like Lbry, Pascal, Decred, or Sia. That would mean you are actually mining 3 coins with two cards.
Nvidia cards are not great at dual mining though. It's probably best to stick with one algorithm/coin, and use both the mine the crap out of it. The 1080ti is a great performer on certain types of algorithms. Check whattomine.com to see what some of those are.
1080/1080Ti are very good in dual mining, only their ETH hashrate is not good which is compensated by much more sia/lbry/dcr/pasc Anyway there are a lot of other algos where they truly shine. |
|
|
|
@crys
can you let us set the difficulty manually? while you try to fix you're automatic difficulty algorith.
Totally agree! The automatic algorithm doesn't work at all. Every Rig get 409.6diff on pool (1.6 in the miner) in 15-30 minutes. While one has 6*1080 and another only 2*1080. P.S. Right now something weird is shown on the pool all numbers are divided by 10.  |
|
|
|
Correct
krxl is doing nothing new. He tune the kernel to run faster on the th 1080ti. And the speed has improved slightly.
Now show me 35mhash on the gtx 1070.
It working faster only on 1-4 gpu rigs... On multi gpu (6-8) rigs with 1080 ti sp-mod still faster SPmod 3/5 gives 231Mh/s on 6*1080 CWI gives 250MH/s on 6*1080 same clocks. |
|
|
|
I run the cards at the +/- best efficiency (MH per watt), I'm not after highest possible speed regardless of the power consumption.
Profitability today is 10s times more than electricity cost (at least in most of the areas). Mine 1070 run at 56-57Mh/s without no tweaking more than juast move the slider in Afterburner and no overheating. The difference covers all additional costs. So what's the point of that? How many watts does the 1070 draw at that speed according to the miner? 56-57 = 150W 53-54 = 135W |
|
|
|
I run the cards at the +/- best efficiency (MH per watt), I'm not after highest possible speed regardless of the power consumption.
Profitability today is 10s times more than electricity cost (at least in most of the areas). Mine 1070 run at 56-57Mh/s without no tweaking more than juast move the slider in Afterburner and no overheating. The difference covers all additional costs. So what's the point of that? |
|
|
|
Can you please lower the maximum difficulty for lowdiff port. All my rigs stabilize with diff 2.5 (both Sigt and DNR) after 30-60minutes, and to my opinion it is too high even for 6/1080. And it is completely unacceptable for 2/1080 or 5/1060 etc. But they also get the same 2.5diff. I think 1-1.5 is more than enough. P.S. DNR lowdiff starts with extremely lowdiff so that many shares are rejected at the beginning. 0.25 (as with SIGT) wil work much better. so would a max of 1.6diff work? ... then push anything higher to the hidiff port? ... we can try - and let me know how it goes ... in fact - a few seconds interruption to the sigt mining - and ill get it restarted now ... interruption is momentary ... edit - changed this for the denarius stratum also ... let see how it all goes now ... #crysx Thank you. I haven't restarted miners and for DNR I've got 1.6diff for 6x1070. But for Sigt for now i've got 1diff for 6x1080. Lets see where it will stop. Anyway as for now I see hashrate on the pool very close to the miner. P.S. But the starting difficulty for DNR is only 0.007 - it is very low - for cpu miner maybe OK, but not for gpu. I get 10-20% of rejects at the beginning, it lowers quickly but not good anyway. P.P.S Several minutes later 6*1080 also are on 1.6Diff. |
|
|
|
Can you please lower the maximum difficulty for lowdiff port. All my rigs stabilize with diff 2.5 (both Sigt and DNR) after 30-60minutes, and to my opinion it is too high even for 6/1080. And it is completely unacceptable for 2/1080 or 5/1060 etc. But they also get the same 2.5diff. I think 1-1.5 is more than enough. P.S. DNR lowdiff starts with extremely lowdiff so that many shares are rejected at the beginning. 0.25 (as with SIGT) wil work much better. |
|
|
|
What about bad luck for denarius?
It is 120-140 constantly for several days. While signatum has 60-80-90 the same days.
P.S. Does anybody know how to check yiimp pool for luck, or any other mining DNR?
have you taken notice of the network hashrate? ... sigt - Net Hashrate 1,580,681.87 MH/s dnr - Net Hashrate 24,173.70 MH/s then combine that with the pool hashrate and compare what 'luck' ( which is a completely false value mostly - as the diff and hashrate change constantly ) the pool might have ... zpool - 9.2gh tribus ... yiimp - 36.5 tribus ... CWI-Pool Denarius - 1.6gh tribus ... its all relative ... the more miners to the pool - the higher the hashrate - the better the chance ( or 'luck' ) of solving a block ... network hashrate play a massive part in this also ... as the network hashrate goes up - so does the network difficulty ... and thats what creates the so called 'luck' making it difficult ( which is also why its called difficulty  ) ... the network diff for tribus right now tho is 1626 - which is pretty high for this algo ... because right this second - the network hash rate is 156gh ... our pool has 1.6gh ... again - its all relative ... when we DO solve a block - we get higher rewards per miner - because there are less miners ... but the chances of solving a block is far less with less miners ... #crysx Actually you didn't answer the question. Your pool hashrate relative to SIGT network is on the same board as with DNR: SIGT Est. Avg. Time per Round (Network) 45 seconds Est. Avg. Time per Round (Pool) 25 minutes 10 seconds DNR Est. Avg. Time per Round (Network) 31 seconds Est. Avg. Time per Round (Pool) 20 minutes 18 seconds But the "luck" factor is constantly different. So I just asked if someone know how to find "luck" of yiimp based pools. Whether it is normal for all (bad luck) or just bad luck for your pool. |
|
|
|
|
What about bad luck for denarius?
It is 120-140 constantly for several days. While signatum has 60-80-90 the same days.
P.S. Does anybody know how to check yiimp pool for luck, or any other mining DNR?
|
|
|
|
2 weeks have past, and still nobody has managed to create a faster opensource signatum kernel based on your work. Stop trolling and show some skills.
I think you'd better write good code than make wars on forum. Your skunk miner was already beated in terms of speed at least by CWI. Their miner completely beats yours in terms of CPU usage which is 0-0.3% usual, while yours uses 1-2-3-4 cores completely depending on intensity. Your sp3/5 give ~231Mh/s on 6*1080 while CWI 250Mh/s. The same clocks. |
|
|
|
What settings and what miner you are using. I can only hit 90ish with 7x 1060's. I am using CCMiner.
There are several miners that can do 19-21Mh on 1060OC. |
|
|
|
Is the Russian-speaking branch ?
А зачем? |
|
|
|
Tell us the settings for mine with amd pls i have one rig amd and i would to use it for mining sigt
Honestly, don't bother. Mine ZEC if you are on AMD. getting 113 mh/s on my 7x rx 470 4gb rig 5*1060 = 103Mh/s |
|
|
|
On one rig I always get smashed numbers/letters in the miner window. It is working but looks weird. Tried to resize window, restarted - doesn't help. Some time after start it looks normal but later like this: https://s2.postimg.org/a3cf6w1eh/123.jpg |
|
|
|
You are the last person to tell that no gpu miner for nist5 exist.
Gpu miners exist, but most of the new coins you see today doesn't support mining with the JSON-RPC html protocol (getwork()) in the wallet. This meens that without a pool, you cannot use ccminer or sgminer to solo-mine. I linked 2 new coins and asked for pools, and it turned out that they had pools already. Here is my original mesage. And that is what I pointed on. It is lie. Because Gpu miners exist (for at least a year and you definitely knew that as far as you uses best of them as the basis), pools exist (CTIC2 had the pool from the beginning). |
|
|
|
Since last night the pool has extremely good luck(unlike previous days), for 16 hours i got what i was suppose to get for 24 hours I dont know if its coincidence but its since i changed to the new 9.8 version of the miner. Не каркай. |
|
|
|
Most of alexis work is based on my opensource optimized maxwell ccminer kernels. I have more than 1000 commits to github. Don't forget this... Anyway, the unreleased nist5 private is doing 55mhash. Ccminer 2.1 45 mhash and alexis 1.0.0 48mhash.
Gtx 1070 same clocks and launch config.
I understand that. And anyway you make good job. I just noticed that lie is not good thing. You are the last person to tell that no gpu miner for nist5 exist. Also with the pools. CXT&CTIC2 were already on popular pools for some time (sorry for my bad sequence of tenses). |
|
|
|
|
Show Posts
