[ANN][BURST] Burst | Efficient HDD Mining | New 1.2.3 Fork block 92000

[Yanakitu Tenatako]

I am having difficulty woth speed even with SATA3 drives, lots of things that seens "could work" simply don't.
By my experience I would stay away of USB 2.0 drives.

I can't read plots of 32Tb in less than 2 minutes. All on Sata3.

That is a matter of CPU bottleneck, and not reading speed. Go ahead and open a process monitor on your system. When a new block starts you will see your CPU at 100% (and if not, you need a better miner).

I spent some bucks on best A10 cpu that is available to the market, and guess what? Nothing changes.
On reading plots all cores also get to 100% and time is not significaly reduced (few seconds on 180 sec is not noticable really).

so, CPU really does not matter... not a lot. Maybe for 40 hdd cluster or so...

[unsoindovo]

there a re any possibility to know how many plotted TB are over burst address?

thank you!

[Grim]

Wow, our pool is doing amazingly! Thank you all! 


Just sent the first 10k bonus to the pool address, and I think we just found 3 blocks in a row!

I put 33TB on your pool. I'll gonna see for the next few days how it goes.
So don't send me any rewards yet 

You can send me some if I decide to stay.
(came from solo and devpoolv2)

[Blago]

I am having difficulty woth speed even with SATA3 drives, lots of things that seens "could work" simply don't.
By my experience I would stay away of USB 2.0 drives.

I can't read plots of 32Tb in less than 2 minutes. All on Sata3.

That is a matter of CPU bottleneck, and not reading speed. Go ahead and open a process monitor on your system. When a new block starts you will see your CPU at 100% (and if not, you need a better miner).

I spent some bucks on best A10 cpu that is available to the market, and guess what? Nothing changes.
On reading plots all cores also get to 100% and time is not significaly reduced (few seconds on 180 sec is not noticable really).

so, CPU really does not matter... not a lot. Maybe for 40 hdd cluster or so...

PM me which processor (A10 xxxx) and send me your config-file and start screenshot.
Miner has multicore processing algorithm, the more cores, the faster processing

[Blago]

[miner]

new update miner-burst-1.141101
https://www.dropbox.com/s/1ezxwhnjhkl2eyz/miner-burst-1.141101.zip?dl=0

changes:
* Minor cosmetic changes
- Options "UseResponseMaxTime" and "ResponseMaxTime" removed (no longer used in non-blocking sockets)
* Updater now in separate thread
* Added option "ProxyPort"



My config for host:

Code:

{
   "Mode" : "pool",
   "Server" : "pool.burstcoin.io",
   "Port": 80,
   "UpdaterAddr" : "pool.burstcoin.io",
   "UpdaterPort": 8124,
   "EnableProxy": true,
   "ProxyPort": 8126,
   "Paths":["C:\\plots","D:\\plots","E:\\plots","G:\\plots","H:\\plots","F:\\plots","I:\\plots"],
   "CacheSize" : 200000,
   "ShowMsg" : false , 
   "ShowUpdates" : false,
   "UseSorting" : true,
   "Debug": false,
   "UseFastRcv" : true, 
   "SendInterval": 100,
   "UpdateInterval": 2000
} 

Config for satellite:

Code:

{
   "Mode" : "pool",
   "Server" : "192.168.1.33",
   "Port": 8126,
   "UpdaterAddr" : "192.168.1.33",
   "UpdaterPort": 8126,
   "Paths":["C:\\plots\\","D:\\plots\\","E:\\plots\\","F:\\plots\\","G:\\plots\\"],
   "CacheSize" : 100000,
   "ShowMsg" : false , 
   "ShowUpdates" : false,
   "UseSorting" : true,
   "UseFastRcv" : false,
   "SendInterval": 50,
   "UpdateInterval": 3000
} 

src: https://github.com/Blagodarenko/miner-burst/

[go6ooo1212]

Wow , I'll handle some test of this new miner, Blago

EDIT: Just mailed you

[Sglasio]

C:\Users\Dmitry>ping pool3.burstcoin.io

Oбмeн пaкeтaми c pool3.burstcoin.io [23.227.167.165] c 32 бaйтaми дaнныx:
Пpeвышeн интepвaл oжидaния для зaпpoca.
Пpeвышeн интepвaл oжидaния для зaпpoca.

(((

[FakeAccount]

I'm still struggling with win7 64bit and it's memory insanity.  Does win 8 have same issues as win7?

keep hitting "File xxxxxxxxxxx locked?" messages and as a result not 100% of files are read.
When your miner gets this condition/error, could you have that specific thread pause for x number of seconds and then retry the same file where it left off?
I think maybe a parameter in the config file: "ThreadWait" : 5, (5 seconds) would work nicely.  parameter with value of 0 could be used to indicate not using this approach as default.
as other drives finish reading, memory becomes available and previous "file locked" threads can resume since memory is available. this all happens in the span of 5-15 seconds and pausing wouldn't effect the majority of mining time.
i can't think of another way to deal with this on win7.
I will purposefully re-plot some files/drives (strategically) to have some control over the order in which miner will finish reading all drives and not have the insane memory issues on win7.

What do you think about adding this option?  or maybe there's another way to achieve similar control?

[miner]

new update miner-burst-1.141101
https://www.dropbox.com/s/1ezxwhnjhkl2eyz/miner-burst-1.141101.zip?dl=0

changes:
* Minor cosmetic changes
- Options "UseResponseMaxTime" and "ResponseMaxTime" removed (no longer used in non-blocking sockets)
* Updater now in separate thread
* Added option "ProxyPort"



My config for host:

Code:

{
   "Mode" : "pool",
   "Server" : "pool.burstcoin.io",
   "Port": 80,
   "UpdaterAddr" : "pool.burstcoin.io",
   "UpdaterPort": 8124,
   "EnableProxy": true,
   "ProxyPort": 8126,
   "Paths":["C:\\plots","D:\\plots","E:\\plots","G:\\plots","H:\\plots","F:\\plots","I:\\plots"],
   "CacheSize" : 200000,
   "ShowMsg" : false , 
   "ShowUpdates" : false,
   "UseSorting" : true,
   "Debug": false,
   "UseFastRcv" : true, 
   "SendInterval": 100,
   "UpdateInterval": 2000
} 

Config for satellite:

Code:

{
   "Mode" : "pool",
   "Server" : "192.168.1.33",
   "Port": 8126,
   "UpdaterAddr" : "192.168.1.33",
   "UpdaterPort": 8126,
   "Paths":["C:\\plots\\","D:\\plots\\","E:\\plots\\","F:\\plots\\","G:\\plots\\"],
   "CacheSize" : 100000,
   "ShowMsg" : false , 
   "ShowUpdates" : false,
   "UseSorting" : true,
   "UseFastRcv" : false,
   "SendInterval": 50,
   "UpdateInterval": 3000
} 

src: https://github.com/Blagodarenko/miner-burst/

[Blago]

I'm still struggling with win7 64bit and it's memory insanity.  Does win 8 have same issues as win7?

keep hitting "File xxxxxxxxxxx locked?" messages and as a result not 100% of files are read.
When your miner gets this condition/error, could you have that specific thread pause for x number of seconds and then retry the same file where it left off?
...
What do you think about adding this option?  or maybe there's another way to achieve similar control?

Soon will add this option and re-reading problem files

[Yanakitu Tenatako]

I'm still struggling with win7 64bit and it's memory insanity.  Does win 8 have same issues as win7?

keep hitting "File xxxxxxxxxxx locked?" messages and as a result not 100% of files are read.
When your miner gets this condition/error, could you have that specific thread pause for x number of seconds and then retry the same file where it left off?
I think maybe a parameter in the config file: "ThreadWait" : 5, (5 seconds) would work nicely.  parameter with value of 0 could be used to indicate not using this approach as default.
as other drives finish reading, memory becomes available and previous "file locked" threads can resume since memory is available. this all happens in the span of 5-15 seconds and pausing wouldn't effect the majority of mining time.
i can't think of another way to deal with this on win7.
I will purposefully re-plot some files/drives (strategically) to have some control over the order in which miner will finish reading all drives and not have the insane memory issues on win7.

What do you think about adding this option?  or maybe there's another way to achieve similar control?

[miner]

new update miner-burst-1.141101
https://www.dropbox.com/s/1ezxwhnjhkl2eyz/miner-burst-1.141101.zip?dl=0

changes:
* Minor cosmetic changes
- Options "UseResponseMaxTime" and "ResponseMaxTime" removed (no longer used in non-blocking sockets)
* Updater now in separate thread
* Added option "ProxyPort"



My config for host:

Code:

{
   "Mode" : "pool",
   "Server" : "pool.burstcoin.io",
   "Port": 80,
   "UpdaterAddr" : "pool.burstcoin.io",
   "UpdaterPort": 8124,
   "EnableProxy": true,
   "ProxyPort": 8126,
   "Paths":["C:\\plots","D:\\plots","E:\\plots","G:\\plots","H:\\plots","F:\\plots","I:\\plots"],
   "CacheSize" : 200000,
   "ShowMsg" : false , 
   "ShowUpdates" : false,
   "UseSorting" : true,
   "Debug": false,
   "UseFastRcv" : true, 
   "SendInterval": 100,
   "UpdateInterval": 2000
} 

Config for satellite:

Code:

{
   "Mode" : "pool",
   "Server" : "192.168.1.33",
   "Port": 8126,
   "UpdaterAddr" : "192.168.1.33",
   "UpdaterPort": 8126,
   "Paths":["C:\\plots\\","D:\\plots\\","E:\\plots\\","F:\\plots\\","G:\\plots\\"],
   "CacheSize" : 100000,
   "ShowMsg" : false , 
   "ShowUpdates" : false,
   "UseSorting" : true,
   "UseFastRcv" : false,
   "SendInterval": 50,
   "UpdateInterval": 3000
} 

src: https://github.com/Blagodarenko/miner-burst/

That problem is common for me when there is not enough memory, like with 16Gb Blago miner works 32Tb no problem, taking out 8 Gb leaves me with "file locked" situation very soon. Win7 64bit ultimate.

[mmmaybe]

uray, what are doing with pool3 ?

what's the problem?

miner not connected and site not refresh...

come on over to http://burst.ga

you won't be upset, and I'll give you a bonus, and you'll get auto-bonuses too. We're the only BURST pool with auto-failover.

Some of our recent payouts have been over 4k in s single payout! There are many above 1k, and a couple above 2k as well. We are getting back to our spot at the top of the best pools list

Hopefully I can help out a bit (and take some of those payments ). I PM'ed you

[hvidgaard]

I am having difficulty woth speed even with SATA3 drives, lots of things that seens "could work" simply don't.
By my experience I would stay away of USB 2.0 drives.

I can't read plots of 32Tb in less than 2 minutes. All on Sata3.

That is a matter of CPU bottleneck, and not reading speed. Go ahead and open a process monitor on your system. When a new block starts you will see your CPU at 100% (and if not, you need a better miner).

I spent some bucks on best A10 cpu that is available to the market, and guess what? Nothing changes.
On reading plots all cores also get to 100% and time is not significaly reduced (few seconds on 180 sec is not noticable really).

so, CPU really does not matter... not a lot. Maybe for 40 hdd cluster or so...

What makes you say that you're not CPU bound, if it's running at 100%? That's the definition of CPU bound. I just tried to disable half of my cores, and processing time was almost perfectly doubled.

[Irontiga]

[HardInvest]

Holders, there will be payout soon, non-holders and holders, another 300 will be dumped on the market, down to about 134 BURST/each, so if you have a bid in the top 300, and it's above 134 BURST/each, then at least part of your order will be filled.

The payout will be soon, same with the extra sale, be ready

I will post again an hour before it happens, and then when it happens, and then after it happens.

[/HardInvest]

[MsCollec]

How can I invest in all these shares?

[Irontiga]

How can I invest in all these shares?

Go to the wallet->assets->add asset->

15295227971848272658

->buy order

Now don't go and buy at those extortionary prices, place a bid in top 300, and be rewarded shortly!

[mczarnek]

I was thinking I might buy a $100 worth of Burst.

But blockchain size of 23.79 GB when it's only three months old??
Source: https://bchain.info/BTC/

[Irontiga]

I was thinking I might buy a BTC or two worth of Burst.

But blockchain size of 23.79 GB when it's only three months old??
Source: https://bchain.info/BTC/

That is btc's blockchain size....BURST's i think is about 110mb

[mczarnek]

I was thinking I might buy a BTC or two worth of Burst.

But blockchain size of 23.79 GB when it's only three months old??
Source: https://bchain.info/BTC/

That is btc's blockchain size....BURST's i think is about 110mb

My bad.. good.. got to there from a Burst page, thought this was a burst dedicated website.

Though I'm actually surprised if it is indeed over 100mb.. not enough to kill the coin but at this size.. a little bit surprised.

Thanks.

[Irontiga]

I was thinking I might buy a BTC or two worth of Burst.

But blockchain size of 23.79 GB when it's only three months old??
Source: https://bchain.info/BTC/

That is btc's blockchain size....BURST's i think is about 110mb

My bad.. good.. got to there from a Burst page, thought this was a burst dedicated website.

Though I'm actually surprised if it is indeed over 100mb.. not enough to kill the coin but at this size.. a little bit surprised.

Thanks.

Perhaps because burst isn't a crapcoin that's just traded and left on an exchange? Also, note that there are all the asset/aliase/message/dgs transactions as well. These take up space.

[mczarnek]

Assuming you've seen this but Microsoft's write up on Permacoin:
http://cs.umd.edu/~amiller/permacoin.pdf

Their way of doing proof of storage, I believe in a way the allows storing actual data and something burstcoin has clearly thought in first post.