Ok maybe I should think smaller...i have started burst mining with 7x 8TB HDDs and my workstation was busy with plotting them for more than 16 days/24h (one time I had a blue screen after 36h ) Plotting the same TBs on SMR HDDs with my setup could be easy took more than 42 days! Thats to much time for me and my workstation CPU under 100% fire. CPU Plotting 1 SMR drive takes about 15days. So 7 drives can be plotted simultaneously 1 per thread on 1 PC. So it will take 15days for just plotting as it is. With some effort (and availability of faster drives) you can plot them faster.
|
|
|
The reality is that with very optimized plotting you can get it to read faster but it takes 47 seconds for my 8tb drive to be read which is less than the average block time
My current "big miner" runs on an AMD FX-8570, and currently has an 8TB Archive and a 8TB Compute (and a smaller drive) - the Compute reads about 5% faster than the Archive, and BOTH are under 40 seconds using Blago's miner if I'm not doing anything else on the machine. Anything under a minute is tolerable IMO, anything under 30 secs is very good - it's all about getting read before the next block pops up, and it's pretty rare for a block to take less than 30 secs and somewhat uncommon for it to take less than 1 minute. Thats fine, but what is it in numbers? If I get 45secs I get XXXBursts. And if i get under 23secs I get XXX Burst + 2%/10%/20%/..... ? With gpu miner (actually integrated Video) I get these: 2017-08-03 00:54:48.450 INFO 7140 --- [ roundPool-1] burstcoin.jminer.JMinerCommandLine : ------------------------------------------------------- 2017-08-03 00:54:48.485 INFO 7140 --- [ roundPool-1] burstcoin.jminer.JMinerCommandLine : START block '388488', scoopNumber '3283', capacity '31989 GB' 2017-08-03 00:54:48.508 INFO 7140 --- [ roundPool-1] burstcoin.jminer.JMinerCommandLine : targetDeadline '12096000', baseTarget '107259', genSig '9c94db..' 2017-08-03 00:54:48.693 INFO 7140 --- [ roundPool-1] burstcoin.jminer.JMinerCommandLine : dl '312187502' > '12096000' skipped 2017-08-03 00:54:48.693 INFO 7140 --- [ readerPool-41] burstcoin.jminer.JMinerCommandLine : 1% done (0TB 80GB), avg.'80 MB/s' 2017-08-03 00:54:48.742 INFO 7140 --- [ roundPool-1] burstcoin.jminer.JMinerCommandLine : dl '146094717' > '12096000' skipped 2017-08-03 00:54:48.927 INFO 7140 --- [ roundPool-1] burstcoin.jminer.JMinerCommandLine : dl '123372263' > '12096000' skipped 2017-08-03 00:54:49.005 INFO 7140 --- [ roundPool-1] burstcoin.jminer.JMinerCommandLine : dl '38522605' > '12096000' skipped 2017-08-03 00:54:50.176 INFO 7140 --- [ roundPool-1] burstcoin.jminer.JMinerCommandLine : dl '1404181' send (pool) [nonce '4012165637'] 2017-08-03 00:54:50.476 INFO 7140 --- [ readerPool-46] burstcoin.jminer.core.round.Round : dl '10526983' queued 2017-08-03 00:54:51.069 INFO 7140 --- [ readerPool-41] burstcoin.jminer.JMinerCommandLine : 12% done (3TB 623GB), avg.'337 MB/s', eff.'364 MB/s' 2017-08-03 00:54:51.578 INFO 7140 --- [skExecutor-1210] burstcoin.jminer.JMinerCommandLine : winner block '388487', 'BURST-RD7L-VYSA-MVGG-2GUPA' 2017-08-03 00:54:51.628 INFO 7140 --- [ readerPool-46] burstcoin.jminer.core.round.Round : dl '8881138' queued 2017-08-03 00:54:53.423 INFO 7140 --- [ readerPool-46] burstcoin.jminer.JMinerCommandLine : 23% done (7TB 167GB), avg.'351 MB/s', eff.'367 MB/s' 2017-08-03 00:54:54.472 INFO 7140 --- [ readerPool-41] burstcoin.jminer.core.round.Round : dl '3358695' queued 2017-08-03 00:54:54.975 INFO 7140 --- [skExecutor-1211] burstcoin.jminer.JMinerCommandLine : dl '1404181' confirmed! [ 16d 6h 3m 1s ] 2017-08-03 00:54:55.824 INFO 7140 --- [ readerPool-41] burstcoin.jminer.JMinerCommandLine : 34% done (10TB 710GB), avg.'354 MB/s', eff.'360 MB/s' 2017-08-03 00:54:58.151 INFO 7140 --- [ readerPool-46] burstcoin.jminer.JMinerCommandLine : 45% done (14TB 253GB), avg.'358 MB/s', eff.'371 MB/s' 2017-08-03 00:55:00.598 INFO 7140 --- [ readerPool-44] burstcoin.jminer.JMinerCommandLine : 56% done (17TB 797GB), avg.'357 MB/s', eff.'353 MB/s' 2017-08-03 00:55:02.930 INFO 7140 --- [ readerPool-41] burstcoin.jminer.JMinerCommandLine : 67% done (21TB 340GB), avg.'359 MB/s', eff.'370 MB/s' 2017-08-03 00:55:05.756 INFO 7140 --- [ readerPool-41] burstcoin.jminer.JMinerCommandLine : 78% done (24TB 931GB), avg.'351 MB/s', eff.'310 MB/s' 2017-08-03 00:55:08.243 INFO 7140 --- [ readerPool-45] burstcoin.jminer.JMinerCommandLine : 90% done (28TB 475GB), avg.'351 MB/s', eff.'347 MB/s' 2017-08-03 00:55:09.398 INFO 7140 --- [ readerPool-41] burstcoin.jminer.JMinerCommandLine : read 'G:/Burst/plots' (7TB 994GB) in '20s 948ms' 2017-08-03 00:55:11.025 INFO 7140 --- [ readerPool-44] burstcoin.jminer.JMinerCommandLine : read 'D:/Burst/plots' (7TB 998GB) in '22s 574ms' 2017-08-03 00:55:11.487 INFO 7140 --- [ readerPool-45] burstcoin.jminer.JMinerCommandLine : read 'F:/Burst/plots' (7TB 998GB) in '23s 36ms' 2017-08-03 00:55:11.750 INFO 7140 --- [ readerPool-46] burstcoin.jminer.JMinerCommandLine : 100% done (31TB 989GB), avg.'335 MB/s', eff.'244 MB/s' 2017-08-03 00:55:11.750 INFO 7140 --- [ readerPool-46] burstcoin.jminer.JMinerCommandLine : read 'E:/Burst/plots' (7TB 998GB) in '23s 299ms' 2017-08-03 00:55:12.001 INFO 7140 --- [ roundPool-1] burstcoin.jminer.JMinerCommandLine : FINISH block '388488', best deadline '1404181', round time '23s 301ms'
The problem is that I don't see any difference in earnings between CPU miner, which runs only 160MB/s. The earnings fluctuates each day by 2 ... 5 ... 10 times.
|
|
|
Total waste of money to buy the faster stuff JUST BECAUSE IT PLOTS FASTER. Total waste of money to spend day by day with plotting HDDs instead of mining and earn money with faster stuff! 1) Slow plotting can be avoided 2) How much you will mine for that difference in days? 1$ or 2? I think less then 1$.
|
|
|
Haven't seen any sources except original xevan-ccminer, but it has only cpu-hashing implemented, so writing from scratch basing on algo-description and existing opencl kernel. Anyway, there'll be a choice for BitSend miners. Haven't heard about lyra2z330, should look at it. But AMD miners will drown us all one day, will it be leaving ETH for other coins because of hashrate drop, or will it be leaving ETH after PoS, it will definetely be doom-day for all mining community for a long time, I suppose. Anyway low speeds of reds on Signatum defended us from them here. With them everything would be much worse. Lyra2z330 Zoin coin algo. Used to be CPU mining with 300-400Khash per pool till 3-4 days ago. Now top miner makes 1.2Mhash. 10 i5 CPU make 7-8Khash. So you can count.
|
|
|
Hey friend. Burst is in a funk right now. It actually really easy to get started. There is no hashrate in burst. When you plot for example 50tb its linked to your account. The miners simply read that data and look for a deadline which can win the next block. Now. As for speed 40mb/s is fine. The reality is that with very optimized plotting you can get it to read faster but it takes 47 seconds for my 8tb drive to be read which is less than the average block time. Having faster reads is better but not a deciding factor for if you will win a block or not. Im currently mining with 20tb and make 30-40 burst a day give or take. All depends. If you do manage to find a block you will earn much much more.The miner will usually just display what point in the drive its reading at. The entire network underwent a ddos not to long ago and is still recovering. Many of the sites are still down and many of the pools. Im currently mining on pool.burstmining.club and it has been working well for the last few days. Good luck.
Thank you. But you are just repeating what others say. I ploted with cpu plotter and as i understand the are optimized already. But what about numbers? What about influence of MB/s? What about "find block - get much much more" - what is it exacly. Wow much? What is the chance, what does it depends on? I mean in exact numbers, not the "the more TB -the better". Why 40 on one PC and 60 on another. Why 40 with one drive and 160 with 4 drives(40 per drive) with 2core CPU? Why no difference? But more than that - what is the exact influence of speed in numbers? I mean if 50Mb/s = XX Burst than 100Mb/s = XX Burst + 2% (20% .... 100%)? What is the best hardware to mine Burst, bros?
I would recommend to buy 8TB HDDs like the Seagate Iron Wolf PMR-HDD and not any slow HDD like Seagte Archiv wich is a SMR-HDDFor example with my I7 Xeon CPU I plott a single 8TB PMR-HDD within 48h. I tried the same with a SMR Archive HDD and it was 3 times slower! It doesn't make sence. Price is much different and speed difference is only when plotting. But you can avoid it. I wrote a bat file which plotted on SSD, then moved plot to SMR in cycle. It's nothing complex in that. Anyway - the time to plot is miserable compared to ROI - so the cheapest drive wins the game.
|
|
|
Xevan is algo used as PoW by BitSend coin, as I know there's no publically avaliable CUDA miner for this one and decided to give it a try, original dev gave up on this, so CPU/OpenCL only for this time.
I think 1070 should make 5Mhash with Xevan. Have you found souces for it - i saw only X17 on oficial page and no xevan realisation for ccminer despite what the the name says "xevan-ccminer" )) P.S. Убьешь монету ))) И красных обездолишь - им с эфира бежать больше некуда. P.P.S. Have you seen lyra2z330 (lyra2zoin) gpu miner. Definitely someone made it for gpu but can't find.
|
|
|
What is the best hardware to mine Burst, bros?
I don't know if anobody knows for sure. Everything that can be found is about faster plotting and not about optimal mining. What about MB/s? I get 42Mb per drive on one PC. And 60Mb on another with the same drives. Their reading speed is 100+ (8Tb Seagate Archive) So why i don't get this speed - i don't know. Do I need it to be as fast as possible or i can't influence that and it actually has mediocre effect? E.g. 100TB 10Mb/s = 50TB 100MB/s. Is it so or not there is no such info. I wasn't able to find any info about that. The only thing is "more TB - better" and "1 core per HDD". That's all. For what GPU is needed in mining when CPU load is 70% maximum, i don't know. 1 drive or 4 drives on 2core CPU - no change in speed per drive - 42Mb. Why? Why there is "minimal TB" for some pools and no minimum for others? With other altcoin mining it doesn't matter - you will get according to your hashrate and luck of the pool (however on a long run luck equalises). With Burst it isn't so - why? Miner doesn't show any statistics like hashrate or something else clear. Only some info that doesn't make any sence. (while i understand the idea of deadlines itself, but the info doesn't make sence with how fast you are, how much coins you mine) On pools there is some info which I don't know how to interpret. Actually the interface of pools is hard to understand: no hashrates, no mBTC/TB/Day, no graphs, no miners info. With normal mining - you change miner/overclock and see the result almost immideately, you can see what miners are most used, but not with Burst. There is some correlation with the size but it is not evident. For example 50TB can get less than 5Tb. The calculator gives 3 times more numbers than you really get. The sites/pools are down most of the time. Main site is always down. I was able to access online wallet from app maybe 2 times. Local wallet never sync - it just hangs doing nothing at different percent synced and thats all Only Clean DB restarts it from scratch ... till some percent. I can only access wallet from burstation site. There is no clear guide/howto explaining all that things that are much different from what we got used to with normal altcoin mining. So many questions and no answers. IMHO burst team do nothing to popularize the Burst. Seems to me that they only struggle with ddosing and blockchain hacking. If the wallet doesn't sync - why not to simply download biggest part and sync the rest? Or at least add a link to the blockchain file in the wallet so the user doesn't need to search google and download it from some unknown source? It's simple, it can help network (as said above), but it is not done. Why? What is easier that to publish FAQ about all the questions I have in post. I'm sure every Burst miner ask them.
|
|
|
How can I get the miner to try?
|
|
|
Lis lies from the beginning. It is Only Asics coin, it has Extremely Huge Premine = Shit coin.
Have LTC And BTC is also a huge Premine = Shit coin but something about them so you won't say it's true And of course don't you tell me about the ETH Although ETH real Shit coin !!! Bla bla bla. I don't remember devs of BTC or LTC claimed asics resistance while asics ALREADY exist and are in game from the beginning. If ther dev LIES from the beginning, then hope that wallet is not jist a virus.
|
|
|
Lis lies from the beginning. It is Only Asics coin, it has Extremely Huge Premine = Shit coin.
|
|
|
432 confirms? 14 hours? Will change it, was testing Hello. I mined all night and have 4 times coins than payout threshold. Still no payment . Why? The same time I mine on bitcrush and already receiving payments. P.S. On the main page you write Pool Fees 0.5% But take 2%. Not good.
|
|
|
I used to use EWBF miner and got 320 SOL on each of my 1060 instead of getting 285 SOL using excavator, but I had a massive issues in stability in it and it crashes frequently even in stock settings, so I switched to excavator, low SOLs but running stable now for more than three days which has never happened with EWBF..
As far as EWBF restart is almost instant (no DAG generation). Then it is no problem just to kill process once in every XX minute. 330-340Sols instead of 290 is 10-15% extra.
|
|
|
Is it possible to mine on the pool? Somebody is mining on suprnova(at least there is some hashrate), but I get errors after several successful shares: Stratum connection interrupted Stratum connection failed: Failed to connect to xcn.suprnova.cc port 8008: Connection refused
|
|
|
Is there anybody from https://zoi.acc-pool.pwMy account became locked, but I can't get the recovery email. When i try password recovery i get an error: "Unable to setup token for password reset" How can I unlock the account and change the password?
|
|
|
- Dcri settings – during optimization/benchmarking different dcri values are being tested automatically (0, 30, 70 and 100) to make sure profit is maximized.
0 30 70 100 is not enough. These works for 1060/1070, usually somewhere around 35-50-60. But for 1080/1080ti 200+ ... 400+ is more profitable nowadays (LBRY usually ~480-500 on 1080Ti) And as for AMD cards and GTX1060 dcri should be changed very presicely. E.g. right now on 1xFuri Eth+DCR dcri30=2.40 dcri36 =2.69$, dcri40 = 2.59 dcri50=2.30 First to implement realtime optimizing of dcri setting will get many users. Thank you very much for the feedback and pointers. (1) LBRY – currently not supported. We have added to the wish list though (2) More dcri values - will add more values to the optimization. Naturally, the more values we add the lengthier the benchmarking process will be. This is especially true due to dag size (e.g. optimization for ETH +DCR is not the same as optimization for UBQ+DCR). (3) Real time dcri optimization – we currently do that for a limited number of values. Including all possible values would make bencmarking run forever... . Nevertheless, point taken, we will think of a creative way to address this. Thanks again! 1. Sia. Pascal, kessak, nist5 etc also should be added to maximize profit. Without them you won't beat modded versions of NHM. 2. Benchmark can be done in one attempt if you would be able to change dcri in real time. Anyway manual input for some algo is ok. 3. I think that with dual mining 3 settings are just the points to start closer to the optimum. After start real time optimizing should take place.
|
|
|
- Dcri settings – during optimization/benchmarking different dcri values are being tested automatically (0, 30, 70 and 100) to make sure profit is maximized.
0 30 70 100 is not enough. These works for 1060/1070, usually somewhere around 35-50-60. But for 1080/1080ti 200+ ... 400+ is more profitable nowadays (LBRY usually ~480-500 on 1080Ti) And as for AMD cards and GTX1060 dcri should be changed very presicely. E.g. right now on 1xFuri Eth+DCR dcri30=2.40 dcri36 =2.69$, dcri40 = 2.59 dcri50=2.30 First to implement realtime optimizing of dcri setting will get many users.
|
|
|
Receiving this errors in log: 11.07.2017 10:01:29.725 INFO >>>>> LOG START >>>>> 11.07.2017 10:01:29.756 SharedMemory INFO Creating shared memory file 11.07.2017 10:01:29.911 SharedMemory ERROR Error while creating memory file: Некоторые или ссылки на свойства нельзя преобразовать. 11.07.2017 10:01:30.929 SharedMemory ERROR Trying to access non-existing map file 11.07.2017 10:01:31.915 SharedMemory ERROR Trying to access non-existing map file 11.07.2017 10:01:32.915 SharedMemory ERROR Trying to access non-existing map file
|
|
|
You need to add more miners and newer ones. Dual Claymore 9.7 is faster on 1060/1070 than 9.5 that is downloaded Xmr-stack-cpu is faster than Claymore. With Dual Claymore the one of the most important things to add is -dcri setting - 1080/1080ti are much more profitable with high values. The best would be automatic changing in realtime to get maximum profit. Or at least 3-5 user entered values from which app will choose the most profitable at the moment.
|
|
|
|