Topic: [CLOSED] BTC Guild - Pays TxFees+NMC, Stratum, VarDiff, Private Servers - page 209. (Read 903150 times)

To be fair, running multiple instances of mining software is pretty rare.  Most people don't waste their time.  For the vast majority, BFGMiner is superior.  For fringe cases that for some reason decide they want to split it over multiple instances, cgminer is better (possibly).


Lol speak for yourself, i currently have no less then 4 instances of bfgminer running same time on 1 pc. I found out how to map com ports to each worker and running 50 usb miners,  divided them in half running on two pool same time, plus running scrypt (twice on same gpu) and if i really want to i can remap 2 com ports to solo mine a wee little btc.


All kinds of goodness you can get out of bfgminer.

Well, I'm too new at this gig to be able to tell you what is 'best', I don't even know what is 'best for me' as there could be other miners out there that work differently and provide me some additional advantage. I like to keep things clean and straightforward, maybe later I'll look at wizardry but for now it's all about connecting my Block Erupters to the BTCG pool and the various incarnations of BFGMiner that I've downloaded from the BTCG website have all worked well. I've had more issues with power supplies, hubs and drivers being uncooperative, internet connection drop-outs and external events like power failures and DDoS attacks than I have with BFGMiner which has worked liked a charm so far. I have to say that version 3.2.1 which I am using now seems to have lower error rates than the previous versions and as I run my miners via an Asus Eee pc on Windows 7 x32, so far it's been pretty much plain sailing, just what I like.

Now, here's where I need your help please. I've been following some of Luke-Jr's thread about the new BFGMiner version 3.3.0 which provides support for BF1/Blue Fury/Red Fury usb miners and I'm expecting a delivery of twelve of them hopefully before the end of the month. I suppose I'll need to upgrade to the new BFGMiner version 3.3.0 when the Blue Furies arrive and what I had hoped to do was just to add another Orico 10 port hub, plug in the Blue Furies alongside the Block Erupters, reboot the new miner and away we go, with both the Furies and the Erupters working side by side. I don't mess around with workers, I don't apportion any hashing to other pools, I try to set up as cleanly and as easily as possible.

So, given that I haven't delved too deeply into Luke-Jr's long technical thread and that so far I've read nothing to the contrary, does this sound like it will work out how I hope?

Any thoughts and information you can offer will be greatly appreciated.

Thanks very much.

I'm not really trying to say anything about either miner, usually.  I just know what a support problem USB serial drivers have been in general.  It just boggles my mind why anyone would volunteer for that irritation.

CGMiner has been very stable for me since 3.2.1.  I have not seen the issues that many supposedly have.  So I wonder how many are self inflicted?

Also I don't know what constitutes a "superior" mining program?

Yeah, that was...fun.  6 blocks in 10 minutes!  Going to be some nice shifts ending over the next few hours

Nice, six blocks in a row!

To be fair, running multiple instances of mining software is pretty rare.  Most people don't waste their time.  For the vast majority, BFGMiner is superior.  For fringe cases that for some reason decide they want to split it over multiple instances, cgminer is better (possibly).

And your serial port mappings *never* change when you reboot or replug your mining hardware so that you don't have to continually edit your .bat files so that you get what you want when running 4 instances of your miner software?

What?!?  This is the most retarded post I've ever seen on this board.  

BFGMiner is far simpler to get going - install VCP drivers, job done.  No messing with WinUSB, zdiag and all that shite. 


The original post I was replying to was saying "If you don't want to restart your miner all the time use an old version of cgminer" - which is crap.  

The whole network is growing quite rapidly lately.  BTC Guild historically has *slightly* outpaced network growth ever since ASICs started coming online, slightly increasing our share of the network as each round of new hardware comes online (then losing a giant chunk whenever a new private mining company arrives).

BTC Guild really grows very fast this week.

The latest hour pool speed has already exceed 750 TH/s.

Woohoo!  I love when my ESP works properly .  I guess after seeing the situation enough times (but explained differently each time), eventually I can link up the proper answer on the first try.

Thanks, that explained it, that miner was using an old worker which was set to PPS from the beginning. 

Pointing a new rig would take ~1 hour to visible under the PPLNS open shifts.  The next shift to complete (top of open shifts) would only be slightly higher (since the extra hash power was only present for part of the period).  The following one (added to the top of open shifts) would reflect the extra shares since that shift you had the extra power running the entire time.

Considering there is 740 TH/s mining successfully, if you're seeing a problem, you need to be more specific on what you've done.  Mining software versions, actually hash rates used, same/different worker, etc.


My suspicion:  If you truly doubled your hash rate for a period, you either didn't setup the second miner correctly (wrong pool/worker), or you had it running on PPS.  PPS Shares do not get listed under PPLNS stats.

I doubled my hashrate for 3 hours (direct another mining rig towards BTCGUILD), but during the next several shift, each new shift contains almost the same submitted shares as before, is this normal?

As a comparison, my hashrate were cut by half (maintenance of existing rigs) for several hours just a few days ago, and I could observe an immediate drop in submitted shares in each new shift

Now I dare not to direct that rig towards BTCGUILD

3.4.3 would crash for me eventually with a winsock error.  3.6.4 seems the most promising stable one since 3.1.1 for me.

M

I use a modified version of cgminer 3.1 I think. I noticed that from time to time it crashes when pool connection gets interrupted. It even outputs some message.

CGMiner works great for me.

But if you like messing with USB Serial drivers the have fun. I guess that's fine if you point all of your hash rate at one place a at a time.

Hmm, I don't need to restart 3.4.3.  Plus I don't need to mess with USB Serial drivers. Win, win.

I got it working. Aparently USB 3.0 hub doesn't lilke USB 3.0 port - who would've thought. Plugging them all in USB 2.0 worked like a charm. However, I don't have 6X USB 2.0 ports on one computer so I had to plug half on a different machine. At least now I know it wasn't any of my hardware.

Thanks for all the help, you guys always bail me out.

The shifts were about to drop under 30 minutes per shift, so the N value was increased by ~30% to bring it back to the 45-50 minute spot.  This means it takes more blocks to equal PPS, but you have more time to get them, meaning shifts will on average end closer to neutral (lows won't be as low, highs won't be as high).  This has absolutely zero impact on your variance in a 24 hour period, it only affects per-shift variance (decreasing it).