[ANN][BURST] Burst | Efficient HDD Mining | New 1.2.3 Fork block 92000 - page 786.

enta2k

full member

Activity: 294

Merit: 101

The Future of Security Tokens

Hey pinnballdude thats really very usefull, i will do it like that.
Damn that makes me sad, i thought after 2 weeks of trying around now everything is fine.
I was able to plott the whole 5,4tb file in 15h, now it takes a week or i have to find a gpu plotter version that works correctly.
Didn´t knew, that it could be so bad.

I have one more question, so for example i go start plot 0 and add plots 1000 like this

-Xmx2000m -cp pocminer.jar;lib/*;lib/akka/*;lib/jetty/* pocminer.POCMiner generate blabla 0 1000 4000 4 the next cmd would be
-Xmx2000m -cp pocminer.jar;lib/*;lib/akka/*;lib/jetty/* pocminer.POCMiner generate blabla 1000 1000 4000 4 i don´t have to go 1001 + 1000, because i read that in this thread
and it made it impossible to plot even files, because it couldn´t be evenly divided.

Thats why i startet to plot 1 big file with gpu.

Hard and very time intensive learning process Cheesy

pinballdude

sr. member

Activity: 286

Merit: 250

Quote from: enta2k on September 17, 2014, 04:54:21 PM

Quote from: pinballdude on September 17, 2014, 04:19:26 PM

Quote from: enta2k on September 17, 2014, 03:46:31 PM

can someone give me an example of a "too long deadline"?
I really dont know if mine are long or not Cheesy

This is of course when doing solo
The system is set up to to average 4 minute blocks, so 240 seconds should be average. That means that half the time a 240 second deadline will win a block, and half the time it is too large. at 120 seconds it might be 1/4 risk you don't get a block, and at 60 it might be 1/8 risk someone is faster, etc. etc. conversely at 480 you will only win a block 1/4 of the time, at 960 only 1/8 of the time... i think.. not sure these calculations work out, but it ought to be something like that. i had one at 180 that did not win a block, and one at 114 that did win a block. Patience is pretty vital, I had to wait almost a week before i got a block, and i was cpu plotting like crazy on 3 pcs, 14 cores, 24/7 towards 4TB, so on average i must have had somewhat over 1TB plottable

Okay i have to say i don´t get it, you mean your system is giving you a result every 4 Minutes average?
Isn´t the average time set by the amount of space you are using?
I mined solo some time too and sometimes theres a result after 3 seconds and sometimes it takes ages.
Can you post a screenshot of what you mean, because i think i missunderstand it.

The thing is i plottet 6GB gpu and everyone says it´s worse than cpu plots,
i really would like to see if my average whatever time is good or bad.

It works this way - everyone mining at all finds a deadline in their plot files... the larger plot file, the more tickets they have in the plotfiles, so the better the chance of having a ticket with a really low number. (ticket is a seed that gets converted to a number, using data from the network, so basically the resulting deadline is your lucky number, which you cannot fake, and anyone else can easily verify). So every miner has a best deadline, and the very very best deadline is the time it takes before a block is generated. The miners simply wait as many seconds as is their best deadline, and if the block is still not created, they do it.

The numbers and difficulty and stuff is arranged such that on average someone will have a deadline around 240 seconds. If we stray away from that, the entire systen recalibrates. Still, someone might be lucky and get a real real low deadline, then a block is solved very very fast, and the next time perhaps everyne is quite with bad luck, and the smallest deadline anywhere is like 800 and we have to wait and wait until the 800 seconds passes and the lucky dude with a 800 deadline gets his block.

so the amount of space you have plotted will get you smaller deadlines with more space - simply because you have more random number tickets to begin with (more random numbers, more of them will randomly tend to be smallish) a block can be solved instantly by anyone, but the network lets whoever do it, who can prove he has the code for the lowest deadline, and these codes we have in our plot files.

I don't know all this in enough detail to really be certain about how stuff works, but above is how i think it sort of works.

SpeedDemon13

hero member

Activity: 518

Merit: 500

Quote from: enta2k on September 17, 2014, 05:51:05 PM

i used the 2.0.1 mod with 14.5 drivers

Maybe it was the modded version that caused the issue.

AMD 14.5 would work ok on GPU plotter 2.1.1. Just redo the plots again.

pinballdude

sr. member

Activity: 286

Merit: 250

Quote from: enta2k on September 17, 2014, 05:26:39 PM

My plot file is 5,4TB and i plotted everything with gpu.
If this is causing a like 10mb performance, i really hope there will be a fix for the gpu plotter soon,
because, it takes almost a week to plot with cpu Sad

You are the dude, if you say thats a very bad performance, i really should plot again with cpu,
as hard as it is, better plott forever than having like zero performance.

I usually create a batch file with many calls to the generator, each generating like 128GB or some such. In that way, a bad file is not so much data, and i can just delete it and recreate. If You did that, you could cpu plot until a gpu plotter that works for you get along, and you could even plot with exactly the same specifications and probably compare the two files, or the results coming out of them, to verify the gpu plotter is working for you as it should.

right now i'm plotting a USB 1TB drive i found somewhere and it is done this way :

Code:

title  Drive:L 30000000 to 30500000
"%PROGRAMFILES%\Java\jre7\bin\java.exe" -Xmx2000m -cp pocminer.jar;lib/*;lib/akka/*;lib/jetty/* pocminer.POCMiner generate  blabla 30000000 500000 4000 4

title  Drive:L 30500000 to 31000000
"%PROGRAMFILES%\Java\jre7\bin\java.exe" -Xmx2000m -cp pocminer.jar;lib/*;lib/akka/*;lib/jetty/* pocminer.POCMiner generate  blabla 30500000 500000 4000 4

title  Drive:L 31000000 to 31500000
"%PROGRAMFILES%\Java\jre7\bin\java.exe" -Xmx2000m -cp pocminer.jar;lib/*;lib/akka/*;lib/jetty/* pocminer.POCMiner generate  blabla 31000000 500000 4000 4

title  Drive:L 31500000 to 32000000
"%PROGRAMFILES%\Java\jre7\bin\java.exe" -Xmx2000m -cp pocminer.jar;lib/*;lib/akka/*;lib/jetty/* pocminer.POCMiner generate  blabla 31500000 500000 4000 4

title  Drive:L 32000000 to 32500000
"%PROGRAMFILES%\Java\jre7\bin\java.exe" -Xmx2000m -cp pocminer.jar;lib/*;lib/akka/*;lib/jetty/* pocminer.POCMiner generate  blabla 32000000 500000 4000 4

title  Drive:L 32500000 to 33000000
"%PROGRAMFILES%\Java\jre7\bin\java.exe" -Xmx2000m -cp pocminer.jar;lib/*;lib/akka/*;lib/jetty/* pocminer.POCMiner generate  blabla 32500000 500000 4000 4

title  Drive:L 33000000 to 33500000
"%PROGRAMFILES%\Java\jre7\bin\java.exe" -Xmx2000m -cp pocminer.jar;lib/*;lib/akka/*;lib/jetty/* pocminer.POCMiner generate  blabla 33000000 500000 4000 4

title  Drive:L 33500000 to 34000000
"%PROGRAMFILES%\Java\jre7\bin\java.exe" -Xmx1200m -cp pocminer.jar;lib/*;lib/akka/*;lib/jetty/* pocminer.POCMiner generate  blabla 33500000 500000 4000 4

title  Drive:L 34000000 to 34500000
"%PROGRAMFILES%\Java\jre7\bin\java.exe" -Xmx1200m -cp pocminer.jar;lib/*;lib/akka/*;lib/jetty/* pocminer.POCMiner generate  blabla 34000000 500000 4000 4

title  Drive:L 34500000 to 35000000
"%PROGRAMFILES%\Java\jre7\bin\java.exe" -Xmx1200m -cp pocminer.jar;lib/*;lib/akka/*;lib/jetty/* pocminer.POCMiner generate  blabla 34500000 500000 4000 4

means that the window always have a title what it's doing, and also means that the files show up on automatic as the script gets finished with the files.
I mine them while they are being created, that works perfectly fine

If the pc is sloggy bc of the CPU plotting, try to lower the priority of the java process that is doing your plotting to below average, that way other stuff gets preference. You can also select a number of cores that is less that what you have, to save some for other programs. I use 4 of 8 cores atm. and that's not really slowing anything down at all, but the process is also set with below average.

I should probably have gone GPU plotting, but my GPUs were already mining skynet and indocoin, and no reason to interfere with that ;-)

enta2k

full member

Activity: 294

Merit: 101

The Future of Security Tokens

i used the 2.0.1 mod with 14.5 drivers

Maybe it was the modded version that caused the issue.

SpeedDemon13

hero member

Activity: 518

Merit: 500

Quote from: enta2k on September 17, 2014, 05:26:39 PM

My plot file is 5,4TB and i plotted everything with gpu.
If this is causing a like 10mb performance, i really hope there will be a fix for the gpu plotter soon,
because, it takes almost a week to plot with cpu Sad

You are the dude, if you say thats a very bad performance, i really should plot again with cpu,
as hard as it is, better plott forever than having like zero performance.

What gpu and driver did you use? The latest gpu plotter and AMD 14.x drivers plot fine, but older gpu plotters with AMD 14.x driver can produce incorrect plot data. If your using an older gpu plotter, then use the AMD 13.x drivers.

enta2k

full member

Activity: 294

Merit: 101

The Future of Security Tokens

Quote from: pinballdude on September 17, 2014, 05:41:26 PM

Quote from: enta2k on September 17, 2014, 05:20:02 PM

lol, for example my last dadline is 707506293144
Does this tell me, that my plot file is fucked?

either that, or that the plot file has very very few nounces in it, and is super small. I've had very small plot files under generation generate crazy deadlines, but deadlines improve a lot as the file grow in size, something like perhaps the best seen deadline over some period gets half as big, with double the filesize (or something like that)

my pc with 3TB plots right now has a minimum deadline of 4721 over the last 6 hours of mining, so it's not super easy to hit the small ones.

btw. it would be overly super cool if the java wallet server could be set up to add to a file the best deadline seen for every block one is mining. Such a log would be fun to have. The current log has to be set to log *A LOT* of stuff before the wallet starts logging deadline numbers.

Haven´t seen a deadline smaller than 1 billion since i plottet my file with gpu.
Looks right gpu plotter is really really shitty and now i can start all over Sad

pinballdude

sr. member

Activity: 286

Merit: 250

Quote from: enta2k on September 17, 2014, 05:20:02 PM

lol, for example my last dadline is 707506293144
Does this tell me, that my plot file is fucked?

either that, or that the plot file has very very few nounces in it, and is super small. I've had very small plot files under generation generate crazy deadlines, but deadlines improve a lot as the file grow in size, something like perhaps the best seen deadline over some period gets half as big, with double the filesize (or something like that)

my pc with 3TB plots right now has a minimum deadline of 4721 over the last 6 hours of mining, so it's not super easy to hit the small ones.

btw. it would be overly super cool if the java wallet server could be set up to add to a file the best deadline seen for every block one is mining. Such a log would be fun to have. The current log has to be set to log *A LOT* of stuff before the wallet starts logging deadline numbers.

enta2k

full member

Activity: 294

Merit: 101

The Future of Security Tokens

My plot file is 5,4TB and i plotted everything with gpu.
If this is causing a like 10mb performance, i really hope there will be a fix for the gpu plotter soon,
because, it takes almost a week to plot with cpu Sad

You are the dude, if you say thats a very bad performance, i really should plot again with cpu,
as hard as it is, better plott forever than having like zero performance.

burstcoin

sr. member

Activity: 280

Merit: 250

Quote from: enta2k on September 17, 2014, 05:20:02 PM

lol, for example my last dadline is 707506293144
Does this tell me, that my plot file is fucked?

I'd say so. I don't know how much space your using, but on 2TB you'll almost always stay under 2mill at the current difficulty. Billions or higher is bad unless you have like a 10MB plot file.

enta2k

full member

Activity: 294

Merit: 101

The Future of Security Tokens

lol, for example my last dadline is 707506293144
Does this tell me, that my plot file is fucked?

sickfancy

full member

Activity: 153

Merit: 100

Quote from: dcct on September 16, 2014, 10:00:55 AM

Quote from: koko2530 on September 16, 2014, 09:57:10 AM

how to solo on 3 computer?
can run wallet on computer A and run pocminer on computer B ,C ?

thanks

Sure you can. Probably you want a miner on Computer A, too.

Just add computer B and C to nxt.allowedBotHosts= in your config.

I'd like to try this when but not sure I understand. I have 2 computers A and B each running wallet and mining. I want to run wallet only on computer A. To do this, I only need to add B to nxt.allowedBotHost= in computer A config? I don't have to do anything to computer B?

SpeedDemon13

hero member

Activity: 518

Merit: 500

Quote from: enta2k on September 17, 2014, 04:54:21 PM

Quote from: pinballdude on September 17, 2014, 04:19:26 PM

Quote from: enta2k on September 17, 2014, 03:46:31 PM

can someone give me an example of a "too long deadline"?
I really dont know if mine are long or not Cheesy

This is of course when doing solo
The system is set up to to average 4 minute blocks, so 240 seconds should be average. That means that half the time a 240 second deadline will win a block, and half the time it is too large. at 120 seconds it might be 1/4 risk you don't get a block, and at 60 it might be 1/8 risk someone is faster, etc. etc. conversely at 480 you will only win a block 1/4 of the time, at 960 only 1/8 of the time... i think.. not sure these calculations work out, but it ought to be something like that. i had one at 180 that did not win a block, and one at 114 that did win a block. Patience is pretty vital, I had to wait almost a week before i got a block, and i was cpu plotting like crazy on 3 pcs, 14 cores, 24/7 towards 4TB, so on average i must have had somewhat over 1TB plottable

Okay i have to say i don´t get it, you mean your system is giving you a result every 4 Minutes average?
Isn´t the average time set by the amount of space you are using?
I mined solo some time too and sometimes theres a result after 3 seconds and sometimes it takes ages.
Can you post a screenshot of what you mean, because i think i missunderstand it.

The thing is i plottet 6GB gpu and everyone says it´s worse than cpu plots,
i really would like to see if my average whatever time is good or bad.

Double digit millions or larger is a really bad deadline.

enta2k

full member

Activity: 294

Merit: 101

The Future of Security Tokens

Quote from: pinballdude on September 17, 2014, 04:19:26 PM

Quote from: enta2k on September 17, 2014, 03:46:31 PM

can someone give me an example of a "too long deadline"?
I really dont know if mine are long or not Cheesy

This is of course when doing solo
The system is set up to to average 4 minute blocks, so 240 seconds should be average. That means that half the time a 240 second deadline will win a block, and half the time it is too large. at 120 seconds it might be 1/4 risk you don't get a block, and at 60 it might be 1/8 risk someone is faster, etc. etc. conversely at 480 you will only win a block 1/4 of the time, at 960 only 1/8 of the time... i think.. not sure these calculations work out, but it ought to be something like that. i had one at 180 that did not win a block, and one at 114 that did win a block. Patience is pretty vital, I had to wait almost a week before i got a block, and i was cpu plotting like crazy on 3 pcs, 14 cores, 24/7 towards 4TB, so on average i must have had somewhat over 1TB plottable

Okay i have to say i don´t get it, you mean your system is giving you a result every 4 Minutes average?
Isn´t the average time set by the amount of space you are using?
I mined solo some time too and sometimes theres a result after 3 seconds and sometimes it takes ages.
Can you post a screenshot of what you mean, because i think i missunderstand it.

The thing is i plottet 6GB gpu and everyone says it´s worse than cpu plots,
i really would like to see if my average whatever time is good or bad.

Dzus1k

member

Activity: 74

Merit: 10

Any dice casino already ?

dcct

sr. member

Activity: 280

Merit: 250

Quote from: daWallet on September 17, 2014, 04:24:54 PM

@dcct

https://bitcointalk.org/index.php?topic=731923.msg8738422;topicseen#msg8738422

Thank you

daWallet

sr. member

Activity: 302

Merit: 250

@dcct

https://bitcointalk.org/index.php?topic=731923.msg8738422;topicseen#msg8738422

you're welcome

dcct

sr. member

Activity: 280

Merit: 250

There has been a version of my miner for uray's pool. Anyone has a link at hand? Cant find it.

pinballdude

sr. member

Activity: 286

Merit: 250

Quote from: enta2k on September 17, 2014, 03:46:31 PM

can someone give me an example of a "too long deadline"?
I really dont know if mine are long or not Cheesy

This is of course when doing solo
The system is set up to to average 4 minute blocks, so 240 seconds should be average. That means that half the time a 240 second deadline will win a block, and half the time it is too large. at 120 seconds it might be 1/4 risk you don't get a block, and at 60 it might be 1/8 risk someone is faster, etc. etc. conversely at 480 you will only win a block 1/4 of the time, at 960 only 1/8 of the time... i think.. not sure these calculations work out, but it ought to be something like that. i had one at 180 that did not win a block, and one at 114 that did win a block. Patience is pretty vital, I had to wait almost a week before i got a block, and i was cpu plotting like crazy on 3 pcs, 14 cores, 24/7 towards 4TB, so on average i must have had somewhat over 1TB plottable

fivebells

sr. member

Activity: 462

Merit: 250

Quote from: dcct on September 17, 2014, 03:21:23 PM

Hold on for a few hours, new version is almost ready. Just needs some final testing.

It's OK, I just changed the code.

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