|
Hi Doc
I'm trying to setting up SRB in Awesomeminer. But I created two workers (one for 580 8GB and other for 570 4GB) and I can't run separated 'cause I can't set it by command line (like -d or -di).
Is there a possibility to setup the config.txt as .bat arguments? Like -d 1 -i 54 -t 2?
|
|
|
|
@JCE-Miner I did some tests using double_hash with Ryzen 7 1700 at IPBC, and I think it's worse than single hash. Ya, the cache is the problem. Ryzen 7 1700 runs with 16 threads around 2200 at 3.6GHz 2933 RAM/L3. With double hash, more than 16MB cache is used. With Ryzen 5 1600, with just 12 threads, there is 4MB free to play  . Is nice to see R5 1600 shinning. I'm thinking about a second RIG with a R5, but I was reluctant about mining performance. |
|
|
|
Can you give a config.json with those coins?
At this point it's just a mess of bad info.. so not right now. It's not working this time at all Nem kezelt kivétel: System.ArgumentNullException: A gyűjtemény nem lehet NULL. Paraméter neve: c a következő helyen: System.Collections.ArrayList.InsertRange(Int32 index, ICollection c) a következő helyen: System.Collections.ArrayList.AddRange(ICollection c) a következő helyen: AwesomeMinerCoinUpdater.AwesomeMinerCoinUpdater..ctor(Boolean EnablePriceCache) a következő helyen: AwesomeMinerCoinUpdater.AwesomeMinerCoinUpdater.Main(String[] args) same here, even without a config.json file |
|
|
|
Even in assembly, we have very few control of the cache level. Just a few instructions: the movntdqa and some prefetchnt (nt == non temporal == no cache). JCE mostly let the CPU handle everything, except in "use_cache":false mode.
Progressing on assembly for multi-hash on AES-64 (the easiest to write).
I reach 79 h/s on Hexa-hash on CV-v7, which is very bad, but when using IPBC where the JCE multihash does marvels, i get some interresting results. More tests and optims to do.
Surprisingly, i didn't run out of registers in x64 with 6 hashes at the same time. But on 32 bits it will be terrible. I'll provide hexa-hash 32-bits for code symetry, but probably useless.
edit : i reach 1700 h/s on on IPBC my stock ryzen 1600 with JCE 0.26 and its multihash, with config multi
3+1+1+1+1+1+3+1+1+1+1+1
so 12 threads, two triple and ten simple. Curiously the double are less good...
That's the fastest combination I found. On CN-v7 still cannot beat the default 8x simple
Damn! Awesome for a stock hexa-core Ryzen! How to setup this? I can do some testes in Ryzen 7 to see the scalling with 8 cores (but the same cache) |
|
|
|
Hi ! Nice i've users from all the world  Bitcointalk magic I advise to use the -q parameter : it quits at first network problem. And with a .bat you can loop forever: :MineXmr
jce_cn_cpu_miner64 -q --low ......
goto :MineXmr
this way at each connection problem you restart miner, you'll loose just a few seconds at each problem, probably negligible. And the default wait between two network attemps is 5s, so restarting the miner or waiting for 5s is just the same delay. I'm doing a huge refactoring of my assembly for factorize more, to provide multi-hash from triple- to hexa- at the same time. Current version provides only simple and double. I'm from the newest Brazil's province. Yeah, Bitcointalk magic Just for feedback: Ryzen 7 1700 at 3.6GHz and 3200MHz memory (16-16-16-36 1T) can reach 2400H/s mining CN-Lite. I'm having problems to stabilize at this. At 2933 memory I can reach around 2200H/s. So, the bottleneck is clairly de memory. Is there a specific timing that improve CN mining? I know the L3 cache runs at memory frequency and takes advantage of main latencies. For GPUs I know it likes FAW lowered. except if you go over your cache limits, memory shoudn't have big impact. it's better to play with Performance or similar modes in Bios which lower cache timings and give huge cryponight speed boost. thanks for the report baz, i'm working on multi hash over 2, that's good for you the cn-light and ipbc miners to the guy who quoted the full doc : it makes the topic harder to read  The Ryzen's L3 cache runs at memory clock. There is a huge gain from 2133 to 2800, and smaller gains at 2800+ for Cryptonight V7. For Lite, as I can see, there is more room to improvements clocking high memory (and, of course, L3 cache). 10% from 2933 to 3200. |
|
|
|
Hi ! Nice i've users from all the world Bitcointalk magic I advise to use the -q parameter : it quits at first network problem. And with a .bat you can loop forever: :MineXmr
jce_cn_cpu_miner64 -q --low ......
goto :MineXmr
this way at each connection problem you restart miner, you'll loose just a few seconds at each problem, probably negligible. And the default wait between two network attemps is 5s, so restarting the miner or waiting for 5s is just the same delay. I'm doing a huge refactoring of my assembly for factorize more, to provide multi-hash from triple- to hexa- at the same time. Current version provides only simple and double. I'm from the newest Brazil's province. Yeah, Bitcointalk magic Just for feedback: Ryzen 7 1700 at 3.6GHz and 3200MHz memory (16-16-16-36 1T) can reach 2400H/s mining CN-Lite. I'm having problems to stabilize at this. At 2933 memory I can reach around 2200H/s. So, the bottleneck is clairly de memory. Is there a specific timing that improve CN mining? I know the L3 cache runs at memory frequency and takes advantage of main latencies. For GPUs I know it likes FAW lowered. |
|
|
|
{CoinFullName: "Graft", CoinShortName: "GRFT", Algo: "CryptoNight", BlockReward: 1718.7348, BlockTime: 120, BlockExplorer: " https://graft.hashvault.pro/api/network/stats"} {CoinFullName: "Stellite", CoinShortName: "XTL", Algo: "CryptoNight", BlockReward: 17962.55, BlockTime: 60, BlockExplorer: " https://stellite.hashvault.pro/api/network/stats"} {CoinFullName: "Haven", CoinShortName: "XHV", Algo: "CryptoNight", BlockReward: 32.4862 , BlockTime: 120, BlockExplorer: " https://haven.hashvault.pro/api/network/stats"} This works (Using HashVault API,, all soins that this pool supports).. but XHV is not listed on any Exchange CoinUpdater queries so again no help.. Thanks a lot! It doesn't work with Cryptonight-V7/Heavy algorithm config? |
|
|
|
|
Hi JCE. I`m using your miner for the last 2 weeks and it's very good. The best for CN-Lite
But I have a annoying issue: my internet connection is bad (Thanks, Brazil) and when I lost connection, after some time, JCE miner stops trying to connect and stucks.
Is there a argument to avoid it and try to connect forever?
|
|
|
|
Does anyone have MOD for this particular memory Hynix H5GC8H24MJ (new model)?
I tried with these cards:
XFX RX 580 8GB Hynix
NITRO RX 580 8GB Hynix
MSI ARMOR RX 580 8GB Hynix
All with the same memory (H5GC8H24MJ)
MOD: 777000000000000022AA1C00B56A6D46C0551017BE8E060C006AE6000C081420EA8900AB0300000 01B162C31C0313F17
Tried with strap 1500 and 1750.
The best I did was:
720~ h/s with monero7
750~ h/s with heavy
GPU and MEM frequencies by default
"double_threads": true
"intensity": 51, "worksize": 8, "threads": 2
Drivers: Blockchain-Aug23 with Pixel Patcher 1.4.6
Install last driver. Use mod 777000000000000022AA1C00B56A6D46C0551017BE8E060C006AE6000C081420EA8900AB0300000 01B162C31C0313F17 Than set memory to 2150 (maybe some lower depends on card quality - 2140 or 2125) In SRB try intensity 72, 80, 88, 96, 104, 108. Every try wait 3-5 minutes... Aren't there other straps for Cryptonight + Hynix 8GB? These straps are good for ETH (31+ in good ICs) but for CN is quite slow. I think we have room to improvement. Unafortunately (or fortunately) I dont have a 580 8GB with Hynix here to try to change something |
|
|
|
Doc, I don't know if it's possible to solve my issue, because it's a little specific I have three different GPU variants, that have different strong points and weaknesses: RX580 8GB (awesome for Heavy) RX570 4GB (good for V7) R7 260X 2GB (not bad for Lite) To make use of the best of each card I've had to rename the SRBMiner (to avoid the check) executable and run three instances, one for each card. So, I run three SRBMiners lol Is possible (or, better, it worth the work) to run different algorithms/pools in the same miner in the future? (if not, it's fine. I like your miner  ) lol sorry it's not in plan any soon Fine. Working with multiple instances is okay. I see it doesn't run with default settings (and executable name), the miner says is already running (I have to rename .exe and change it in the bat, as explained in my previus reply). It's just for avoid two instances running in the same GPU or is there some issue running multiple SRBMiners? |
|
|
|
Doc, I don't know if it's possible to solve my issue, because it's a little specific I have three different GPU variants, that have different strong points and weaknesses: RX580 8GB (awesome for Heavy) RX570 4GB (good for V7) R7 260X 2GB (not bad for Lite) To make use of the best of each card I've had to rename the SRBMiner (to avoid the check) executable and run three instances, one for each card. So, I run three SRBMiners lol Is possible (or, better, it worth the work) to run different algorithms/pools in the same miner in the future? (if not, it's fine. I like your miner ) EDIT: For who is curious about 260X performance: Cryptonight: 239H/s Crptonight-Heavy: 218H/s Cryptonight-Lite: 640H/s At 1000/1800 1000mv |
|
|
|
Good lord.
Guys. It says there, right in the tool - it's 1080 and 1080Ti (okay, and now TitanXP) only. Literally.
Your P104-100 will not work. Your P106-100 will not work. Your RX470 will definitely not work.
The tool is for ETHhereum. That's why it's called ETHlargement. That's the joke.
Your shares get reflected at the pool. Wait a few damn hours.
No, this tool isn't responsible for killing your rigs, eating your children, your MyEtherWallet being hacked or your land rates increasing.
If you don't trust OhGodACompany, don't run it.
However: if you DO have a TitanXP, 1080 or 1080Ti that isn't running this tool correctly, please, let us know on GitHub or here. These edge cases are usually due to users not running as root/admin, but, hey, who knows, maybe there's RevC memory wandering out there somwhere.
I understand your post A tool with huge people intersted will generate that kind of questions. I think you would put this message to OP lol |
|
|
|
I think its amd user
As an AMD user I don't mine ETH for a long time ))) +1 My last time mining ETH was 8 months ago ;p Newbies says it's a miracle. Yeah, 50MH/s+ is a kind of miracle, but we say "miracle" for something scientific that we cannot explain, and a newbie doesn't know nothing about RRD, FAW, 32AW. For then, if they cannot explain, is a miracle. So, they are acting like they are: newbies. |
|
|
|
V1.4.7
- Added shutdown_temperature parameter (in config.txt) which shuts down the system, default is 95c if not set
- Added average time to find share in stats
- Added keepalive option in pools to prevent possible connection timeouts (pool must support this method)
- Possible fix for Nicehash "job not found"
- Added kernel parameter to gpu_conf
: Keepalive does not work with Nanopool, Nicehash, Minergate. Maybe some others too. Even if you set it to TRUE on these pools, it will auto turn them off.
: kernel parameter can be used so if you have a mixed gpu rig with new+old cards, and the old ones work better with pre-gcn kernels for example
Thanks, doc! About old cards: my old R7 260X is coming from reballing and I want to ask for who have old GCN2 cards: SRB is beating (very) old Claymore 9.7? If yes, what configuration I can start from? I'll try mine with then to see if it's profitable Thanks in advance On my 270X 4Gb card best miner is Claymore 11.3, 2nd place SRBMiner, 3rd place - GGS. Each miner needs right parameters to recieve max speed. Thank you My 260X doesn't mine with Claymore in 10+ versions. So, I'll stick at SRB. Good to see it's the second fastest miner. I'll try some tweakings to old 260X. Let's see what we can reach |
|
|
|
I should also work on another command-line version...
Too much work, too little time!
supported  +1 +2 |
|
|
|
I want to mine luxcoin, but it's been incredibly hard figuring out how to do it. Been researching on youtube and reddit but there isn't any good info on either.
Can I just buy any "gaming" desktop that has a GPU in it or do I have to build a mining rig for it? I don't want to do that because that is a ton of work and I've never done it before.
The Lux's algorithm is Phi. It can be mined by GTX and RX cards, but it's easily mined by GTX cards. You can mine with a decent hashpower with GTX1070/1070ti or better. These cards performs good with @Enemy's miner. Sometimes I mine Lux and Folm in Awesomeminer. These coins is growing fast. Ok so you use a mining rig right? Not a computer. A mining rig still being a computer. My ComRIG is a common PC, with Ryzen 7, 16GB RAM and a GTX1070, but with some cables (risers) connected to another 4 GPUs (2xGTX1060, a RX580 8GB and a RX570 4GB). It's a "hybrid". |
|
|
|
my ASUS STRIX rx570 4gb cards, wouldn't go more than I=29, hashing at 500~600 H/s, no matter what clock and memory settings I put in AB. what can be the problem?
at the same time, some of my RX470 8gb nitro+ are hashing at I=50 and 850-950H/s on one rig, and I=41 and 750-800H/s on the other..
Contact Mattthev, he'll sort you out with some great memory straps to flash your GPUs with in case you haven't got decent ones. I assume you've set your intensity, worksize and amount ot threads properly? no, how can I reach him? here? well, for my STRIXs if I go more than I=29 rig crashes, plus if I leave it at I=0 for auto, it also makes it I=29. as for worksize and threads, optimal I guess is w=8, and T=2 so I keep it like this maybe try with 1 thread. W8 is ok, play with intensity. I believe the problem is definitely not in your miner, I've tried every other miner and still, those STRIXs are hashing better with SRB My Strix 570 4GB is performing around 980H/s at 1230/2020 in Cryptonight V7 and Cryptonight Classic. Intensity 54 and 2 threads. For Heavy I reached better results with only 1 thread and increasing intensity (around 57~59). Memory bottleneck is huge for Heavy algorithm. Around 770H/s with these settings. If you can't reach similar results with these settings, your problem probably is related to biosmod and/or driver and/or overclock. I'm not a genius like Mattthev, but I have good biosmods. Contact me if you want it. confirming 770 h/s with I=59, W=8, T=1. and AB at 1230/2000 plus underwolting -48. thanks a lot! but still far from good Great! In fact, its far from the 8GB cards, but its because the huge memory utilization by Heavy 'cause the threads have size doubled compared to V7. I think we can't improve it more. Is your BIOS modded? What are the stuff that's modded?
Heavy algo is limited on 4gb cards. I could only do 800 H/s on 4gb on Heavy while it does 1030 on cryptonight v7. Few of them are Elpidas and rest are Hynix AJR. The best that worked for me is I=59, W=8, T=1.
8gb cards should be able to do 1000-1100 on Heavy algo. At lastest versions, 1150H/s in my RX580 8GB at 1310/2010 (940mv ) Intensity 57, double threads and love <3 |
|
|
|
I want to mine luxcoin, but it's been incredibly hard figuring out how to do it. Been researching on youtube and reddit but there isn't any good info on either.
Can I just buy any "gaming" desktop that has a GPU in it or do I have to build a mining rig for it? I don't want to do that because that is a ton of work and I've never done it before.
The Lux's algorithm is Phi. It can be mined by GTX and RX cards, but it's easily mined by GTX cards. You can mine with a decent hashpower with GTX1070/1070ti or better. These cards performs good with @Enemy's miner. Sometimes I mine Lux and Folm in Awesomeminer. These coins is growing fast. |
|
|
|
my ASUS STRIX rx570 4gb cards, wouldn't go more than I=29, hashing at 500~600 H/s, no matter what clock and memory settings I put in AB. what can be the problem?
at the same time, some of my RX470 8gb nitro+ are hashing at I=50 and 850-950H/s on one rig, and I=41 and 750-800H/s on the other..
Contact Mattthev, he'll sort you out with some great memory straps to flash your GPUs with in case you haven't got decent ones. I assume you've set your intensity, worksize and amount ot threads properly? no, how can I reach him? here? well, for my STRIXs if I go more than I=29 rig crashes, plus if I leave it at I=0 for auto, it also makes it I=29. as for worksize and threads, optimal I guess is w=8, and T=2 so I keep it like this maybe try with 1 thread. W8 is ok, play with intensity. I believe the problem is definitely not in your miner, I've tried every other miner and still, those STRIXs are hashing better with SRB My Strix 570 4GB is performing around 980H/s at 1230/2020 in Cryptonight V7 and Cryptonight Classic. Intensity 54 and 2 threads. For Heavy I reached better results with only 1 thread and increasing intensity (around 57~59). Memory bottleneck is huge for Heavy algorithm. Around 770H/s with these settings. If you can't reach similar results with these settings, your problem probably is related to biosmod and/or driver and/or overclock. I'm not a genius like Mattthev, but I have good biosmods. Contact me if you want it. |
|
|
|
Not even, Unlike AMD, Nvidia's timings are really good already and are already using more bandwidth % than most AMD modded RX 400-500! I think i got something like +0.2~0.3 MH/s on a GTX 1070, it's really not impressive.
What about 1060 with Hynix? Can it be ETHlarged to be on par with other memory types on ethash? I think it have the same issue. Hynix in 1060 is bad, and maybe it only could be "saved" by a complete strap mod, not only RRD/FAW mod. |
|
|
|
|
Show Posts
