hiya folks, it's me again with another random technical question...
So, I've got myself 4T spread across 4 disks, and I've plotted and optimized and such (3.2T worth of nonces), and I'm mining away happily on cryptomining.farm using Uray's miner r4. In the past, I had no problems getting dcct's plotter and optimizer to work, but with a few different pools, I was unable to get the dcct miner to work, thus why I found myself using Uray's miner. Uray's miner is working ok, BUT, I've organized my disks into 50G plotfiles (16 files per disk), and when it gets a block, it seems to try to read all plot files across all disks at once, basically blowing up all disks at once, and making the machine put up massive load averages, while just basically waiting for IO. (I was using an old thin client, turned low power "server" to mine, but to try to help this, I'm now mining on 8 threads/4G RAM dedicated to the miner, and it's still melting whatever box I mine on)
So, I guess my question is there any way to make Uray's miner read the plots sequentially, or one disk at a time? Or, do any of the other cpu miners out there do that? It would seem I could get the same sort of speed per round, without beating the crap out of my machine that way...
I can't be the first to observe and/or request this, right?
Thanks.
I recall that if you specify the drives as C:\+D:\+E:\ it will read the drives sequentially instead of simultaneously - but I don't recall if that was the native miner or one of the third parties - probably Blagos.
Thanks!
Well, except that I'm running Linux (I don't do windoze, personally or professionally), soooo anyway, no drive letters.
The disks are mounted as such... (df -h output)
Filesystem Size Used Avail Use% Mounted on
/dev/sdf1 932G 801G 132G 86% /media/usb_drive0
/dev/sdg1 932G 801G 132G 86% /media/usb_drive1
/dev/sdh1 932G 801G 132G 86% /media/usb_drive2
/dev/sdi1 932G 801G 132G 86% /media/usb_drive3
I'll work on giving some other miners a shot, and we'll see if I get any different results. And please understand, I'm not bitching, it's actually working great, on my existing disk, I'm averaging like 600+ burst per day. I'm just trying to improve this ugliness (you can really see where I went from optimizing to mining in the graph below), and hopefully not sacrifice good equipment by cooking it on the quest for burstcoin...
seems a bit much in terms of load... No?
Oh shiney! Another question or two... my disks are all USB, not ideal, but I got the disks for free, so beggars can't be choosers. The 4 1T disks are USB3, and plugged into a single USB3 hub. The server in question actually has enough USB3 ports to plug in all 4 disks directly. Considering the hypothetical speeds of USB3, should that matter? Or, should I see greater performance if I plug all the disks directly into the box in your collective experiences?
And lastly, and I apologize for this if it's been answered or documented, but my attempts at finding this have proven fruitless thus far... This question is for both the "standard" version of a mining pool for burst (I think that's Uray's V2, if I remember correctly), AND for the wallet/lockchain itself... API? RPC? Logfile?? Meaning, is there a methodology to query metrics about my mining? balances? transactions? etc. etc. I'd settle for launching the miner and wallet with a ">>" into a file, if burst echoed anything with friggin' timestamps!! I'm a *NIX nerd by trade, and the wallet being written in java, AND the pool software seemingly not wanting to make a lot of standard information metrics available easily has been somewhat frustrating for me... I realize I'm the opposite of most, but I NEED my CLI damnit!
Thanks again. And sorry to ramble.