[ANN] jminer v0.5.3 - GPU assisted PoC-Miner for Burstcoin (BURST) - PoC2

[luxe]

Will you please tell me how did you managed 100Tb in single comp, and some more info on cooling system.

Add external usb3 HDDs. You also need some usb3 ports + hubs. You could use your internal HDDs at the same time. I need the win7 installation on my pc, so I'm mining 25 TB on CPU. Jminer won't work on win7 (it'll work, but you can't use the PC for anything else).

Edit: Mining on HDD doesn't need the caching at all, so if this is switched off on all OSs jminer may consume even less power, no?

If you know a way to switch off caching for Win7, feel free to tell us.
In your case of 25TB ... what about adding more memory to your PC?
16-32GB should be able to handle the cache needs?! (not sure if the benefit will be big enough to legitimate such a investion)

[equipoise]

Will you please tell me how did you managed 100Tb in single comp, and some more info on cooling system.

Add external usb3 HDDs. You also need some usb3 ports + hubs. You could use your internal HDDs at the same time. I need the win7 installation on my pc, so I'm mining 25 TB on CPU. Jminer won't work on win7 (it'll work, but you can't use the PC for anything else).

Edit: Mining on HDD doesn't need the caching at all, so if this is switched off on all OSs jminer may consume even less power, no?

If you know a way to switch off caching for Win7, feel free to tell us.
In your case of 25TB ... what about adding more memory to your PC?
16-32GB should be able to handle the cache needs?! (not sure if the benefit will be big enough to legitimate such a investion)

I'm with 16 GB RAM. Blago's miner had the same problem with win7 and then he fixed it, so it's doable.

@luxe, it's possible, C <=> Java  (FILE_FLAG_NO_BUFFERING)
    https://github.com/nyholku/purejavacomm/blob/master/src/jtermios/windows/WinAPI.java
    http://www.docjar.com/html/api/sun/nio/fs/WindowsConstants.java.html

[Yanakitu Tenatako]

Hello,

Today I upgraded win7 to win10, results are good.
JMINER works well, using only few Gb of RAM.
No stress on CPU. I have a feeling that even 4Gb of ram would be ok.

I plotted 6x4Tb drives, read time with GPU and jminer is 52 seconds.
GPU load is high 99%.
So far, so good. Before read time was 1m53s. So, very good result.

Considering adding more HDD drives, jminer is a must have tool.
Great job luxe.

GPU load is really low, from 30%-70%, even lower on hdd read, speed is 120mb/s shown in jminer.
Thinking like there can be better result.

[luxe]

Will you please tell me how did you managed 100Tb in single comp, and some more info on cooling system.

Add external usb3 HDDs. You also need some usb3 ports + hubs. You could use your internal HDDs at the same time. I need the win7 installation on my pc, so I'm mining 25 TB on CPU. Jminer won't work on win7 (it'll work, but you can't use the PC for anything else).

Edit: Mining on HDD doesn't need the caching at all, so if this is switched off on all OSs jminer may consume even less power, no?

If you know a way to switch off caching for Win7, feel free to tell us.
In your case of 25TB ... what about adding more memory to your PC?
16-32GB should be able to handle the cache needs?! (not sure if the benefit will be big enough to legitimate such a investion)

I'm with 16 GB RAM. Blago's miner had the same problem with win7 and then he fixed it, so it's doable.

@luxe, it's possible, C <=> Java  (FILE_FLAG_NO_BUFFERING)
    https://github.com/nyholku/purejavacomm/blob/master/src/jtermios/windows/WinAPI.java
    http://www.docjar.com/html/api/sun/nio/fs/WindowsConstants.java.html

I remember that discussion, my point is still, that i will not implement a Win7 specail case in a java application ...
I hoped for a way, to edit this FILE_FLAG_NO_BUFFERING  in the OS itself, in registry or something ... or via parameter for java vm ...
 

[luxe]

Hello,

Today I upgraded win7 to win10, results are good.
JMINER works well, using only few Gb of RAM.
No stress on CPU. I have a feeling that even 4Gb of ram would be ok.

I plotted 6x4Tb drives, read time with GPU and jminer is 52 seconds.
GPU load is high 99%.
So far, so good. Before read time was 1m53s. So, very good result.

Considering adding more HDD drives, jminer is a must have tool.
Great job luxe.

GPU load is really low, from 30%-70%, even lower on hdd read, speed is 120mb/s shown in jminer.
Thinking like there can be better result.

I am very pleased to hear that ...
You say you need 52sec. thats still a little slow.
Data of a 4TB drive should be read in below 20sec. (my experience, but can depend on sata controller etc.)
If you GPU is not 100% while checking deadlines, the number of drives should not have influence on the 52sec round time.
So basically, if you add another 6x4TB under same conditions, your read speed would be 240mb/s and round would still be finished in 52sec.

Anyway, 120mb/s divided by number of drives is 20mb/s per drive (not cool) ...
If you drives read speed is not limited by hardware, i suggest:
- Use every drive as single drive (no raid or extended partitions over multiple drives or something)
- Use a high staggersize for your plotfiles to reduce seak operations of your harddrive, https://bchain.info/BURST/tools/overlap will provide info about that! Optimize your plotfiles if your staggersize is 8096 or something!

Plot Optimizer v1.6:
https://bitcointalk.org/index.php?topic=731923.msg9440236#msg9440236
Plot Optimizer v1.6 with GUI for Win:
http://forum.burst-team.us:4567/topic/26/plot-optimizer-v1-6-with-gui-1-0-3-j6jq-win

[Yanakitu Tenatako]

Thank you for post luxe,

I have a problem with win10 and jminer.
Installed everything from scratch and got this error on all machines:

Exception: java.lang.OutOfMemoryError thrown from the UncaughtExceptionHandler in thread "Timer-1"
Exception in thread "readerPool-52" java.lang.OutOfMemoryError: Java heap space
Exception in thread "readerPool-51" java.lang.reflect.UndeclaredThrowableException: Failed to invoke event listener method
HandlerMethod details:
Bean [burstcoin.jminer.core.checker.Checker]
Method [public void burstcoin.jminer.core.checker.Checker.handleMessage(burstcoin.jminer.core.reader.event.ReaderLoadedPartEvent)]
Resolved arguments:

• [type=burstcoin.jminer.core.reader.event.ReaderLoadedPartEvent] [value=burstcoin.jminer.core.reader.event.ReaderLoadedPartEvent@c6b981]

        at org.springframework.context.event.ApplicationListenerMethodAdapter.doInvoke(ApplicationListenerMethodAdapter.java:240)
        at org.springframework.context.event.ApplicationListenerMethodAdapter.processEvent(ApplicationListenerMethodAdapter.java:113)
        at org.springframework.context.event.ApplicationListenerMethodAdapter.onApplicatio nEvent(ApplicationListenerMethodAdapter.java:103)
        at org.springframework.context.event.SimpleApplicationEventMulticaster.invokeListe ner(SimpleApplicationEventMulticaster.java:163)
        at org.springframework.context.event.SimpleApplicationEventMulticaster.multicastEv ent(SimpleApplicationEventMulticaster.java:136)
        at org.springframework.context.support.AbstractApplicationContext.publishEvent(AbstractApplicationContext.java:380)
        at org.springframework.context.support.AbstractApplicationContext.publishEvent(AbstractApplicationContext.java:347)
        at burstcoin.jminer.core.reader.task.ReaderLoadDriveTask.load(ReaderLoadDriveTask.java:91)
        at burstcoin.jminer.core.reader.task.ReaderLoadDriveTask.run(ReaderLoadDriveTask.java:59)
        at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source)
        at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source)
        at java.lang.Thread.run(Unknown Source)
Caused by: java.lang.OutOfMemoryError: Java heap space


Win 10 Pro 64bit, java latest. Getting same error on every machine.
This occurs really in matter of minutes, sometime after hour or so.


Regarding speed, this is a situation:
Plots of 26Tb are read in less than a minute, 50-60 seconds.


2016-01-13 05:13:29.007  INFO 4856 --- [    roundPool-1] burstcoin.jminer.CommandLineRunner       : dl '550384831' > '60000' skipped
2016-01-13 05:13:29.022  INFO 4856 --- [  readerPool-26] burstcoin.jminer.CommandLineRunner       : 1% done (0TB 2GB), eff.read '8 MB/s'
2016-01-13 05:13:29.022  INFO 4856 --- [    roundPool-1] burstcoin.jminer.CommandLineRunner       : dl '300150332' > '60000' skipped
2016-01-13 05:13:29.044  INFO 4856 --- [    roundPool-1] burstcoin.jminer.CommandLineRunner       : dl '75916006' > '60000' skipped
2016-01-13 05:13:29.091  INFO 4856 --- [    roundPool-1] burstcoin.jminer.CommandLineRunner       : dl '39550334' > '60000' skipped
2016-01-13 05:13:29.107  INFO 4856 --- [    roundPool-1] burstcoin.jminer.CommandLineRunner       : dl '29188557' > '60000' skipped
2016-01-13 05:13:29.528  INFO 4856 --- [    roundPool-1] burstcoin.jminer.CommandLineRunner       : dl '21378323' > '60000' skipped
2016-01-13 05:13:29.634  INFO 4856 --- [    roundPool-1] burstcoin.jminer.CommandLineRunner       : dl '14026369' > '60000' skipped
2016-01-13 05:13:29.796  INFO 4856 --- [    roundPool-1] burstcoin.jminer.CommandLineRunner       : dl '8353362' > '60000' skipped
2016-01-13 05:13:30.095  INFO 4856 --- [    roundPool-1] burstcoin.jminer.CommandLineRunner       : dl '2465560' > '60000' skipped
2016-01-13 05:13:30.387  INFO 4856 --- [    roundPool-1] burstcoin.jminer.CommandLineRunner       : dl '2067519' > '60000' skipped
2016-01-13 05:13:32.017  INFO 4856 --- [    roundPool-1] burstcoin.jminer.CommandLineRunner       : dl '1476051' > '60000' skipped
2016-01-13 05:13:32.095  INFO 4856 --- [    roundPool-1] burstcoin.jminer.CommandLineRunner       : dl '108588' > '60000' skipped
2016-01-13 05:13:34.569  INFO 4856 --- [  readerPool-25] burstcoin.jminer.CommandLineRunner       : 12% done (2TB 846GB), eff.read '128 MB/s'
2016-01-13 05:13:40.236  INFO 4856 --- [  readerPool-24] burstcoin.jminer.CommandLineRunner       : 23% done (5TB 668GB), eff.read '128 MB/s'
2016-01-13 05:13:45.591  INFO 4856 --- [  readerPool-26] burstcoin.jminer.CommandLineRunner       : 34% done (8TB 490GB), eff.read '130 MB/s'
2016-01-13 05:13:49.630  INFO 4856 --- [    roundPool-1] burstcoin.jminer.CommandLineRunner       : dl '43168' send (solo)
2016-01-13 05:13:49.894  INFO 4856 --- [  networkPool-1] burstcoin.jminer.CommandLineRunner       : dl '43168' confirmed!  [ 0d 11h 59m 28s ]
2016-01-13 05:13:50.980  INFO 4856 --- [  readerPool-31] burstcoin.jminer.CommandLineRunner       : 45% done (11TB 310GB), eff.read '131 MB/s'
2016-01-13 05:13:56.462  INFO 4856 --- [  readerPool-26] burstcoin.jminer.CommandLineRunner       : 56% done (14TB 132GB), eff.read '131 MB/s'
2016-01-13 05:14:03.833  INFO 4856 --- [  readerPool-29] burstcoin.jminer.CommandLineRunner       : 67% done (16TB 978GB), eff.read '124 MB/s'
2016-01-13 05:14:09.519  INFO 4856 --- [  readerPool-29] burstcoin.jminer.CommandLineRunner       : 78% done (19TB 798GB), eff.read '124 MB/s'
2016-01-13 05:14:15.283  INFO 4856 --- [  readerPool-29] burstcoin.jminer.CommandLineRunner       : 89% done (22TB 620GB), eff.read '124 MB/s'
2016-01-13 05:14:25.380  INFO 4856 --- [  readerPool-24] burstcoin.jminer.CommandLineRunner       : 100% done (25TB 440GB), eff.read '115 MB/s'
2016-01-13 05:14:25.395  INFO 4856 --- [    roundPool-1] burstcoin.jminer.CommandLineRunner       : FINISH block '185941', best deadline '43168', round time '56s 420ms'


Considering very low-end GPU integrated in APU it is ok for me, GPU usage is on average of 60% (I thought that GPU will be bottleneck - but it is not).
Here are screenshots of GPU usage while mining:

     



I dont know what could cause problem, while I tested it had no issues... never expected this situation.

[luxe]

...
Exception: java.lang.OutOfMemoryError thrown from the UncaughtExceptionHandler in thread "Timer-1"
Exception in thread "readerPool-52" java.lang.OutOfMemoryError: Java heap space
...

Java VM is running out of memory (sometimes this happens even if not all system memory is used) ...
you should monitor, if really all available memory of your system is used ...
You can force Java VM to use more memory if not. Your machines have 8GB momory, right?

On memory issues:
1. allow java to allocate more memory e.g.: -Xmx6G will allow java to use up to 6GB of memory, for example:

Code:

java -jar -Xmx6G -XX:+UseG1GC burstcoin-jminer-0.3.6-RELEASE.jar

2. reduce 'chunkPartNonces' in jminer.properties (will only help, if GPU is fast enough, will increase CPU usage)
Maybe try 160000 instead of default 320000.

...
I dont know what could cause problem, while I tested it had no issues... never expected this situation.

If there is a fast block ... so the previous round is not finished, the memory usage may have a little peak.
Maybe you didn't have a fast block while testing ... but I'm quite sure that -Xmx6G will fix your problem.

[Yanakitu Tenatako]

...
Exception: java.lang.OutOfMemoryError thrown from the UncaughtExceptionHandler in thread "Timer-1"
Exception in thread "readerPool-52" java.lang.OutOfMemoryError: Java heap space
...

Java VM is running out of memory (sometimes this happens even if not all system memory is used) ...
you should monitor, if really all available memory of your system is used ...
You can force Java VM to use more memory if not. Your machines have 8GB momory, right?

On memory issues:
1. allow java to allocate more memory e.g.: -Xmx6G will allow java to use up to 6GB of memory, for example:

Code:

java -jar -Xmx6G -XX:+UseG1GC burstcoin-jminer-0.3.6-RELEASE.jar

2. reduce 'chunkPartNonces' in jminer.properties (will only help, if GPU is fast enough, will increase CPU usage)
Maybe try 160000 instead of default 320000.

...
I dont know what could cause problem, while I tested it had no issues... never expected this situation.

If there is a fast block ... so the previous round is not finished, the memory usage may have a little peak.
Maybe you didn't have a fast block while testing ... but I'm quite sure that -Xmx6G will fix your problem.

Memory usage is below 1,5Gb according to task manager.
Going to try right now your suggestions. Thanks.


c:\Burst>"run 0.3.6-RELEASE.bat"

c:\Burst>java -jar -Xmx6G -XX:+UseG1GC burstcoin-jminer-0.3.6-RELEASE.jar
Invalid maximum heap size: -Xmx6G
The specified size exceeds the maximum representable size.
Error: Could not create the Java Virtual Machine.
Error: A fatal exception has occurred. Program will exit.

c:\Burst>"run 0.3.6-RELEASE.bat"

c:\Burst>java -jar -Xmx4G -XX:+UseG1GC burstcoin-jminer-0.3.6-RELEASE.jar
Invalid maximum heap size: -Xmx4G
The specified size exceeds the maximum representable size.
Error: Could not create the Java Virtual Machine.
Error: A fatal exception has occurred. Program will exit.

In device manager i 6.95Gb of ram available (of 8Gb maximum).


And chunkPartNonces=160000 is already from start, I changed it.

Will start with parameter  java -jar -Xmx1G -XX:+UseG1GC burstcoin-jminer-0.3.6-RELEASE.jar

[luxe]

...
Exception: java.lang.OutOfMemoryError thrown from the UncaughtExceptionHandler in thread "Timer-1"
Exception in thread "readerPool-52" java.lang.OutOfMemoryError: Java heap space
...

Java VM is running out of memory (sometimes this happens even if not all system memory is used) ...
you should monitor, if really all available memory of your system is used ...
You can force Java VM to use more memory if not. Your machines have 8GB momory, right?

On memory issues:
1. allow java to allocate more memory e.g.: -Xmx6G will allow java to use up to 6GB of memory, for example:

Code:

java -jar -Xmx6G -XX:+UseG1GC burstcoin-jminer-0.3.6-RELEASE.jar

2. reduce 'chunkPartNonces' in jminer.properties (will only help, if GPU is fast enough, will increase CPU usage)
Maybe try 160000 instead of default 320000.

...
I dont know what could cause problem, while I tested it had no issues... never expected this situation.

If there is a fast block ... so the previous round is not finished, the memory usage may have a little peak.
Maybe you didn't have a fast block while testing ... but I'm quite sure that -Xmx6G will fix your problem.

Memory usage is below 1,5Gb according to task manager.
Going to try right now your suggestions. Thanks.


c:\Burst>"run 0.3.6-RELEASE.bat"

c:\Burst>java -jar -Xmx6G -XX:+UseG1GC burstcoin-jminer-0.3.6-RELEASE.jar
Invalid maximum heap size: -Xmx6G
The specified size exceeds the maximum representable size.
Error: Could not create the Java Virtual Machine.
Error: A fatal exception has occurred. Program will exit.

c:\Burst>"run 0.3.6-RELEASE.bat"

c:\Burst>java -jar -Xmx4G -XX:+UseG1GC burstcoin-jminer-0.3.6-RELEASE.jar
Invalid maximum heap size: -Xmx4G
The specified size exceeds the maximum representable size.
Error: Could not create the Java Virtual Machine.
Error: A fatal exception has occurred. Program will exit.

In device manager i 6.95Gb of ram available (of 8Gb maximum).


And chunkPartNonces=160000 is already from start, I changed it.

Will start with parameter  java -jar -Xmx1G -XX:+UseG1GC burstcoin-jminer-0.3.6-RELEASE.jar

Well, thats strange, please make sure you use 64bit Java ... test it in command line with:

Code:

java -version

To download Java 64bit JRE (uninstall the 32bit java before installing the 64bit one)
http://www.oracle.com/technetwork/java/javase/downloads/jre8-downloads-2133155.html


Btw. if that was the problem, you will not need that -Xmx6G anymore i guess ...

[Yanakitu Tenatako]

C:\>cd Burst

C:\Burst>java -version
java version "1.8.0_66"
Java(TM) SE Runtime Environment (build 1.8.0_66-b18)
Java HotSpot(TM) Client VM (build 25.66-b18, mixed mode, sharing)

C:\Burst>



Never installed 32bit version. Clean fresh 64bit install only.
Again problems, jminer with option  java -jar -Xmx1G -XX:+UseG1GC burstcoin-jminer-0.3.6-RELEASE.jar
it just freezes at 100% plot reading done, not telling how long it takes to read, and not getting next block info.

[luxe]

...
java version "1.8.0_66"
Java(TM) SE Runtime Environment (build 1.8.0_66-b18)
Java HotSpot(TM) Client VM (build 25.66-b18, mixed mode, sharing)
...

If it's 64-bits it will say so, otherwise it's 32-bits.
source: http://stackoverflow.com/questions/4574090/installed-jvm-is-64-bit-or-32-bit

mine:
java version "1.8.0_60"
Java(TM) SE Runtime Environment (build 1.8.0_60-b27)
Java HotSpot(TM) 64-Bit Server VM (build 25.60-b23, mixed mode)

You can try on the command line:

Code:

java -d64 -version

If it's not a 64-bit version, you'll get a message that looks like:

Code:

This Java instance does not support a 64-bit JVM. Please install the desired version.

If not maybe add -d64 as argument to the *.bat, to force 64bit. (if 32bit and 64bit are supported by your java vm, and jminer why ever takes the 32bit one)

Code:

java -jar -d64 -Xmx6G -XX:+UseG1GC burstcoin-jminer-0.3.6-RELEASE.jar

source: http://stackoverflow.com/questions/2062020/how-can-i-tell-if-im-running-in-64-bit-jvm-or-32-bit-jvm-from-within-a-program

EDIT:

Again problems, jminer with option  java -jar -Xmx1G -XX:+UseG1GC burstcoin-jminer-0.3.6-RELEASE.jar
it just freezes at 100% plot reading done, not telling how long it takes to read, and not getting next block info.

Thats because 1G means the Java VM can only use 1GB of memory, thats to small ... we should focus on running with 64-bit and 6GB :-)
Just to explain, a 32-bit is limited in addressing memory, you noticed that, guess even -Xmx2G did not work.

[Yanakitu Tenatako]

Going to fix right away.
But I am certain I installed 64bit version, I always do.
De facto, it is not then 64bit.

Update in 5 minutes.

Thank you again, Luxe.

[Yanakitu Tenatako]

C:\Burst>java -version
java version "1.8.0_66"
Java(TM) SE Runtime Environment (build 1.8.0_66-b18)
Java HotSpot(TM) 64-Bit Server VM (build 25.66-b18, mixed mode)

C:\Burst>

It is now OK. Really sorry for this, I checked again and I DL-ed 64bit installer. Anyone should pay attention to what this java automatic installer is doing by own will.


First result is here : (looks really gooooood )

C:\Burst>java -jar -d64 -Xmx6G -XX:+UseG1GC burstcoin-jminer-0.3.6-RELEASE.jar
21:03:29.190 [Timer-0] INFO  burstcoin.jminer.CommandLineRunner - start the engines ...

2016-01-13 21:03:31.018  INFO 3396 --- [        Timer-0] o.s.boot.SpringApplication               : Starting application on Miner-091 with PID 3396 (started by Arrow in C:\Burst)
2016-01-13 21:03:31.190  INFO 3396 --- [        Timer-0] s.c.a.AnnotationConfigApplicationContext : Refreshing org.springframework.context.annotation.AnnotationConfigApplicationContext@23e81b98: startup date [Wed Jan 13 21:03:31 PST 2016]; root of context hierarchy
2016-01-13 21:03:34.584  INFO 3396 --- [        Timer-0] b.jminer.core.checker.util.OCLChecker    : success ... started openCL context!
2016-01-13 21:03:34.662  INFO 3396 --- [        Timer-0] o.s.s.concurrent.ThreadPoolTaskExecutor  : Initializing ExecutorService  'networkPool'
2016-01-13 21:03:34.693  INFO 3396 --- [        Timer-0] o.s.s.concurrent.ThreadPoolTaskExecutor  : Initializing ExecutorService  'readerPool'
2016-01-13 21:03:35.568  INFO 3396 --- [        Timer-0] o.s.s.concurrent.ThreadPoolTaskExecutor  : Initializing ExecutorService  'roundPool'
2016-01-13 21:03:35.881  INFO 3396 --- [        Timer-0] org.eclipse.jetty.util.log               : Logging initialized @8989ms
2016-01-13 21:03:39.643  INFO 3396 --- [        Timer-0] o.s.j.e.a.AnnotationMBeanExporter        : Registering beans for JMX exposure on startup
2016-01-13 21:03:39.690  INFO 3396 --- [        Timer-0] o.s.boot.SpringApplication               : Started application in 9.813 seconds (JVM running for 12.801)
2016-01-13 21:03:39.706  INFO 3396 --- [        Timer-0] burstcoin.jminer.CommandLineRunner       :
2016-01-13 21:03:39.721  INFO 3396 --- [        Timer-0] burstcoin.jminer.CommandLineRunner       :                             Burstcoin (BURST)
2016-01-13 21:03:39.737  INFO 3396 --- [        Timer-0] burstcoin.jminer.CommandLineRunner       :             __         __   GPU assisted PoC-Miner
2016-01-13 21:03:39.737  INFO 3396 --- [        Timer-0] burstcoin.jminer.CommandLineRunner       :            |__| _____ |__| ____   ___________
2016-01-13 21:03:39.737  INFO 3396 --- [        Timer-0] burstcoin.jminer.CommandLineRunner       :    version |  |/     \|  |/    \_/ __ \_  __ \
2016-01-13 21:03:39.753  INFO 3396 --- [        Timer-0] burstcoin.jminer.CommandLineRunner       :      0.3.6 |  |  Y Y  \  |   |  \  ___/|  | \/
2016-01-13 21:03:39.753  INFO 3396 --- [        Timer-0] burstcoin.jminer.CommandLineRunner       :        /\__|  |__|_|  /__|___|  /\___  >__|
2016-01-13 21:03:39.753  INFO 3396 --- [        Timer-0] burstcoin.jminer.CommandLineRunner       :        \______|     \/        \/     \/
2016-01-13 21:03:39.768  INFO 3396 --- [        Timer-0] burstcoin.jminer.CommandLineRunner       :       mining engine: BURST-LUXE-ZDVD-CX3E-3SM58
2016-01-13 21:03:39.768  INFO 3396 --- [        Timer-0] burstcoin.jminer.CommandLineRunner       :      openCL checker: BURST-QHCJ-9HB5-PTGC-5Q8J9
2016-01-13 21:03:40.393  INFO 3396 --- [    roundPool-1] burstcoin.jminer.CommandLineRunner       : -------------------------------------------------------
2016-01-13 21:03:40.409  INFO 3396 --- [    roundPool-1] burstcoin.jminer.CommandLineRunner       : START block '186037', scoopNumber '1575', capacity '26045 GB'
2016-01-13 21:03:40.409  INFO 3396 --- [    roundPool-1] burstcoin.jminer.CommandLineRunner       :       targetDeadline '60000', baseTarget '2319625'
2016-01-13 21:03:40.581  INFO 3396 --- [  networkPool-1] burstcoin.jminer.CommandLineRunner       :       winner block '186036', 'BURST-9EE4-BAXQ-876T-BQRWF'
2016-01-13 21:03:40.596  INFO 3396 --- [    roundPool-1] burstcoin.jminer.CommandLineRunner       : dl '312852067' > '60000' skipped
2016-01-13 21:03:40.628  INFO 3396 --- [    roundPool-1] burstcoin.jminer.CommandLineRunner       : dl '307882924' > '60000' skipped
2016-01-13 21:03:40.643  INFO 3396 --- [   readerPool-8] burstcoin.jminer.CommandLineRunner       : 1% done (0TB 2GB), eff.read '2 MB/s'
2016-01-13 21:03:40.659  INFO 3396 --- [    roundPool-1] burstcoin.jminer.CommandLineRunner       : dl '67612539' > '60000' skipped
2016-01-13 21:03:40.753  INFO 3396 --- [    roundPool-1] burstcoin.jminer.CommandLineRunner       : dl '15926967' > '60000' skipped
2016-01-13 21:03:41.268  INFO 3396 --- [    roundPool-1] burstcoin.jminer.CommandLineRunner       : dl '13600520' > '60000' skipped
2016-01-13 21:03:41.409  INFO 3396 --- [    roundPool-1] burstcoin.jminer.CommandLineRunner       : dl '4204180' > '60000' skipped
2016-01-13 21:03:41.581  INFO 3396 --- [    roundPool-1] burstcoin.jminer.CommandLineRunner       : dl '2783440' > '60000' skipped
2016-01-13 21:03:44.378  INFO 3396 --- [    roundPool-1] burstcoin.jminer.CommandLineRunner       : dl '1472035' > '60000' skipped
2016-01-13 21:03:46.300  INFO 3396 --- [    roundPool-1] burstcoin.jminer.CommandLineRunner       : dl '248815' > '60000' skipped
2016-01-13 21:03:46.893  INFO 3396 --- [   readerPool-6] burstcoin.jminer.CommandLineRunner       : 12% done (2TB 846GB), eff.read '111 MB/s'
2016-01-13 21:03:50.487  INFO 3396 --- [   readerPool-8] burstcoin.jminer.CommandLineRunner       : 23% done (5TB 668GB), eff.read '143 MB/s'
2016-01-13 21:03:53.971  INFO 3396 --- [   readerPool-2] burstcoin.jminer.CommandLineRunner       : 34% done (8TB 491GB), eff.read '159 MB/s'
2016-01-13 21:03:55.971  INFO 3396 --- [    roundPool-1] burstcoin.jminer.CommandLineRunner       : dl '121016' > '60000' skipped
2016-01-13 21:03:57.175  INFO 3396 --- [   readerPool-6] burstcoin.jminer.CommandLineRunner       : 45% done (11TB 312GB), eff.read '172 MB/s'
2016-01-13 21:04:00.237  INFO 3396 --- [   readerPool-4] burstcoin.jminer.CommandLineRunner       : 56% done (14TB 134GB), eff.read '182 MB/s'
2016-01-13 21:04:04.346  INFO 3396 --- [   readerPool-2] burstcoin.jminer.CommandLineRunner       : 67% done (16TB 980GB), eff.read '181 MB/s'
2016-01-13 21:04:08.034  INFO 3396 --- [   readerPool-5] burstcoin.jminer.CommandLineRunner       : 78% done (19TB 803GB), eff.read '183 MB/s'
2016-01-13 21:04:12.036  INFO 3396 --- [   readerPool-8] burstcoin.jminer.CommandLineRunner       : 89% done (22TB 625GB), eff.read '182 MB/s'
2016-01-13 21:04:20.135  INFO 3396 --- [   readerPool-6] burstcoin.jminer.CommandLineRunner       : 100% done (25TB 445GB), eff.read '163 MB/s'
2016-01-13 21:04:20.151  INFO 3396 --- [    roundPool-1] burstcoin.jminer.CommandLineRunner       : FINISH block '186037', best deadline 'N/A', round time '39s 789ms'

[luxe]

C:\Burst>java -version
java version "1.8.0_66"
Java(TM) SE Runtime Environment (build 1.8.0_66-b18)
Java HotSpot(TM) 64-Bit Server VM (build 25.66-b18, mixed mode)

C:\Burst>

It is now OK. Really sorry for this, I checked again and I DL-ed 64bit installer. Anyone should pay attention to what this java automatic installer is doing by own will.

First result is here : (looks really gooooood )

...

I'm glad we could solve that issue ... let it burst :-)

[Yanakitu Tenatako]

I am really sorry for bothering, but I am getting this error on every couple of hours:
I tried with memory options 6G 4G and without and still, it is the same.


Exception in thread "readerPool-156" java.lang.OutOfMemoryError: Java heap space
2016-01-14 08:09:25.908  WARN 4692 --- [  networkPool-2] b.j.c.n.t.NetworkRequestMiningInfoTask   : Unable to get mining info from wallet: null
Exception in thread "readerPool-183" 2016-01-14 08:09:50.236  WARN 4692 --- [  networkPool-2] b.j.c.n.t.NetworkRequestMiningInfoTask   : Unable to get mining info from wallet: null
Exception in thread "readerPool-185" Exception in thread "readerPool-182" 2016-01-14 08:10:06.064  INFO 4692 --- [    roundPool-2] burstcoin.jminer.CommandLineRunner       : dl '117665198' > '60000' skipped
java.lang.OutOfMemoryError: Java heap space2016-01-14 08:10:13.971  WARN 4692 --- [  networkPool-2] b.j.c.n.t.NetworkRequestMiningInfoTask   : Unable to get mining info from wallet: java.net.SocketTimeoutException: Connect Timeout

2016-01-14 08:10:29.721  WARN 4692 --- [  networkPool-2] b.j.c.n.t.NetworkRequestMiningInfoTask   : Unable to get mining info from wallet: null
2016-01-14 08:10:45.518  WARN 4692 --- [  networkPool-2] b.j.c.n.t.NetworkRequestMiningInfoTask   : Unable to get mining info from wallet: java.net.SocketTimeoutException: Connect Timeout
java.lang.OutOfMemoryError: Java heap space
java.lang.OutOfMemoryError: Java heap space
2016-01-14 08:11:09.236  WARN 4692 --- [  networkPool-2] b.j.c.n.t.NetworkRequestMiningInfoTask   : Unable to get mining info from wallet: java.net.SocketTimeoutException: Connect Timeout
2016-01-14 08:11:25.018  WARN 4692 --- [  networkPool-2] b.j.c.n.t.NetworkRequestMiningInfoTask   : Unable to get mining info from wallet: null
java.lang.OutOfMemoryError: Java heap space
java.lang.OutOfMemoryError: Java heap space
java.lang.OutOfMemoryError: Java heap space
java.lang.OutOfMemoryError: Java heap space
2016-01-14 08:11:32.877  WARN 4692 --- [  networkPool-2] b.j.c.n.t.NetworkRequestMiningInfoTask   : Unable to get mining info from wallet: null
java.lang.OutOfMemoryError: Java heap space
java.lang.OutOfMemoryError: Java heap space
2016-01-14 08:12:12.424  WARN 4692 --- [  networkPool-2] b.j.c.n.t.NetworkRequestMiningInfoTask   : Unable to get mining info from wallet: java.net.SocketTimeoutException: Connect Timeout
java.lang.OutOfMemoryError: Java heap space
java.lang.ArrayIndexOutOfBoundsException: -12016-01-14 08:12:28.205  WARN 4692 --- [  networkPool-2] b.j.c.n.t.NetworkRequestMiningInfoTask   : Unable to get mining info from wallet: null

        at sun.nio.ch.NativeThreadSet.remove(Unknown Source)
        at sun.nio.ch.FileChannelImpl.position(Unknown Source)2016-01-14 08:12:44.034  WARN 4692 --- [  networkPool-2] b.j.c.n.t.NetworkRequestMiningInfoTask   : Unable to get mining info from wallet: java.net.SocketTimeoutException: Connect Timeout

2016-01-14 08:13:07.737  WARN 4692 --- [  networkPool-2] b.j.c.n.t.NetworkRequestMiningInfoTask   : Unable to get mining info from wallet: null
        at sun.nio.ch.FileChannelImpl.position(Unknown Source)
        at burstcoin.jminer.core.reader.task.ReaderLoadDriveTask.load(ReaderLoadDriveTask.java:75)2016-01-14 08:13:23.549  WARN 4692 --- [  networkPool-2] b.j.c.n.t.NetworkRequestLastWinnerTask   : Error: Failed to 'getBlockchainStatus'

2016-01-14 08:13:23.581  INFO 4692 --- [  networkPool-2] b.j.c.n.t.NetworkRequestLastWinnerTask   :       last winner 'N/A', walletServer out of sync.
        at burstcoin.jminer.core.reader.task.ReaderLoadDriveTask.run(ReaderLoadDriveTask.java:59)
2016-01-14 08:13:55.569  WARN 4692 --- [  networkPool-2] b.j.c.n.t.NetworkRequestMiningInfoTask   : Unable to get mining info from wallet: null
        at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source)2016-01-14 08:14:19.334  WARN 4692 --- [  networkPool-2] b.j.c.n.t.NetworkRequestMiningInfoTask   : Unable to get mining info from wallet: null

        at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source)
        at java.lang.Thread.run(Unknown Source)
2016-01-14 08:14:35.418  WARN 4692 --- [  networkPool-2] b.j.c.n.t.NetworkRequestMiningInfoTask   : Unable to get mining info from wallet: java.net.SocketTimeoutException: Connect Timeout
java.lang.OutOfMemoryError: Java heap space
java.lang.OutOfMemoryError: Java heap space2016-01-14 08:14:51.916  WARN 4692 --- [  networkPool-2] b.j.c.n.t.NetworkRequestMiningInfoTask   : Unable to get mining info from wallet: null

java.lang.OutOfMemoryError: Java heap space2016-01-14 08:15:16.369  WARN 4692 --- [  networkPool-2] b.j.c.n.t.NetworkRequestLastWinnerTask   : Error: Failed to 'getBlockchainStatus'

[luxe]

I am really sorry for bothering, but I am getting this error on every couple of hours:
I tried with memory options 6G 4G and without and still, it is the same.


Exception in thread "readerPool-156" java.lang.OutOfMemoryError: Java heap space
2016-01-14 08:09:25.908  WARN 4692 --- [  networkPool-2] b.j.c.n.t.NetworkRequestMiningInfoTask   : Unable to get mining info from wallet: null
Exception in thread "readerPool-183" 2016-01-14 08:09:50.236  WARN 4692 --- [  networkPool-2] b.j.c.n.t.NetworkRequestMiningInfoTask   : Unable to get mining info from wallet: null
Exception in thread "readerPool-185" Exception in thread "readerPool-182" 2016-01-14 08:10:06.064  INFO 4692 --- [    roundPool-2] burstcoin.jminer.CommandLineRunner       : dl '117665198' > '60000' skipped
java.lang.OutOfMemoryError: Java heap space2016-01-14 08:10:13.971  WARN 4692 --- [  networkPool-2] b.j.c.n.t.NetworkRequestMiningInfoTask   : Unable to get mining info from wallet: java.net.SocketTimeoutException: Connect Timeout

2016-01-14 08:10:29.721  WARN 4692 --- [  networkPool-2] b.j.c.n.t.NetworkRequestMiningInfoTask   : Unable to get mining info from wallet: null
2016-01-14 08:10:45.518  WARN 4692 --- [  networkPool-2] b.j.c.n.t.NetworkRequestMiningInfoTask   : Unable to get mining info from wallet: java.net.SocketTimeoutException: Connect Timeout
java.lang.OutOfMemoryError: Java heap space
java.lang.OutOfMemoryError: Java heap space
2016-01-14 08:11:09.236  WARN 4692 --- [  networkPool-2] b.j.c.n.t.NetworkRequestMiningInfoTask   : Unable to get mining info from wallet: java.net.SocketTimeoutException: Connect Timeout
2016-01-14 08:11:25.018  WARN 4692 --- [  networkPool-2] b.j.c.n.t.NetworkRequestMiningInfoTask   : Unable to get mining info from wallet: null
java.lang.OutOfMemoryError: Java heap space
java.lang.OutOfMemoryError: Java heap space
java.lang.OutOfMemoryError: Java heap space
java.lang.OutOfMemoryError: Java heap space
2016-01-14 08:11:32.877  WARN 4692 --- [  networkPool-2] b.j.c.n.t.NetworkRequestMiningInfoTask   : Unable to get mining info from wallet: null
java.lang.OutOfMemoryError: Java heap space
java.lang.OutOfMemoryError: Java heap space
2016-01-14 08:12:12.424  WARN 4692 --- [  networkPool-2] b.j.c.n.t.NetworkRequestMiningInfoTask   : Unable to get mining info from wallet: java.net.SocketTimeoutException: Connect Timeout
java.lang.OutOfMemoryError: Java heap space
java.lang.ArrayIndexOutOfBoundsException: -12016-01-14 08:12:28.205  WARN 4692 --- [  networkPool-2] b.j.c.n.t.NetworkRequestMiningInfoTask   : Unable to get mining info from wallet: null

        at sun.nio.ch.NativeThreadSet.remove(Unknown Source)
        at sun.nio.ch.FileChannelImpl.position(Unknown Source)2016-01-14 08:12:44.034  WARN 4692 --- [  networkPool-2] b.j.c.n.t.NetworkRequestMiningInfoTask   : Unable to get mining info from wallet: java.net.SocketTimeoutException: Connect Timeout

2016-01-14 08:13:07.737  WARN 4692 --- [  networkPool-2] b.j.c.n.t.NetworkRequestMiningInfoTask   : Unable to get mining info from wallet: null
        at sun.nio.ch.FileChannelImpl.position(Unknown Source)
        at burstcoin.jminer.core.reader.task.ReaderLoadDriveTask.load(ReaderLoadDriveTask.java:75)2016-01-14 08:13:23.549  WARN 4692 --- [  networkPool-2] b.j.c.n.t.NetworkRequestLastWinnerTask   : Error: Failed to 'getBlockchainStatus'

2016-01-14 08:13:23.581  INFO 4692 --- [  networkPool-2] b.j.c.n.t.NetworkRequestLastWinnerTask   :       last winner 'N/A', walletServer out of sync.
        at burstcoin.jminer.core.reader.task.ReaderLoadDriveTask.run(ReaderLoadDriveTask.java:59)
2016-01-14 08:13:55.569  WARN 4692 --- [  networkPool-2] b.j.c.n.t.NetworkRequestMiningInfoTask   : Unable to get mining info from wallet: null
        at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source)2016-01-14 08:14:19.334  WARN 4692 --- [  networkPool-2] b.j.c.n.t.NetworkRequestMiningInfoTask   : Unable to get mining info from wallet: null

        at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source)
        at java.lang.Thread.run(Unknown Source)
2016-01-14 08:14:35.418  WARN 4692 --- [  networkPool-2] b.j.c.n.t.NetworkRequestMiningInfoTask   : Unable to get mining info from wallet: java.net.SocketTimeoutException: Connect Timeout
java.lang.OutOfMemoryError: Java heap space
java.lang.OutOfMemoryError: Java heap space2016-01-14 08:14:51.916  WARN 4692 --- [  networkPool-2] b.j.c.n.t.NetworkRequestMiningInfoTask   : Unable to get mining info from wallet: null

java.lang.OutOfMemoryError: Java heap space2016-01-14 08:15:16.369  WARN 4692 --- [  networkPool-2] b.j.c.n.t.NetworkRequestLastWinnerTask   : Error: Failed to 'getBlockchainStatus'

Damn, ok you seam to have some network issues there ... you could try to increase 'connectionTimeout' and 'refreshInterval' make sure your wallet is accessible.

Code:

refreshInterval=3000
connectionTimeout=12000

If that does not help, i need to know more about your setup ... all machines are accessing same wallet or every machine has it's own?
How big is your staggersize?
Please provide complete error logs ... if there was more ... i can not see if the connection problems are resulting from OutOfMemory or the other way round ...

[jorjito25]

Hi luxe,

Thanks for your work   Since some time, I get this error:

Error: ReaderPartLoadedEvent for unknown chunkPartStartNonce

No java error, just that on two boxes. And hundreds of them. No errors with blago's miner, but strange thing is that they seem to find the same number of dl. I do use large startnonces....

Any idea....? No hits on google.

[luxe]

Hi luxe,

Thanks for your work   Since some time, I get this error:

Error: ReaderPartLoadedEvent for unknown chunkPartStartNonce

No java error, just that on two boxes. And hundreds of them. No errors with blago's miner, but strange thing is that they seem to find the same number of dl. I do use large startnonces....

Any idea....? No hits on google.

This error does not effect your mining ... but indicates you have duplicate or overlapping plots.
Please check for plot-file duplicate or overlapping plots e.g. use https://bchain.info/BURST/tools/overlap

jminer uses a lookup with chunkPartStartNonce as unique key, to calculate how much capacity is left in a round.
Once a chunkPart is read it's removed from that lookup ... in your case it was already removed, means you have at least two times the same chunkPartStartNonce.

[jaggard]

Here's something that may help people on win 7 - Dyncache, a service to manage cache sizes. Something that m$ put out to implement similar cache management for it that they put in win 8+. https://www.microsoft.com/en-us/download/details.aspx?id=9258

[luxe]

Here's something that may help people on win 7 - Dyncache, a service to manage cache sizes. Something that m$ put out to implement similar cache management for it that they put in win 8+. https://www.microsoft.com/en-us/download/details.aspx?id=9258

Thanks for that hint jaggard!
I have no Win7 for testing, could someone confirm, that this works?
@equipoise, maybe this can fix your issues?