Author

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

legendary
Activity: 3248
Merit: 1070
Why does everyone keep talking about GPUs? I thought this was a hard drive capacity-"mined" coin? Huh

correct - the mining process is scraping over your plot files.
The amount of storage devoted for plot files is equal to your chances of finding a block.
It also defines the amount of CPU power you need to scrape, because you need to read 1/4096 of your plotted volume. In most cases this is not important and can easily run on a single core, in the background, not hurting other processes running.

The actual "plotting" involves a CPU-intensive process and may take a day for a Terabyte. The i7-3930K I used for plotting yielded 2 TB/day. Lots of people buy a couple 4TB disks and don't want to wait 2 weeks to plot them, hence the development of a gnu-plotter.




Its the same problem. I am buying 1000 TB and it will take weeks to plot. Having only CPU i will not think of getting 1000 TB. GPU only make people scale up and everything end up the same but people have to spend more money.

1000 tb are you serious?

That is only 250 4TB drives. Ok 275 4 TB Drives after microdick finishes messing with them.

lol "only", you need multiple rig for that, and you can't dump the amount produced by that, not worth it

right now even 100tb are not worth it
legendary
Activity: 1582
Merit: 1019
011110000110110101110010
Why does everyone keep talking about GPUs? I thought this was a hard drive capacity-"mined" coin? Huh

correct - the mining process is scraping over your plot files.
The amount of storage devoted for plot files is equal to your chances of finding a block.
It also defines the amount of CPU power you need to scrape, because you need to read 1/4096 of your plotted volume. In most cases this is not important and can easily run on a single core, in the background, not hurting other processes running.

The actual "plotting" involves a CPU-intensive process and may take a day for a Terabyte. The i7-3930K I used for plotting yielded 2 TB/day. Lots of people buy a couple 4TB disks and don't want to wait 2 weeks to plot them, hence the development of a gnu-plotter.




Its the same problem. I am buying 1000 TB and it will take weeks to plot. Having only CPU i will not think of getting 1000 TB. GPU only make people scale up and everything end up the same but people have to spend more money.

1000 tb are you serious?

That is only 250 4TB drives. Ok 275 4 TB Drives after microdick finishes messing with them.

Yes i know but time to plot them risk to take a while, unless plotting on multiple computer

Well yeah it would be multiple computers. Also the GPU plot generator has to be there. It takes time but this coin is something that anyone can scale up just by reinvesting the coin. Hopefully this is a winner winner chicken dinner!
legendary
Activity: 1582
Merit: 1019
011110000110110101110010
The dev's 2.0 Pool is not updating. 2 shares submited and recieved in last 20 minutes - neither recorded.

My BURST has not changed in a while but my share count is changing. It goes up and then it goes down. Shares are not something that I understand yet. When the share count goes down where did they go?

I just got paid.
hero member
Activity: 1036
Merit: 531
Why does everyone keep talking about GPUs? I thought this was a hard drive capacity-"mined" coin? Huh

correct - the mining process is scraping over your plot files.
The amount of storage devoted for plot files is equal to your chances of finding a block.
It also defines the amount of CPU power you need to scrape, because you need to read 1/4096 of your plotted volume. In most cases this is not important and can easily run on a single core, in the background, not hurting other processes running.

The actual "plotting" involves a CPU-intensive process and may take a day for a Terabyte. The i7-3930K I used for plotting yielded 2 TB/day. Lots of people buy a couple 4TB disks and don't want to wait 2 weeks to plot them, hence the development of a gnu-plotter.




Its the same problem. I am buying 1000 TB and it will take weeks to plot. Having only CPU i will not think of getting 1000 TB. GPU only make people scale up and everything end up the same but people have to spend more money.

1000 tb are you serious?

That is only 250 4TB drives. Ok 275 4 TB Drives after microdick finishes messing with them.

Yes i know but time to plot them risk to take a while, unless plotting on multiple computer
legendary
Activity: 1582
Merit: 1019
011110000110110101110010
Why does everyone keep talking about GPUs? I thought this was a hard drive capacity-"mined" coin? Huh

correct - the mining process is scraping over your plot files.
The amount of storage devoted for plot files is equal to your chances of finding a block.
It also defines the amount of CPU power you need to scrape, because you need to read 1/4096 of your plotted volume. In most cases this is not important and can easily run on a single core, in the background, not hurting other processes running.

The actual "plotting" involves a CPU-intensive process and may take a day for a Terabyte. The i7-3930K I used for plotting yielded 2 TB/day. Lots of people buy a couple 4TB disks and don't want to wait 2 weeks to plot them, hence the development of a gnu-plotter.




Its the same problem. I am buying 1000 TB and it will take weeks to plot. Having only CPU i will not think of getting 1000 TB. GPU only make people scale up and everything end up the same but people have to spend more money.

1000 tb are you serious?

That is only 250 4TB drives. Ok 275 4 TB Drives after microdick finishes messing with them.
hero member
Activity: 1036
Merit: 531
Why does everyone keep talking about GPUs? I thought this was a hard drive capacity-"mined" coin? Huh

correct - the mining process is scraping over your plot files.
The amount of storage devoted for plot files is equal to your chances of finding a block.
It also defines the amount of CPU power you need to scrape, because you need to read 1/4096 of your plotted volume. In most cases this is not important and can easily run on a single core, in the background, not hurting other processes running.

The actual "plotting" involves a CPU-intensive process and may take a day for a Terabyte. The i7-3930K I used for plotting yielded 2 TB/day. Lots of people buy a couple 4TB disks and don't want to wait 2 weeks to plot them, hence the development of a gnu-plotter.




Its the same problem. I am buying 1000 TB and it will take weeks to plot. Having only CPU i will not think of getting 1000 TB. GPU only make people scale up and everything end up the same but people have to spend more money.

1000 tb are you serious?
hero member
Activity: 1400
Merit: 505
New client Update 1.1.0

Backend is caught up to date with nxt 1.2.8.
Nxt new APIs are usable.
Hard fork on block 11800 to enable new nxt features(encrypted messaging, DGS).
UI is not yet updated for new features.

Move your burst_db folder from 1.0.3 into the new folder to avoid a resync. Db upgrade will take a few minutes though.

https://mega.co.nz/#!3xZ2DIwR!QQnamRK_JCz-QvFwb_A9gS6_tWCxAiFtVoqI8Unqlhg
sha256: f9d2a2d199993088eb9a03f1cb282ecbb36e704a4b7c609d5e878573752dad30

Good work Smiley

It needs work. Transactions are backasswards.

yeah its not recent row first
legendary
Activity: 1582
Merit: 1019
011110000110110101110010
The dev's 2.0 Pool is not updating. 2 shares submited and recieved in last 20 minutes - neither recorded.

My BURST has not changed in a while but my share count is changing. It goes up and then it goes down. Shares are not something that I understand yet. When the share count goes down where did they go?
legendary
Activity: 1582
Merit: 1019
011110000110110101110010
New client Update 1.1.0

Backend is caught up to date with nxt 1.2.8.
Nxt new APIs are usable.
Hard fork on block 11800 to enable new nxt features(encrypted messaging, DGS).
UI is not yet updated for new features.

Move your burst_db folder from 1.0.3 into the new folder to avoid a resync. Db upgrade will take a few minutes though.

https://mega.co.nz/#!3xZ2DIwR!QQnamRK_JCz-QvFwb_A9gS6_tWCxAiFtVoqI8Unqlhg
sha256: f9d2a2d199993088eb9a03f1cb282ecbb36e704a4b7c609d5e878573752dad30

Good work Smiley

It needs work. Transactions are backasswards.
hero member
Activity: 620
Merit: 500
X:\burst2\burst-pool-miner>gpuPlotGenerator.exe 10364770829529893068 0 10000 16
GPU plot generator v1.0.0
Author: Cryo
Bitcoin: 138gMBhCrNkbaiTCmUhP9HLU9xwn5QKZgD
Burst: BURST-YA29-QCEW-QXC3-BKXDL
--------------
Creating plots for nonces 0 to 10000 (2 GB) using 4 MB memory
Retrieving OpenCL platform
Retrieving OpenCL GPU device
Creating OpenCL context
Creating OpenCL command queue
Creating CPU buffer
Creating OpenCL GPU buffer
Creating OpenCL program
Building OpenCL program
"C:\Users\hoop\AppData\Local\Temp\OCL2292.tmp.cl", line 71: warning: shift
          count is too large
                (p_buffer[p_offset + 4] << 32) |
                                           ^

"C:\Users\hoop\AppData\Local\Temp\OCL2292.tmp.cl", line 72: warning: shift
          count is too large
                (p_buffer[p_offset + 5] << 40) |
                                           ^

"C:\Users\hoop\AppData\Local\Temp\OCL2292.tmp.cl", line 73: warning: shift
          count is too large
                (p_buffer[p_offset + 6] << 48) |
                                           ^

"C:\Users\hoop\AppData\Local\Temp\OCL2292.tmp.cl", line 74: warning: shift
          count is too large
                (p_buffer[p_offset + 7] << 56);
                                           ^

"C:\Users\hoop\AppData\Local\Temp\OCL2292.tmp.cl", line 90: warning: shift
          count is too large
                (p_buffer[p_offset] << 56) |
                                       ^

"C:\Users\hoop\AppData\Local\Temp\OCL2292.tmp.cl", line 91: warning: shift
          count is too large
                (p_buffer[p_offset + 1] << 48) |
                                           ^

"C:\Users\hoop\AppData\Local\Temp\OCL2292.tmp.cl", line 92: warning: shift
          count is too large
                (p_buffer[p_offset + 2] << 40) |
                                           ^

"C:\Users\hoop\AppData\Local\Temp\OCL2292.tmp.cl", line 93: warning: shift
          count is too large
                (p_buffer[p_offset + 3] << 32) |
                                           ^

Error:E013:Insufficient Private Resources!

An error occured in the generation process, aborting...
>>> Unable to build the OpenCL program

windows 7 64bit radeon 280x driver 13.9
gpuPlotGenerator only work 32 bit system ?

I am on 64-bit - doesn't work there either. Man oh man. It probably has something to do with the 290x having 4GB of VRAM vs 3GB or 2GB on all other models. Only real difference apart from shader count.
ok its working now Smiley just download update version Smiley

what update did you do may i ask?

GPU plot generator v1.0.0 > GPU plot generator v1.1.0 driver 13.9 catalyst

hmmm ok im using same plotting version but im using catalyst 14.7 and also lowered clock settings 10% as advised but its still coming up with the window stating it encountered a problem and closed
try like this  X:\burst2\burst-pool-miner>gpuPlotGenerator.exe X:/burst2/burst-pool-miner/plots 10364770829529893068 0 330000 2000 128

right just to confirm on my hdd i have my wallet in a folder my burst-pool-miner in a folder and the gpu plotter in a folder all on my H drive. does the gpu plotter need to be in with the pool miner or is it ok where it is?
sr. member
Activity: 252
Merit: 250
New client Update 1.1.0

Backend is caught up to date with nxt 1.2.8.
Nxt new APIs are usable.
Hard fork on block 11800 to enable new nxt features(encrypted messaging, DGS).
UI is not yet updated for new features.

Move your burst_db folder from 1.0.3 into the new folder to avoid a resync. Db upgrade will take a few minutes though.

https://mega.co.nz/#!3xZ2DIwR!QQnamRK_JCz-QvFwb_A9gS6_tWCxAiFtVoqI8Unqlhg
sha256: f9d2a2d199993088eb9a03f1cb282ecbb36e704a4b7c609d5e878573752dad30

Good work Smiley
hero member
Activity: 868
Merit: 1000
Why does everyone keep talking about GPUs? I thought this was a hard drive capacity-"mined" coin? Huh

correct - the mining process is scraping over your plot files.
The amount of storage devoted for plot files is equal to your chances of finding a block.
It also defines the amount of CPU power you need to scrape, because you need to read 1/4096 of your plotted volume. In most cases this is not important and can easily run on a single core, in the background, not hurting other processes running.

The actual "plotting" involves a CPU-intensive process and may take a day for a Terabyte. The i7-3930K I used for plotting yielded 2 TB/day. Lots of people buy a couple 4TB disks and don't want to wait 2 weeks to plot them, hence the development of a gnu-plotter.




Its the same problem. I am buying 1000 TB and it will take weeks to plot. Having only CPU i will not think of getting 1000 TB. GPU only make people scale up and everything end up the same but people have to spend more money.

I'm waiting on NVIDIA for 750 TIs GTX 2 GB. Then I will scale up to the big time. I'll convert my office into a BURST Farm.

maybe u want to contact djm for that

Well I may have to hire him. Can't expect that for free LOL.

Its open source. Donate to him. I will be donating to him. Once its out.

Yeah that's what I meant.

i actually contacted him. But he says he need to see a working version first (AMD) before he pay any attention to it.
legendary
Activity: 1582
Merit: 1019
011110000110110101110010
Why does everyone keep talking about GPUs? I thought this was a hard drive capacity-"mined" coin? Huh

correct - the mining process is scraping over your plot files.
The amount of storage devoted for plot files is equal to your chances of finding a block.
It also defines the amount of CPU power you need to scrape, because you need to read 1/4096 of your plotted volume. In most cases this is not important and can easily run on a single core, in the background, not hurting other processes running.

The actual "plotting" involves a CPU-intensive process and may take a day for a Terabyte. The i7-3930K I used for plotting yielded 2 TB/day. Lots of people buy a couple 4TB disks and don't want to wait 2 weeks to plot them, hence the development of a gnu-plotter.




Its the same problem. I am buying 1000 TB and it will take weeks to plot. Having only CPU i will not think of getting 1000 TB. GPU only make people scale up and everything end up the same but people have to spend more money.

I'm waiting on NVIDIA for 750 TIs GTX 2 GB. Then I will scale up to the big time. I'll convert my office into a BURST Farm.

maybe u want to contact djm for that

Well I may have to hire him. Can't expect that for free LOL.

Its open source. Donate to him. I will be donating to him. Once its out.

Yeah that's what I meant.
member
Activity: 112
Merit: 10
The dev's 2.0 Pool is not updating. 2 shares submited and recieved in last 20 minutes - neither recorded.
hero member
Activity: 868
Merit: 1000
Why does everyone keep talking about GPUs? I thought this was a hard drive capacity-"mined" coin? Huh

correct - the mining process is scraping over your plot files.
The amount of storage devoted for plot files is equal to your chances of finding a block.
It also defines the amount of CPU power you need to scrape, because you need to read 1/4096 of your plotted volume. In most cases this is not important and can easily run on a single core, in the background, not hurting other processes running.

The actual "plotting" involves a CPU-intensive process and may take a day for a Terabyte. The i7-3930K I used for plotting yielded 2 TB/day. Lots of people buy a couple 4TB disks and don't want to wait 2 weeks to plot them, hence the development of a gnu-plotter.




Its the same problem. I am buying 1000 TB and it will take weeks to plot. Having only CPU i will not think of getting 1000 TB. GPU only make people scale up and everything end up the same but people have to spend more money.

I'm waiting on NVIDIA for 750 TIs GTX 2 GB. Then I will scale up to the big time. I'll convert my office into a BURST Farm.

maybe u want to contact djm for that

Well I may have to hire him. Can't expect that for free LOL.

Its open source. Donate to him. I will be donating to him. Once its out.
legendary
Activity: 1582
Merit: 1019
011110000110110101110010
Why does everyone keep talking about GPUs? I thought this was a hard drive capacity-"mined" coin? Huh

correct - the mining process is scraping over your plot files.
The amount of storage devoted for plot files is equal to your chances of finding a block.
It also defines the amount of CPU power you need to scrape, because you need to read 1/4096 of your plotted volume. In most cases this is not important and can easily run on a single core, in the background, not hurting other processes running.

The actual "plotting" involves a CPU-intensive process and may take a day for a Terabyte. The i7-3930K I used for plotting yielded 2 TB/day. Lots of people buy a couple 4TB disks and don't want to wait 2 weeks to plot them, hence the development of a gnu-plotter.




Its the same problem. I am buying 1000 TB and it will take weeks to plot. Having only CPU i will not think of getting 1000 TB. GPU only make people scale up and everything end up the same but people have to spend more money.

I'm waiting on NVIDIA for 750 TIs GTX 2 GB. Then I will scale up to the big time. I'll convert my office into a BURST Farm.

maybe u want to contact djm for that

Well I may have to hire him. Can't expect that for free LOL.
legendary
Activity: 1059
Merit: 1000
Can i mine on multiple hard drives?
Yes, you just need seperate miners running for each drive.

So I can create a plot for each disk and then start a miner for each disk?  Wink

Can I do it with the same address?

BURS----

Yes dude. http://burstcoin.info/faq.php

Perfect, thanks! Wink
hero member
Activity: 868
Merit: 1000
Why does everyone keep talking about GPUs? I thought this was a hard drive capacity-"mined" coin? Huh

correct - the mining process is scraping over your plot files.
The amount of storage devoted for plot files is equal to your chances of finding a block.
It also defines the amount of CPU power you need to scrape, because you need to read 1/4096 of your plotted volume. In most cases this is not important and can easily run on a single core, in the background, not hurting other processes running.

The actual "plotting" involves a CPU-intensive process and may take a day for a Terabyte. The i7-3930K I used for plotting yielded 2 TB/day. Lots of people buy a couple 4TB disks and don't want to wait 2 weeks to plot them, hence the development of a gnu-plotter.




Its the same problem. I am buying 1000 TB and it will take weeks to plot. Having only CPU i will not think of getting 1000 TB. GPU only make people scale up and everything end up the same but people have to spend more money.

I'm waiting on NVIDIA for 750 TIs GTX 2 GB. Then I will scale up to the big time. I'll convert my office into a BURST Farm.

maybe u want to contact djm for that
legendary
Activity: 1582
Merit: 1019
011110000110110101110010
Why does everyone keep talking about GPUs? I thought this was a hard drive capacity-"mined" coin? Huh

correct - the mining process is scraping over your plot files.
The amount of storage devoted for plot files is equal to your chances of finding a block.
It also defines the amount of CPU power you need to scrape, because you need to read 1/4096 of your plotted volume. In most cases this is not important and can easily run on a single core, in the background, not hurting other processes running.

The actual "plotting" involves a CPU-intensive process and may take a day for a Terabyte. The i7-3930K I used for plotting yielded 2 TB/day. Lots of people buy a couple 4TB disks and don't want to wait 2 weeks to plot them, hence the development of a gnu-plotter.




Its the same problem. I am buying 1000 TB and it will take weeks to plot. Having only CPU i will not think of getting 1000 TB. GPU only make people scale up and everything end up the same but people have to spend more money.

I'm waiting on NVIDIA for 750 TIs GTX 2 GB. Then I will scale up to the big time. I'll convert my office into a BURST Farm.
member
Activity: 87
Merit: 10
X:\burst2\burst-pool-miner>gpuPlotGenerator.exe 10364770829529893068 0 10000 16
GPU plot generator v1.0.0
Author: Cryo
Bitcoin: 138gMBhCrNkbaiTCmUhP9HLU9xwn5QKZgD
Burst: BURST-YA29-QCEW-QXC3-BKXDL
--------------
Creating plots for nonces 0 to 10000 (2 GB) using 4 MB memory
Retrieving OpenCL platform
Retrieving OpenCL GPU device
Creating OpenCL context
Creating OpenCL command queue
Creating CPU buffer
Creating OpenCL GPU buffer
Creating OpenCL program
Building OpenCL program
"C:\Users\hoop\AppData\Local\Temp\OCL2292.tmp.cl", line 71: warning: shift
          count is too large
                (p_buffer[p_offset + 4] << 32) |
                                           ^

"C:\Users\hoop\AppData\Local\Temp\OCL2292.tmp.cl", line 72: warning: shift
          count is too large
                (p_buffer[p_offset + 5] << 40) |
                                           ^

"C:\Users\hoop\AppData\Local\Temp\OCL2292.tmp.cl", line 73: warning: shift
          count is too large
                (p_buffer[p_offset + 6] << 48) |
                                           ^

"C:\Users\hoop\AppData\Local\Temp\OCL2292.tmp.cl", line 74: warning: shift
          count is too large
                (p_buffer[p_offset + 7] << 56);
                                           ^

"C:\Users\hoop\AppData\Local\Temp\OCL2292.tmp.cl", line 90: warning: shift
          count is too large
                (p_buffer[p_offset] << 56) |
                                       ^

"C:\Users\hoop\AppData\Local\Temp\OCL2292.tmp.cl", line 91: warning: shift
          count is too large
                (p_buffer[p_offset + 1] << 48) |
                                           ^

"C:\Users\hoop\AppData\Local\Temp\OCL2292.tmp.cl", line 92: warning: shift
          count is too large
                (p_buffer[p_offset + 2] << 40) |
                                           ^

"C:\Users\hoop\AppData\Local\Temp\OCL2292.tmp.cl", line 93: warning: shift
          count is too large
                (p_buffer[p_offset + 3] << 32) |
                                           ^

Error:E013:Insufficient Private Resources!

An error occured in the generation process, aborting...
>>> Unable to build the OpenCL program

windows 7 64bit radeon 280x driver 13.9
gpuPlotGenerator only work 32 bit system ?

I am on 64-bit - doesn't work there either. Man oh man. It probably has something to do with the 290x having 4GB of VRAM vs 3GB or 2GB on all other models. Only real difference apart from shader count.
ok its working now Smiley just download update version Smiley

what update did you do may i ask?

GPU plot generator v1.0.0 > GPU plot generator v1.1.0 driver 13.9 catalyst

hmmm ok im using same plotting version but im using catalyst 14.7 and also lowered clock settings 10% as advised but its still coming up with the window stating it encountered a problem and closed
try like this  X:\burst2\burst-pool-miner>gpuPlotGenerator.exe X:/burst2/burst-pool-miner/plots 10364770829529893068 0 330000 2000 128
Jump to: