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

Burst is falling because Bitcoin dropped 10% in 2 hours and is now just $301~ USD per BTC.

This shit is fucked lol  We are either going to see the next Bitcoin mega pump forming over the next week or we are all gonna be cleaned out.

It's been a fun ride whatever happens! ;-)

People could we have a dedicated thread for mining related posts only? Investors and new people who want to buy coming to this thread and only see about mining. If nobody buy your coin then what's the point of mining ? We need to discuss more how to expand the coin, not focusing on mining only.

Just my 2 BURSTs,

Regards,

As one of people who's using Linux, and have no proper GFX card - found ploting always a bit slow...
On Windows wPlotGenerator by Cerr Janror worked very nicely, and for Linux there was dcct by Markus Tervooren.
(Original Java based ploter is just waaay to slow)

I've added wPlotGenerator improved code into dcct, so new dcct code is now faster.
Using SSE4 I'm getting 2x improvement in speed over stock dcct ploter.
Basically, it's speed you get from wPlotGenerator.
I was unable to test AVX2, as have no Haswell CPU to try it on.

Here's info how to make it:

git clone https://github.com/Mirkic7/mdcct.git
cd mdcct
make

It will make 'plot' binary which uses SSE4 code.
Also it will make 'plotavx2' which can use AVX2 code.
Reason for breaking them apart was that I had some issues with compiling AVX2 code (guess older gcc version problems).

Syntax is simple (basically same as dcct one with added '-x' option):
For SSE4 binary
Usage: ./plot -k KEY [ -x CORE ] [-d DIRECTORY] [-s STARTNONCE] [-n NONCES] [-m STAGGERSIZE] [-t THREADS]
 CORE:
   0 - default core
   1 - SSE4 core

For AVX2 binary
Usage: ./plotavx2 -k KEY [ -x CORE ] [-d DIRECTORY] [-s STARTNONCE] [-n NONCES] [-m STAGGERSIZE] [-t THREADS]
  CORE:
    0 - default core
    1 - SSE4 core
    2 - AVX2 core

Note: Using AVX2 on non-AVX2 CPU will core dump.

All credit goes to original dcct coder&wplotgenerator coder.

BURST donations are welcome : BURST-RQW7-3HNW-627D-3GAEV

It all seems good to me.
Maybe you can use a higher stagger size like 16384 as you have 8GB of memory for plotting. It'll reduce disk stress later for the mining process.

Most alt will go up when BTC goes up.

It's barely off the ground this thing - we have no cause for immediate concern on the price other than it pisses most of us off to see so many coins dumped with no buy support.

I have a feeling it will shoot up with BTC seeing as it has plummeted with BTC.

You guys know, it's actually a good thing that the guys with hundreds of tb's are dumping, because it helps with distribution, which is a really good thing.

[MINER]
Thank you guys for testing, working on a solution to the problems

[MEMORY]
I have three computers with Win7 x64, all parameters and EnablePrefetch EnableSuperPrefetch set to 0.
Theoretically, the system should not be left in memory to read the file for caching, but in practice it is not.
The system leaves the data in memory, but begins to actively unload when you start another process running with a disk and a large amount of data.
On this screenshot is running miner (big peaks) and dcct's merge tool, memory gradually released ... (RAM 16 G, plots: 10 Tb)


On this screenshot dcct's merge tool finalized (red), a miner is in idle (blue), was replaced by a block (green), and then came another new block (yellow) - the memory is consumed to the maximum limit is not being released.


I think this is the problem of the memory manager Win 7, on Win XP x64 this behavior was not observed.
Conclusion: there is nothing wrong, the system will clear the memory, if necessary, the rig I have not rebooted for a week.

[TIME]
At the expense of staggersize / plot size: especially is not affected by if the file merged.
Example:
17930413153828766298_22500000_800000_800000 [@ 3084 ms]
17930413153828766298_21700000_800000_800000 [@ 4373 ms]
17930413153828766298_26900000_800000_8000 [@ 25558 ms]
As can be seen, not merged files are read and processed several times longer.
CacheSize desirable value must be a multiple of the nonces file, since Miner reads CacheSize pieces of the file.

A sad truth.

it is not hard for those who owns hundreds of idle TB,  you will found several miners in thread who owns hundreds of TB  easily, even some guys reach 800TB+ ,the hdds are just idle for them, they can mine 10+ ,45+block a day, they can get free 0.5-1BTC a day with little electricity, that's a greate profit for them, if you mine BTC with asic, it may be take with months to mine a btc and cost a lot of electricity, of course it is not hard for them, difficulty is still too low for burst

Got a nice GPU? And it's called plotting, not piloting

PS. No need for big text, we can all see it

I just tried piloting.2 hours only 60GB pilot generated on g1830,painfully slow.When will it finish 1600GB,lol.Any faster way?

Whole lot better now, gives accurate data . Shows assets(which Uray's one doesn't....yet)

Look at all of the tards dumping. Great buying opportunity. I've sold some when the price was higher but I am back to holding.

Same here.  Issue persists.

"Setting your stagger size equal to 75% of your total memory (or up to the amount of memory you have,) is a decent default. I.E. if my computer has 8GB of RAM, I would set my stagger size to 8192.Setting your stagger size equal to 75% of your total memory (or up to the amount of memory you have,) is a decent default. I.E. if my computer has 8GB of RAM, I would set my stagger size to 8192."

huh?  8192 is 75% of 10,922, explain your math, please.

Many thanks for explanation.

I am generating plot with these parameters:
Machine is 4 x R9 280X (but only 2 are generating, no need for more because of HDD speed) + 8Gb ram.

devices.txt is :
0 0 8192 128 8192
0 1 8192 128 8192

command line parameters are:
gpuplotgenerator.exe generate "D:\plots" 30xxxxxxxxxxxxxxx778 10101000000000 2048000 8192
gpuplotgenerator.exe generate "D:\plots" 30xxxxxxxxxxxxxxx778 10101025000000 2048000 8192
gpuplotgenerator.exe generate "D:\plots" 30xxxxxxxxxxxxxxx778 10101050000000 2048000 8192
gpuplotgenerator.exe generate "D:\plots" 30xxxxxxxxxxxxxxx778 10101075000000 2048000 8192
gpuplotgenerator.exe generate "D:\plots" 30xxxxxxxxxxxxxxx778 10101100000000 2048000 8192
gpuplotgenerator.exe generate "D:\plots" 30xxxxxxxxxxxxxxx778 10101125000000 2048000 8192
gpuplotgenerator.exe generate "D:\plots" 30xxxxxxxxxxxxxxx778 10101150000000 2048000 8192
gpuplotgenerator.exe generate "D:\plots" 30xxxxxxxxxxxxxxx778 10101175000000 2048000 8192

It is 4Tb total per disk (range change for every hdd).


GpuPlotGenerator says:
-------------------------
GPU plot generator v3.0.0
-------------------------
Author:   Cryo
Bitcoin:  138gMBhCrNkbaiTCmUhP9HLU9xwn5QKZgD
Burst:    BURST-YA29-QCEW-QXC3-BKXDL
----
Checking input parameters...
----
Path: D:\plots
Nonces: 10101050000000 to 10101052047999 (500GB 0MB)
CPU memory: 2GB 0MB
----
Initializing OpenCL devices...
GPU[0] memory: 2GB 0MB
GPU[1] memory: 2GB 0MB
----
Creating CPU stagger buffer...
Creating CPU plots buffer...
Opening output file...



------------------------------------------------------------------------------------------------------------------------------------

Dedicated mining machine will be 8 or 16 Gb ram, 8 hdd (32Tb total).

Is there something I should change before plotting all drives, considering equipment and ram size?


That would be it, final step before mining, after this I should only wait to be done and start mining.
Will not bother more

Sleep deprivation. I went on an all night attack at C-CEX until I got my coins back. I was mistaken the source address of the depositor for my own. Like I said: I'm a fucking idiot!

So, what was it? Were you typing in the wrong password, or was it the caching issue?

Here is the problem with your explanation....

I have been logged in for the past 72 hours straight. I copy and paste the password. It was coming into the old address. And then it just changed. My numeric one is still the same. There have been 3 different alpha-numeric ones. I'll PM you a screen shot. You can verify my numeric one on your pool.

This is freaking me out DEV!

Never mind. I'm a fucking idiot!