Jminer Setup
-
I tried 0.4.2-RELEASE and the result is the same error!
-
@BurstmanJens Thanks for info.
I would like to find out, if your OpenCl config is the problem, or if it is a jminer bug/issue.
Please follow https://github.com/bhamon/gpuPlotGenerator#list-platforms steps and find out your platform and device ... if that tool does not work, too. It is not a jminer issue.
-
@luxe
I installed the AMD-SDK again and this time it worked!
Now jminer starts but what does "dl '529414232' > '172800' skipped" mean?
-
The pool provides a min. deadline that is allowed to commit, called 'targetDeadline'. The miner will skip all deadlines below.
You can see targetDeadlines overview here: http://util.burst-team.us:8888/
-
@luxe
So, do I need to change anything to correct it?
-
No, it is correct like it is.
-
@luxe
It looks like this...2016-08-16 23:15:23.615 INFO 5092 --- [ roundPool-1] burstcoin.jminer.JMinerCommandLine : -------------------------------------------------------
2016-08-16 23:15:23.621 INFO 5092 --- [ roundPool-1] burstcoin.jminer.JMinerCommandLine : START block '263184', scoopNumber '1392', capacity '10984 GB'
2016-08-16 23:15:23.625 INFO 5092 --- [ roundPool-1] burstcoin.jminer.JMinerCommandLine : targetDeadline '172800', baseTarget '1174644'
2016-08-16 23:15:23.636 INFO 5092 --- [ roundPool-1] burstcoin.jminer.JMinerCommandLine : dl '529414232' > '172800' skipped
2016-08-16 23:15:23.692 INFO 5092 --- [ readerPool-12] burstcoin.jminer.JMinerCommandLine : 1% done (0TB 1GB), avg.'19 MB/s'
2016-08-16 23:15:23.705 INFO 5092 --- [ roundPool-1] burstcoin.jminer.JMinerCommandLine : dl '203480136' > '172800' skipped
2016-08-16 23:15:23.903 INFO 5092 --- [ roundPool-1] burstcoin.jminer.JMinerCommandLine : dl '108632406' > '172800' skipped
2016-08-16 23:15:24.119 INFO 5092 --- [ roundPool-1] burstcoin.jminer.JMinerCommandLine : dl '78444985' > '172800' skipped
2016-08-16 23:15:24.149 INFO 5092 --- [ roundPool-1] burstcoin.jminer.JMinerCommandLine : dl '57738458' > '172800' skipped
2016-08-16 23:15:24.154 INFO 5092 --- [ roundPool-1] burstcoin.jminer.JMinerCommandLine : dl '45909961' > '172800' skipped
2016-08-16 23:15:24.349 INFO 5092 --- [ roundPool-1] burstcoin.jminer.JMinerCommandLine : dl '37359802' > '172800' skipped
2016-08-16 23:15:24.984 INFO 5092 --- [ roundPool-1] burstcoin.jminer.JMinerCommandLine : dl '32848299' > '172800' skipped
2016-08-16 23:15:25.457 INFO 5092 --- [ roundPool-1] burstcoin.jminer.JMinerCommandLine : dl '28532590' > '172800' skipped
2016-08-16 23:15:25.664 INFO 5092 --- [ roundPool-1] burstcoin.jminer.JMinerCommandLine : dl '6979077' > '172800' skipped
2016-08-16 23:15:27.006 INFO 5092 --- [ readerPool-15] burstcoin.jminer.JMinerCommandLine : 12% done (1TB 221GB), avg.'87 MB/s', eff.'88 MB/s'
2016-08-16 23:15:27.852 INFO 5092 --- [ roundPool-1] burstcoin.jminer.JMinerCommandLine : dl '4892991' > '172800' skipped
2016-08-16 23:15:30.406 INFO 5092 --- [ readerPool-13] burstcoin.jminer.JMinerCommandLine : 23% done (2TB 442GB), avg.'88 MB/s', eff.'89 MB/s'
2016-08-16 23:15:32.587 INFO 5092 --- [ roundPool-1] burstcoin.jminer.JMinerCommandLine : dl '4207413' > '172800' skipped
2016-08-16 23:15:33.727 INFO 5092 --- [ readerPool-14] burstcoin.jminer.JMinerCommandLine : 34% done (3TB 662GB), avg.'88 MB/s', eff.'89 MB/s'
2016-08-16 23:15:36.293 INFO 5092 --- [ roundPool-1] burstcoin.jminer.JMinerCommandLine : dl '2280807' > '172800' skipped
2016-08-16 23:15:37.084 INFO 5092 --- [ readerPool-15] burstcoin.jminer.JMinerCommandLine : 45% done (4TB 883GB), avg.'88 MB/s', eff.'88 MB/s'
2016-08-16 23:15:40.523 INFO 5092 --- [ readerPool-13] burstcoin.jminer.JMinerCommandLine : 56% done (6TB 102GB), avg.'88 MB/s', eff.'86 MB/s'
2016-08-16 23:15:41.260 INFO 5092 --- [ roundPool-1] burstcoin.jminer.JMinerCommandLine : dl '540313' > '172800' skipped
2016-08-16 23:15:43.215 INFO 5092 --- [ roundPool-1] burstcoin.jminer.JMinerCommandLine : dl '485307' > '172800' skipped
2016-08-16 23:15:43.915 INFO 5092 --- [ readerPool-15] burstcoin.jminer.JMinerCommandLine : 67% done (7TB 323GB), avg.'88 MB/s', eff.'87 MB/s'
2016-08-16 23:15:47.359 INFO 5092 --- [ readerPool-7] burstcoin.jminer.JMinerCommandLine : 78% done (8TB 544GB), avg.'88 MB/s', eff.'86 MB/s'
2016-08-16 23:15:51.002 INFO 5092 --- [ readerPool-14] burstcoin.jminer.JMinerCommandLine : 89% done (9TB 765GB), avg.'87 MB/s', eff.'80 MB/s'
2016-08-16 23:15:56.414 INFO 5092 --- [ readerPool-15] burstcoin.jminer.JMinerCommandLine : 100% done (10TB 984GB), avg.'81 MB/s', eff.'55 MB/s'
2016-08-16 23:15:56.615 INFO 5092 --- [ roundPool-1] burstcoin.jminer.JMinerCommandLine : FINISH block '263184', best deadline 'N/A', round time '32s 754ms'...all where skipped!
-
Yes, you did not find one that is good enough (below 172800)... there are pools with higher targetDeadlines, all you can do is switch. But i suggest you just keep it like it is, was just bad luck this round ...
-
@luxe
It's working now ! Thank's for all your help!
-
Whats the optimal setup for:
chunkPartNonces=
readerThreads=How do you decide? 1 or more readerThreads per drive?
Is the default value of chunkPartNonces=320000 optimal?
I have an AMD RX480 and 6 drives at the moment!
-
Please check:
https://github.com/de-luxe/burstcoin-jminer/wiki/configure-jminer.properties#miner-memory-usage
If you have enough memory 'readerThreads=0' and increase chunkPartNonces ... chunkPartNonces higher than staggersize has no effect.If you still have questions, feel free to ask.
Nice, 6 drives and how much capacity? How about post a screen of jminer running, maybe i find something to improve.
-
@luxe
Yes, I read that page! But i still wonder if default(320000) or 960000 is better? It says depending on how strong the GPU is!
How do you calculate the number optimal for your system? Or do you have to try different amounts?The drives are not that large 1-2TB each but 60 to 80 MB/s seems slow!
-
@BurstmanJens
Do you use optimized plotfiles? How high is your staggersize?
(if you do now know what i mean, add 'listPlotFiles=true' and make a screen)
How about just try if 960000 is better for you :-)
Also try add 'showDriveInfo=true' to get more detailed info, how every drive performs.
-
@luxe
Is restarting Jminer while plotting a drive wise?
Do you have to restart Jminer to take the new properies?
-
@BurstmanJens No need to hurry ... may work, but i would let it run.
Yes changes only take effect after restart.
-
@luxe
Ok. I'll try the changes you suggested after the new drive is plotted!
-
@luxe
It seems too have little or no effect when I change chunkPartNonces to 960000 instead of 320000!
How do you optimize plotfiles?
-
http://forums.burst-team.us:4567/topic/26/plot-optimizer-v1-6-with-gui-1-0-3-j6jq-win/2
http://forums.burst-team.us:4567/topic/25/plot-optimizer-v1-6-win
-
I went through those problems but now I have one that I am sure is easy to fix. I learned via youtube over many hours how to use jminer for my burst, now i am getting what I assume is the not confirmed message. I would not get it using Blago except maybe once a day. Here is a screenshot, do I need to make a small change? Thanks in advance!

-
@Rorepme Increase connectionTimeout in jminer.properties, in most cases the pool received your nonce, but was just not able to answer in time.
