GPU Reading Speed Falling from 1200+ Mb to 303 Mb using the jminer-0.4.11.



  • GPU Reading Speed Falling from 1200+ Mb to 303 Mb using the jminer-0.4.11. Any one having this issue before and how it can be solved?



  • @SKANDI ,

    Short answer, disconnect half of your drives :), I would guess you have at least 80TB. What happens is the first scanned drives report high read speeds, but the ones in the back drag the average down. I get the same thing 1400+ at the beginning ends up around 300 at the end of scan. I am using 4.10.



  • Am having 35 TB for now, i was planning to upgrade to 150 TB. i bought 4 Drives 8TB seagate as a test.
    Am using GTX 1080ti 11GB OC for plotting. and unfrtounatly am getting the error "unable to get minning info from the wallet" and am not being able to solve this issue aswell. :( am not sure if burstcoin mining is worth it.



  • @SKANDI , post you config here, remove any passphrases if they are in the file.

    You mean 35TB not GB no??



  • Once i start the Jminer it scans the HDD and it detects a Deadline. But after the pool send the second block am receiving the error and the miner not able to scan the HDD. i tried to set the connectionTimeout=70000 but still not working. tried to change the walletServer=Burstcoin (burstcoin which is the PC name) but still not working.

    Find the Config Below:
    plotPaths=G:/Burst/plots,F:/Burst/plots,E:/Burst/plots,D:/Burst/plots,
    poolMining=true
    numericAccountId=15897797494081209988
    poolServer=http://poolofd32th.club:8124
    walletServer=http://localhost:8125
    winnerRetriesOnAsync=
    winnerRetryIntervalInMs=
    devPool=false
    devPoolCommitsPerRound=
    soloServer=http://localhost:8125
    passPhrase=xxxxxxxxxxxxxx
    targetDeadline=
    platformId=0
    deviceId=0
    chunkPartNonces=320000
    refreshInterval=2000
    connectionTimeout=30000



  • @rds LOL yes Tb am sorry .



  • @SKANDI , so that happens to me once in awhile. After a block finishes, the JMiner will pop off lines saying it can't contact the pool. 1, 2 even 6 or seven. Then it just sits there like it;s dead, but when the next block rolls around it starts right up. Is this your experience. Did you wait until the next block started to see if the miner will respond?



  • Unfortunately this is not what is happening i can live with missing 2 or 3 blocks that's fine, but in my case the Jminer will keep rolling "unable to get info from wallet". And having I3 it's taking 27 sec to scan the 28 TB. while the GPU can scan them in 13- 17 secs. Any CPU u would recommend cause am feedup with the Jminer.



  • @SKANDI , 28 sec for scan is good and if you add another 28TB that will only go up by a few secs. Run the CPU miner while you troubleshoot the JMiner.

    First I would set up the JMiner for solo without changing your reward assignment. See if it scans. It should but if you get a DL it will report reward recipient is not a match.



  • @SKANDI said in GPU Reading Speed Falling from 1200+ Mb to 303 Mb using the jminer-0.4.11.:

    Once i start the Jminer it scans the HDD and it detects a Deadline. But after the pool send the second block am receiving the error and the miner not able to scan the HDD. i tried to set the connectionTimeout=70000 but still not working. tried to change the walletServer=Burstcoin (burstcoin which is the PC name) but still not working.

    Find the Config Below:
    plotPaths=G:/Burst/plots,F:/Burst/plots,E:/Burst/plots,D:/Burst/plots,
    poolMining=true
    numericAccountId=15897797494081209988
    poolServer=http://poolofd32th.club:8124
    walletServer=http://localhost:8125
    winnerRetriesOnAsync=
    winnerRetryIntervalInMs=
    devPool=false
    devPoolCommitsPerRound=
    soloServer=http://localhost:8125
    passPhrase=xxxxxxxxxxxxxx
    targetDeadline=
    platformId=0
    deviceId=0
    chunkPartNonces=320000
    refreshInterval=2000
    connectionTimeout=30000

    change

    walletServer=http://localhost:8125

    to

    walletServer=

    and I believe it will stop trying to check your wallet and say unable to connect, I mean you're not running a local wallet since you're pool mining, so if you don't have a local wallet running, it can't connect to that local wallet to check for data... but even then, if you're pool mining, you don't need to check a local wallet anyhow...

    also maybe

    winnerRetriesOnAsync=

    to

    winnerRetriesOnAsync=0

    since it might have some default value that will keep trying to check, but if you set retry to 0 it won't try or retry at all? something like that?



  • @Darkbane , good point. I always run a local wallet even when pool mining so I never thought of that.



  • C:\Users\SKANDI\AppData\Roaming\BurstWallet\burstcoin-jminer-0.4.10-SNAPSHOT>java -jar -d64 -XX:+UseG1GC burstcoin-jminer-0.4.10-SNAPSHOT.jar
    22:26:42.633 [main] INFO burstcoin.jminer.JMinerApplication - Starting the engines ... please wait!
    WARNING: An illegal reflective access operation has occurred
    WARNING: Illegal reflective access by org.springframework.cglib.core.ReflectUtils$1 (jar:file:/C:/Users/SKANDI/AppData/Roaming/BurstWallet/burstcoin-jminer-0.4.10-SNAPSHOT/burstcoin-jminer-0.4.10-SNAPSHOT.jar!/BOOT-INF/lib/spring-core-4.3.8.RELEASE.jar!/) to method java.lang.ClassLoader.defineClass(java.lang.String,byte[],int,int,java.security.ProtectionDomain)
    WARNING: Please consider reporting this to the maintainers of org.springframework.cglib.core.ReflectUtils$1
    WARNING: Use --illegal-access=warn to enable warnings of further illegal reflective access operations
    WARNING: All illegal access operations will be denied in a future release
    2017-10-05 22:26:44.432 INFO 5472 --- [ main] b.jminer.core.checker.util.OCLChecker : -------------------------------------------------------
    2017-10-05 22:26:44.448 INFO 5472 --- [ main] b.jminer.core.checker.util.OCLChecker : List of system openCL platforms and devices (* = used for mining)
    2017-10-05 22:26:44.448 INFO 5472 --- [ main] b.jminer.core.checker.util.OCLChecker :
    2017-10-05 22:26:44.448 INFO 5472 --- [ main] b.jminer.core.checker.util.OCLChecker : * PLATFORM-[0] NVIDIA CUDA - (OpenCL 1.2 CUDA 9.0.191)
    2017-10-05 22:26:44.463 INFO 5472 --- [ main] b.jminer.core.checker.util.OCLChecker : * DEVICE-[0] GeForce GTX 1080 Ti (11GB) - NVIDIA Corporation (OpenCL 1.2 CUDA | '385.69')
    2017-10-05 22:26:44.463 INFO 5472 --- [ main] b.jminer.core.checker.util.OCLChecker : * [0] work group size: '1024', computing units: '28', available 'true'
    2017-10-05 22:26:44.463 INFO 5472 --- [ main] b.jminer.core.checker.util.OCLChecker : DEVICE-[1] GeForce GTX 1080 Ti (11GB) - NVIDIA Corporation (OpenCL 1.2 CUDA | '385.69')
    2017-10-05 22:26:44.463 INFO 5472 --- [ main] b.jminer.core.checker.util.OCLChecker : [1] work group size: '1024', computing units: '28', available 'true'
    2017-10-05 22:26:44.463 INFO 5472 --- [ main] b.jminer.core.checker.util.OCLChecker : DEVICE-[2] GeForce GTX 1060 6GB (6GB) - NVIDIA Corporation (OpenCL 1.2 CUDA | '385.69')
    2017-10-05 22:26:44.463 INFO 5472 --- [ main] b.jminer.core.checker.util.OCLChecker : [2] work group size: '1024', computing units: '10', available 'true'
    2017-10-05 22:26:44.605 INFO 5472 --- [ main] b.jminer.core.checker.util.OCLChecker :
    2017-10-05 22:26:44.621 INFO 5472 --- [ main] b.jminer.core.checker.util.OCLChecker : (*) openCL context successfully started! (platformId: 0, deviceId: 0)
    2017-10-05 22:26:44.621 INFO 5472 --- [ main] b.jminer.core.checker.util.OCLChecker : -------------------------------------------------------
    2017-10-05 22:26:44.636 INFO 5472 --- [ main] burstcoin.jminer.core.CoreProperties : Winner and PoolInfo feature disabled, property 'walletServer' undefined!
    2017-10-05 22:26:45.271 INFO 5472 --- [ main] burstcoin.jminer.JMinerCommandLine : -------------------------------------------------------
    2017-10-05 22:26:45.286 INFO 5472 --- [ main] burstcoin.jminer.JMinerCommandLine : Burstcoin (BURST)
    2017-10-05 22:26:45.286 INFO 5472 --- [ main] burstcoin.jminer.JMinerCommandLine : __ __ GPU assisted PoC-Miner
    2017-10-05 22:26:45.286 INFO 5472 --- [ main] burstcoin.jminer.JMinerCommandLine : || _____ || ____ ___________
    2017-10-05 22:26:45.286 INFO 5472 --- [ main] burstcoin.jminer.JMinerCommandLine : version | |/ | |/ _/ __ _ __
    2017-10-05 22:26:45.286 INFO 5472 --- [ main] burstcoin.jminer.JMinerCommandLine : 0.4.10 | | Y Y \ | | \ /| | /
    2017-10-05 22:26:45.302 INFO 5472 --- [ main] burstcoin.jminer.JMinerCommandLine : /_
    | |
    || /|| /_ >|
    2017-10-05 22:26:45.302 INFO 5472 --- [ main] burstcoin.jminer.JMinerCommandLine : _
    ___| / / /
    2017-10-05 22:26:45.302 INFO 5472 --- [ main] burstcoin.jminer.JMinerCommandLine : mining engine: BURST-LUXE-RED2-G6JW-H4HG5
    2017-10-05 22:26:45.302 INFO 5472 --- [ main] burstcoin.jminer.JMinerCommandLine : openCL checker: BURST-QHCJ-9HB5-PTGC-5Q8J9
    2017-10-05 22:26:46.046 WARN 5472 --- [cTaskExecutor-1] b.j.c.n.t.NetworkRequestMiningInfoTask : Unable to get mining info from wallet.
    2017-10-05 22:26:47.679 WARN 5472 --- [cTaskExecutor-2] b.j.c.n.t.NetworkRequestMiningInfoTask : Unable to get mining info from wallet.
    2017-10-05 22:26:49.694 WARN 5472 --- [cTaskExecutor-3] b.j.c.n.t.NetworkRequestMiningInfoTask : Unable to get mining info from wallet.
    2017-10-05 22:26:51.704 WARN 5472 --- [cTaskExecutor-4] b.j.c.n.t.NetworkRequestMiningInfoTask : Unable to get mining info from wallet.
    2017-10-05 22:26:54.212 INFO 5472 --- [ roundPool-1] burstcoin.jminer.JMinerCommandLine : -------------------------------------------------------
    2017-10-05 22:26:54.215 INFO 5472 --- [ roundPool-1] burstcoin.jminer.JMinerCommandLine : START block '411316', scoopNumber '28', capacity '31289 GB'
    2017-10-05 22:26:54.215 INFO 5472 --- [ roundPool-1] burstcoin.jminer.JMinerCommandLine : targetDeadline '2592000', baseTarget '173107'
    2017-10-05 22:26:54.501 INFO 5472 --- [ roundPool-1] burstcoin.jminer.JMinerCommandLine : dl '2241669413' > '2592000' skipped
    2017-10-05 22:26:54.501 INFO 5472 --- [ readerPool-3] burstcoin.jminer.JMinerCommandLine : 1% done (0TB 20GB), avg.'17 MB/s'
    2017-10-05 22:26:54.501 INFO 5472 --- [ roundPool-1] burstcoin.jminer.JMinerCommandLine : dl '370595500' > '2592000' skipped
    2017-10-05 22:26:54.567 INFO 5472 --- [ roundPool-1] burstcoin.jminer.JMinerCommandLine : dl '336131562' > '2592000' skipped
    2017-10-05 22:26:54.629 INFO 5472 --- [ roundPool-1] burstcoin.jminer.JMinerCommandLine : dl '18684560' > '2592000' skipped
    2017-10-05 22:26:54.817 INFO 5472 --- [ roundPool-1] burstcoin.jminer.JMinerCommandLine : dl '2348211' send (pool) [nonce '30299082']
    2017-10-05 22:26:57.011 INFO 5472 --- [ readerPool-1] burstcoin.jminer.JMinerCommandLine : 12% done (3TB 481GB), avg.'302 MB/s', eff.'336 MB/s'
    2017-10-05 22:26:59.527 INFO 5472 --- [ readerPool-3] burstcoin.jminer.JMinerCommandLine : 23% done (6TB 962GB), avg.'319 MB/s', eff.'337 MB/s'
    2017-10-05 22:27:01.782 WARN 5472 --- [TaskExecutor-10] b.j.c.n.t.NetworkRequestMiningInfoTask : Unable to get mining info from wallet.
    2017-10-05 22:27:02.030 INFO 5472 --- [ readerPool-3] burstcoin.jminer.JMinerCommandLine : 34% done (10TB 443GB), avg.'325 MB/s', eff.'339 MB/s'
    2017-10-05 22:27:02.423 INFO 5472 --- [cTaskExecutor-6] burstcoin.jminer.JMinerCommandLine : dl '2348211' confirmed! [ 27d 4h 16m 51s ]
    2017-10-05 22:27:04.155 WARN 5472 --- [TaskExecutor-11] b.j.c.n.t.NetworkRequestMiningInfoTask : Unable to get mining info from wallet.
    2017-10-05 22:27:04.595 INFO 5472 --- [ readerPool-1] burstcoin.jminer.JMinerCommandLine : 45% done (13TB 925GB), avg.'327 MB/s', eff.'331 MB/s'
    2017-10-05 22:27:06.554 WARN 5472 --- [TaskExecutor-12] b.j.c.n.t.NetworkRequestMiningInfoTask : Unable to get mining info from wallet.
    2017-10-05 22:27:07.078 INFO 5472 --- [ roundPool-1] burstcoin.jminer.JMinerCommandLine : dl '2242615' send (pool) [nonce '106008088']
    2017-10-05 22:27:07.094 INFO 5472 --- [ readerPool-4] burstcoin.jminer.JMinerCommandLine : 56% done (17TB 385GB), avg.'329 MB/s', eff.'338 MB/s'
    2017-10-05 22:27:09.646 INFO 5472 --- [ readerPool-1] burstcoin.jminer.JMinerCommandLine : 67% done (20TB 866GB), avg.'329 MB/s', eff.'333 MB/s'
    2017-10-05 22:27:09.981 WARN 5472 --- [TaskExecutor-15] b.j.c.n.t.NetworkRequestMiningInfoTask : Unable to get mining info from wallet.
    2017-10-05 22:27:11.835 WARN 5472 --- [TaskExecutor-16] b.j.c.n.t.NetworkRequestMiningInfoTask : Unable to get mining info from wallet.
    2017-10-05 22:27:12.161 INFO 5472 --- [ readerPool-4] burstcoin.jminer.JMinerCommandLine : 78% done (24TB 347GB), avg.'331 MB/s', eff.'337 MB/s'
    2017-10-05 22:27:13.806 WARN 5472 --- [TaskExecutor-17] b.j.c.n.t.NetworkRequestMiningInfoTask : Unable to get mining info from wallet.
    2017-10-05 22:27:14.715 INFO 5472 --- [ readerPool-4] burstcoin.jminer.JMinerCommandLine : 89% done (27TB 829GB), avg.'331 MB/s', eff.'332 MB/s'
    2017-10-05 22:27:14.777 INFO 5472 --- [ roundPool-1] burstcoin.jminer.JMinerCommandLine : dl '2126276' send (pool) [nonce '116062894']
    2017-10-05 22:27:14.963 INFO 5472 --- [ roundPool-1] burstcoin.jminer.JMinerCommandLine : dl '2021294' send (pool) [nonce '26789351']
    2017-10-05 22:27:15.104 WARN 5472 --- [TaskExecutor-18] b.j.c.n.task.NetworkSubmitPoolNonceTask : Error: Failed to submit nonce to pool due Exception.
    2017-10-05 22:27:15.119 INFO 5472 --- [TaskExecutor-18] burstcoin.jminer.JMinerCommandLine : dl '2126276' NOT confirmed! [ 24d 14h 37m 56s ]
    2017-10-05 22:27:15.416 WARN 5472 --- [TaskExecutor-19] b.j.c.n.task.NetworkSubmitPoolNonceTask : Error: Failed to submit nonce to pool due Exception.
    2017-10-05 22:27:15.416 INFO 5472 --- [TaskExecutor-19] burstcoin.jminer.JMinerCommandLine : dl '2021294' NOT confirmed! [ 23d 9h 28m 14s ]
    2017-10-05 22:27:15.795 WARN 5472 --- [TaskExecutor-20] b.j.c.n.t.NetworkRequestMiningInfoTask : Unable to get mining info from wallet.
    2017-10-05 22:27:15.928 INFO 5472 --- [TaskExecutor-13] burstcoin.jminer.JMinerCommandLine : dl '2242615' confirmed! [ 25d 22h 56m 55s ]
    2017-10-05 22:27:17.419 INFO 5472 --- [ readerPool-4] burstcoin.jminer.JMinerCommandLine : 100% done (31TB 289GB), avg.'329 MB/s', eff.'314 MB/s'
    2017-10-05 22:27:17.669 INFO 5472 --- [ roundPool-1] burstcoin.jminer.JMinerCommandLine : FINISH block '411316', best deadline '2242615', round time '23s 204ms'
    2017-10-05 22:27:19.795 WARN 5472 --- [TaskExecutor-22] b.j.c.n.t.NetworkRequestMiningInfoTask : Unable to get mining info from wallet.
    2017-10-05 22:27:27.903 WARN 5472 --- [TaskExecutor-26] b.j.c.n.t.NetworkRequestMiningInfoTask : Unable to get mining info from wallet.
    2017-10-05 22:29:56.211 WARN 5472 --- [askExecutor-100] b.j.c.n.t.NetworkRequestMiningInfoTask : Unable to get mining info from wallet.
    2017-10-05 22:30:02.215 WARN 5472 --- [askExecutor-103] b.j.c.n.t.NetworkRequestMiningInfoTask : Unable to get mining info from wallet.
    2017-10-05 22:30:04.196 WARN 5472 --- [askExecutor-104] b.j.c.n.t.NetworkRequestMiningInfoTask : Unable to get mining info from wallet.
    2017-10-05 22:30:06.229 WARN 5472 --- [askExecutor-105] b.j.c.n.t.NetworkRequestMiningInfoTask : Unable to get mining info from wallet.
    2017-10-05 22:30:08.287 WARN 5472 --- [askExecutor-106] b.j.c.n.t.NetworkRequestMiningInfoTask : Unable to get mining info from wallet.
    2017-10-05 22:30:12.239 WARN 5472 --- [askExecutor-108] b.j.c.n.t.NetworkRequestMiningInfoTask : Unable to get mining info from wallet.
    2017-10-05 22:30:16.691 WARN 5472 --- [askExecutor-110] b.j.c.n.t.NetworkRequestMiningInfoTask : Unable to get mining info from wallet.
    2017-10-05 22:30:20.240 WARN 5472 --- [askExecutor-112] b.j.c.n.t.NetworkRequestMiningInfoTask : Unable to get mining info from wallet.



  • @SKANDI first thing I would do is get the 0.4.11 version since it says it fixes some connection issues for walletserver...

    https://forums.burst-team.us/topic/24/burstcoin-jminer-v0-4-11-gpu-assisted-poc-miner-all-platforms

    thats the thread for the software, I generally don't like to give people links to software since thats how some folks try to spread malicious stuff, but you can go to that thread and click his link direct or use the link below, but I always recommend people get in the habit of going to the authors threads and links...

    https://github.com/de-luxe/burstcoin-jminer/releases

    P.S. but also the link below has all the properties and descriptions, could be helpful in tinkering around with things in the future or currently to solve the issue... (if you continue to have problems, in that forum thread above you can contact him directly and let him know whats going on after you get the latest version)

    https://github.com/de-luxe/burstcoin-jminer/wiki/configure-jminer.properties



  • Am not sure what is happening here I disabled the Firewall, I added extension to the Burst wallet, i've did everything am capable to do.

    Last option: install new windows and have a fresh start.



  • @SKANDI said in GPU Reading Speed Falling from 1200+ Mb to 303 Mb using the jminer-0.4.11.:

    Am not sure what is happening here I disabled the Firewall, I added extension to the Burst wallet, i've did everything am capable to do.

    Last option: install new windows and have a fresh start.

    did you read my message to you, you're using an OLDER version 0.4.10 and the first thing you should do is UPGRADE to 0.4.11 before doing crazy things like reinstalling windows... I also gave you direct links to the discussion thread for the software, which you will be able to contact the author of the software if upgrading to the latest version doesn't work... try all THAT before doing crazy stuff...



  • I run 4.10 just fine. The first thing you need to do like I said before is try another pool. The warning in the beginning of illegal operations is telling. Never saw that before. You need to make sure the problem isn't pool related. I've tried to connect to pools months ago that just wouldn't connect for me. I change to a diff pool, with no other changes to the config file and everything works fine.

    After you check the pool, try a different GPU, it looks like you have 3 of them.



  • @Darkbane @rds
    Thank you guys i really appreciate your help. I've been able to get the rig again online and mining fine, but still the :@:@ unable msg insisting to stay.

    plotPaths=G:/Burst/plots,F:/Burst/plots,E:/Burst/plots,D:/Burst/plots
    scanPathsEveryRound=false
    listPlotFiles=false
    poolMining=true
    numericAccountId=15897797494081209988
    poolServer=http://poolofd32th.club:8124
    walletServer=
    winnerRetriesOnAsync=0
    winnerRetryIntervalInMs=
    soloServer=http://localhost:8125
    passPhrase=xxxxxxxxxxxxxx
    targetDeadline=
    triggerServer=
    recommitDeadlines=
    platformId=0
    deviceId=2
    refreshInterval=2000
    updateMiningInfo=true
    connectionTimeout=800000
    debug=false
    writeLogFile=
    logFilePath=
    logPatternConsole=
    logPatternFile=
    readProgressPerRound=9
    byteUnitDecimal=true
    showDriveInfo=true
    showSkippedDeadlines=true
    chunkPartNonces=960000
    readerThreads=0
    logPatternConsole=%red(%d{HH:mm:ss.SSS}) %green(%msg%n)
    showSkippedDeadlines=true



  • @rds @Darkbane Check this guys how it's possible 40 TB getting all these blocks
    https://explore.burst.cryptoguru.org/account/3823180379533295353



  • @SKANDI ,

    So how did you get it to work? From the last config post, I see you are using the GeoForce 1060 (deviceID=2). Was that the fix?

    51ASIC.COM.China is running multiple machines, only one is picked up by the pool.

    There was a guy on Nicehash running 492 Antminer L3s making 2 BTC (~$9000) a day. Nicehash reports all devices, Burst does not. So if 51ASIC.COM.China is forging 6 blocks a day, he definitely has more than 40TB.

    What puzzles me is why he is pool mining, unless he is associated with the pool owners.