Topic: [ANN][BURST] Burst | Efficient HDD Mining | New 1.2.3 Fork block 92000 - page 1061. (Read 2170889 times)

Ware ?

Yea I'm not really sure - I'm far from an expert.  I ended up putting Ubuntu on an old SSD and used dcct's plot tool (link's in here somewhere) which is twice as fast and runs at an 8191 stagger, no problem.  I did a couple smaller drives on Windows and just used 1000, 1000 because that's what I got to work first.

Try a stagger size of 2048 and Xmx at 1024.

A ratio of 2/1 with stagger size/Xmx ratio works best for me.

it works fine at 1400 i dont understand why i cant go higher i get the VM error, i have 8gb of ram.... that particular error happens when i put the stagger above 3500

is it just different for everyones pc... find the max of both and thats what ill need to use?

Burst is only a month old, give it time to grow  . And don't worry ,  stay tuned....

I forget which error that is, either Xmx too high or stagger too high.  I ended up with 1000 for each and ran fine.

F:\pocminer_v1>C:\Windows\SysWOW64\java -Xmx1400m -cp pocminer.jar;lib/*;lib/akk
a/*;lib/jetty/* pocminer.POCMiner generate  14062819640288676663 1 80000 4191 3

Uncaught error from thread [default-akka.actor.default-dispatcher-4] shutting do
wn JVM since 'akka.jvm-exit-on-fatal-error' is enabled for ActorSystem[default]
java.lang.OutOfMemoryError: Java heap space
        at pocminer.GenerateSupr.init(GenerateSupr.java:61)
        at pocminer.GenerateSupr.preStart(GenerateSupr.java:55)
        at akka.actor.Actor$class.aroundPreStart(Actor.scala:470)
        at akka.actor.UntypedActor.aroundPreStart(UntypedActor.scala:97)
        at akka.actor.ActorCell.create(ActorCell.scala:580)
        at akka.actor.ActorCell.invokeAll$1(ActorCell.scala:456)
        at akka.actor.ActorCell.systemInvoke(ActorCell.scala:478)
        at akka.dispatch.Mailbox.processAllSystemMessages(Mailbox.scala:263)
        at akka.dispatch.Mailbox.run(Mailbox.scala:219)
        at akka.dispatch.ForkJoinExecutorConfigurator$AkkaForkJoinTask.exec(Abst
ractDispatcher.scala:393)
        at scala.concurrent.forkjoin.ForkJoinTask.doExec(ForkJoinTask.java:260)
        at scala.concurrent.forkjoin.ForkJoinPool$WorkQueue.runTask(ForkJoinPool
.java:1339)
        at scala.concurrent.forkjoin.ForkJoinPool.runWorker(ForkJoinPool.java:19
79)
        at scala.concurrent.forkjoin.ForkJoinWorkerThread.run(ForkJoinWorkerThre
ad.java:107)

F:\pocminer_v1>pause
Press any key to continue . . .



i get that when i change the stagger size

Hi everyone,

After many hours of setup I finally made it. I have a 1Tb generation in progress and 3x100Gb already finished.
I would like to test the V2 pool but I haven't any BURST for now. Could someone send me 1 BURST to test it please ? Here is my address : BURST-YA29-QCEW-QXC3-BKXDL.

Regarding the plot generation, I found an OpenCL implementation of Shabal (https://github.com/aznboy84/X15GPU/blob/master/kernel/shabal.cl) that could be used to make a GPU version of the generator. I will try to work on it when I have some free time.

Regards

AHAHAH 1M coin dump, stupid guy !!!

I have noticed a big performance jump going from stagger size of 2048 to 8191. It takes much less time to parse the files.  I am using 16 threads (dual xeons with hyper threading) with Xmx set to 4000 and java will consume about 5.2GB of memory during the plot generation process

seems anything higher than 1000 for the ram will get the VM error, do you have to set it to a odd number or something?

For me Its possible we have 600 clone of the Burst, so Burst = Bitcoin

indeed my friend, indeed.

Merci is better

You can try a higher -Xmx number and higher stagger size until it gives a error, then lower it until it works fine. Maybe -Xmx and stagger size at 4191 or 2048.

If you plan to not use the PC for any intensive cpu applications, the 4 threads are fine. If it's your PC to do work or anything else, 3 threads would work better.

Mercy!

The stagger of 1000 will mean that it will take longer to scan the file for the correct nonce. You should increase that. I suggest you use 8000

Once this reaches NXT price, then people have to be on guard at that point and up, but never know depending on several factors.


Yup, have to see when this hit a larger exchange. I would prefer someone that is doing NXT already, ie. Cryptsy, BTER, Poloniex, BTC38, etc....

so i have a i5 quad core with 8gb ram


C:\Windows\SysWOW64\java -Xmx1000m -cp pocminer.jar;lib/*;lib/akka/*;lib/jetty/* pocminer.POCMiner generate %* 14062819640288676663 1 80000 1000 2
pause


is this optimal for plot generation? im doing other things so using 4 threads hits my cpu at 100%.. it doesnt look like its using much ram at all though and its moving really slow

This is a HDD mining coin. No GPU/CPU. Read the OP