burstcoin-jminer v0.4.10 - GPU assisted PoC-Miner (All Platforms)
-
@luxe hey man... What is wrong with my setup? I underlined the lines with errors... I know it is mining and reading faster than my CPU but I can't see information regarding the Best DL or Last Winner, i tried to use the following addresses as walletServer:
- https://wallet.burst-team.us:8125
- https://wallet.burst-team.us:8125/
- http://wallet.burst-team.us:8125
- http://wallet.burst-team.us:8125/
- https://wallet.burst-team.us:8128
- https://79.168.208.213:8125
With all of them I always got this outcome... I should be doing something wrong, or this functions are not working properly @luxe ?
Here is my proprieties file:
# ----------------------------------------------------------------------------------- # - BURSTCOIN JMINER --------- THIS IS EXPERIMENTAL SOFTWARE, USE ON YOUR OWN RISK! - # ----------------------------------------------------------------------------------- # jminer is a PoC (Proof of Capacity) miner with GPU support for Burstcoin (BURST) # (openCL will also work with CPU in needed) # # Requirements: # - Java8 (64bit recommend to use more memory) # - openCL # # PLEASE DONATE # # jminer would not be possible without openCL kernels and java code provided by 'burstDev', # he really deserves some tips for that! # BURST-QHCJ-9HB5-PTGC-5Q8J9 # # Feel free to support future development of mining engine ... # BURST-LUXE-RED2-G6JW-H4HG5 # ----------------------------------------------------------------------------------- # ----------------------------------------------------------------------------------- # NOTICE: your 'jminer.properties' hasn't got to contain all properties listed here # as long there is a default/fallback defined, mentioned in here. # ----------------------------------------------------------------------------------- # ----------------------------------------------------------------------------------- # - PLOT-FILES ---------------------------------------------------------------------- # ----------------------------------------------------------------------------------- # plotPaths - list of plot paths separated with , e.g. D:/,C:/,E:/plots,F:/plots (in one line) # (required) the miner will treat every path as 'physical' drive and use one thread for it # # scanPathsEveryRound - optional 'true' will check 'plotPaths' for changed plot files on every round # (default:true) 'false' will check only on start/restart # # listPlotFiles - optional ... list all plotFiles on start, If walletServer/soloServer is configured, # (default:false) it will show mined blocks and drive seeks/chunks of plotfile, too. # ----------------------------------------------------------------------------------- plotPaths=D:/plots/DONE,E:/plots/DONE scanPathsEveryRound=true listPlotFiles=true # ----------------------------------------------------------------------------------- # - MINING MODE --------------------------------------------------------------------- # ----------------------------------------------------------------------------------- # poolMining - 'true' for pool mining, 'false' for solo mining. # (default:true) ensure to configure the chosen mining-mode below. # ----------------------------------------------------------------------------------- poolMining=true # ----------------------------------------------------------------------------------- # - MINING MODE - POOL ---------------------------------- ONLY NEEDED 4 POOL MINING - # ----------------------------------------------------------------------------------- # NOTICE: # ensure you already setup reward assignment # http://localhost:8125/rewardassignment.html # # numericAccountId - first number in all plot-files # (required for pool) # # poolServer - format is inclusive protocol and port e.g. 'http://pool.com:8125' # (required for pool) # # walletServer - define local or online wallet, to receive and show last winner! # (optional) if empty, winner feature will be just disabled. # format is inclusive protocol and port e.g. 'http://localhost:8125' # online use e.g. 'https://wallet.burst-team.us:8125' # # winnerRetriesOnAsync - number of retries to get winner from walletServer # (default:4) # winnerRetryIntervalInMs - time to wait until next retry to get winner from walletServer # (default:500) # ----------------------------------------------------------------------------------- numericAccountId=9732741443391337776 poolServer=http://pool.ccminer.net:8080 # Winner walletServer=https://79.168.208.213:8125 winnerRetriesOnAsync=10000 winnerRetryIntervalInMs=500 # ----------------------------------------------------------------------------------- # - MINING MODE - SOLO ---------------------------------- ONLY NEEDED 4 SOLO MINING - # ----------------------------------------------------------------------------------- # soloServer - WARN! soloServer should be http://localhost:8125 or http://127.0.0.1:8125 # (default: Solo means you send your PASS on commit results! # http://localhost:8125) DO NOT try to use a online wallet or pool as Server! # # passPhrase - secretPhrase/password of solo mining burst-account # (required for solo) # # targetDeadline - min. deadline to be committed. e.g. 750000 # (optinal) # # triggerServer - emulates open wallet, to prevent it from # (default: false) falling asleep (not sure if needed at all) # # recommitDeadlines - recommits deadlines below 1200 3 times in a interval of 5 sec. # (default: false) experimental feature to increase chance that deadline gets propagated # e.g. on short disconnect or connected peers busy etc. # ----------------------------------------------------------------------------------- soloServer=http://localhost:8125 passPhrase=xxxxxxxxxxxxxx targetDeadline= triggerServer= recommitDeadlines= # ----------------------------------------------------------------------------------- # - OpenCL ----------------------------------------------------------------------------- # ----------------------------------------------------------------------------------- # The miner uses openCL for most of the mining calculations, ensure it is setup correctly. # Instructions can be found e.g. here (thanks cryo): # https://github.com/bhamon/gpuPlotGenerator/blob/master/README.md # You could also use that instruction to find your platformId and deviceId if needed. # # platformId - id of openCL platform on your system. one platform may have multiple # (default:0) devices, the miner currently uses just one (in general not the bottleneck) # # deviceId - specifies the device used by OCLCecker, can be your first GPU, # (default:0) in most cases it will not be 100% used. (depends on capacity) # ----------------------------------------------------------------------------------- platformId= deviceId= # ----------------------------------------------------------------------------------- # - MINING ENGINE ------------------------------------------------------------------- # ----------------------------------------------------------------------------------- # refreshInterval - interval of asking wallet/pool for mining info (in ms), # (default:2000) to check for new block # # connectionTimeout - increase the 'connectionTimeout' on network problems. # (default:12000) this timeout is used for all network requests. # if you use pool or online-wallet, the 12 sec. default may # cause timeout on committing nonces or getting mining info etc. # # debug - setting 'debug' to true will log additional information of the mining process, # (default:false) that are not related to mining, but to miner internals. # # writeLogFile - setting 'writeLogFile' to 'true' will write all logs from console to a file, too. # (default:false) the name of that file can be specified by 'logFilePath'. # # logFilePath - path (filename and optional directory, relative to miner location) # (default:log/jminer.log.txt) # ----------------------------------------------------------------------------------- refreshInterval=1000 connectionTimeout=60000 debug=true writeLogFile=true logFilePath=C:\Users\Goncalo\Desktop\BURST\software\jminer # ----------------------------------------------------------------------------------- # - MINING ENGINE - APPEARANCE / BEHAVIOR ------------------------------------------- # ----------------------------------------------------------------------------------- # readProgressPerRound - defines how often the mining progress is shown per round # (default:9) thats the 'xx% done ...' info. # # byteUnitDecimal - switch between decimal units (true): TB/GB/MB (divided by 1000), # (default:true) or binary units (false) TiB/GiB/MiB (divided by 1024) - https://en.wikipedia.org/wiki/Byte # # showDriveInfo - set this to 'true' to show info about every drive on finish reading it, # (default:false) this is useful to find the slow ones ... can help to optimize your setup. # # showSkippedDeadlines - set this to 'true' to show found deadlines below targetDeadline from # (default:true) this config or provided by pool (overwriting the targetDeadline specified in here) # ----------------------------------------------------------------------------------- readProgressPerRound=5 byteUnitDecimal= showDriveInfo=true showSkippedDeadlines=true # ----------------------------------------------------------------------------------- # - MINING ENGINE - MEMORY USAGE ---------------------------------------------------- # ----------------------------------------------------------------------------------- # chunkPartNonces - staggerSize defines number of nonces per chunk. # (default:320000) the miner will split chunks in smaller pieces called chunkParts. # this makes sense, to save memory and optimize speed. # in the best case chunkPart#1 will be checked before chunkPart#2 is # completely read ... depending on the power of your GPU. # if staggersize is smaller than chunkPartNonces, staggersize will be used. # e.g. play with +/- 160000 steps # # readerThreads - normally '0' means, the miner takes one thread per drive (plotPath) this is recommend. # (default:0) choosing a other number of 'readerThreads' can be useful on memory issues. # For example, if you mine on 4 drives (plotPaths), you can reduce the memory usage # by setting 'readerThreads=2', this will reduce mining speed but save memory. # ----------------------------------------------------------------------------------- chunkPartNonces= readerThreads=
-
if you got local wallet running try pointing to it (http://localhost:1825)
-
@LithStud Yeah I have not a local one in this machine... ;D
I may install it tho. But it is saying that the burst-team wallet is out of sync when in fact it isn't lol
-
@gpedro the IP one didnt work for me at all so no wonder there. Not sure why others doesnt work tho (thus recommendation to try local and see what happens :D )
-
I'm running a AMD r9 280x with 16.11.5 and AMD SDK 3.0
I tried 0.4.9 and 0.4.10 - without any luck - my Card never gets detected at the first plattform overwiew. What is wrong here? Any suggestions?
Windows 10 x64
i7 4770
r9 280x
-
@gpedro you can leave 'walletServer=' empty (disable infos) or try 'walletServer=http://burstcoin.cc:8889'
not sure, but https may be a issue choose wallet without if thats the case ... at burstcoin.cc you will find some.
-
@Zaziki If you know platform and device just specify it manualy ...
e.g.platformId=2 deviceId=1The platform overview is just a info and maybe not detects exotic setups?! not sure ...
May also be a driver issue. Have you checked opencl-z if it shows up there?
-
@luxe that worked hehehe
thanks bro!
-
@gpedro Well guess i have to check why https does not work ... i expected miners to use localhost :-) Never tested something else ...
-
@luxe yeah I thought so but I still didn't got the local wallet running on this PC hehe
-
got it Running, but for now pretty slow.
I have about 92TB, Read times ~2min 34s
With Blago i need about 52s in i7 4770.there must be sth wrong.
All my plots are optimized and One File per Drive.
I Read that r9 280x only Support opencl 1.2, is there maybe the Problem?
-
i tried to solo mine but even though its set up properly, local wallet up to date, I see blocks won by others but my disks aren't being read so its not mining. In actual fact, the disks have gone to sleep lol. Any suggestions? is there some sort of limitation such as passphrase length?
-
@Zaziki 280x is fine ... are you sure you use it? Please provide more details like screen of miner and/or your config.
@ZapbuzZ The miner will start mining as soon the connected wallet receives a new block ... if you provide your config i can take a look on it (without passphrase ... that is not limited as far as i know).
-
ok ty @luxe thanks for information. i decided to go to a pool for now. If I decide to mine solo mode again i will post the config.
-
@Luxe, note that in the config file the target deadline is listed in the solo section of the code, as if it's not applicable to pool mining. There are some pools, specifically the Lex code that does not override this value so it will apply when pool mining on Lex code pools. If someone sets up a short Target DL like 14400 for solo mining and forgets about it and swaps over to a lex code pool they will loose many DL submissions as skipped.
On your next revision, you may want to consider moving it into a more general section of the file. Just a thought.
-
@luxe Sorry for my late answer.
After finishing plotting, times got better - but still i think that 1400MB/s are not that fast. I read that u do 3500 with the same GPU.
Here Some Screens (startupInfo, plotted Files, oneBlock)
Some Info:
I have 6 Drives at the Mainboard internal SATA Controller (SATA6G).
Another 3 Drives are at a Adaptec 6805E Controller
all other Drives are connected via USB 3.0
-
@Zaziki i have more drives/controllers than you, due to parallel reading i reach higher MB/s (~30 sec round time is fine) ... your setup so far looks very good. Btw. you can mount drives to directories, you do not need to assign a-z drive letters ... https://technet.microsoft.com/en-us/library/cc753321(v=ws.11).aspx#BKMK_WINUI
-
@luxe thanks mate
-
My setup:
- 19x 8 TB disks: 8x SATA mainboard, 3x SATA PCIe Controller, 8x USB 3.0 (PCIe controller with 4 USB 3.0 controller chips, 2 disks each port/controller)
- AMD A8-7670K APU with R7 cores used for jminer
- burstcoin-jminer v0.4.10 with Win10 x64
What's going wrong / questions:
- All 11 internal SATA disks are read out first and when they finished their work, all USB 3.0 are read out. Is this kind of prioritization a bug or a feature? I believe I loose a lot of time because of that.
- What does the "GB" number mean. All internal SATA disks show "0GB" and all USB 3.0 disks "1GB".
- Is it somehow possible to show the "100% done...". message only? Just a cosmetic issue. :-)
- What does the "avg." and "eff." value mean exactly? First one is "average" but what's the second one?
Thanks!
-
@eneloop 1. I would guess that the R7 does not have enough threads to spawn one for each of your drives, so it has to recycle the threads after they're done reading the first dozen or so drives. You'll probably need a discreet GPU to turn those 70 second read times into 35 second ones.
- The GB number is just size. Some of your 8TB drives seem to be a bit larger than 8TB. Lucky you.
- Modify the source code and recompile and you can make it say whatever you like. :)
- Dunno this one.






