Who dafuq is still using DOS in 2016? ![Shocked](https://bitcointalk.org/Smileys/default/shocked.gif) pretty much anyone that grew up before windows 7 and still understands the usefullness of a command line. Oh, and every linux/unix user out there. The power given to you far exceeds a pretty gui. Command lines and DOS are not the same creatures. Not even in the same Genus! ![Undecided](https://bitcointalk.org/Smileys/default/undecided.gif)
|
|
|
...It is not hard to ssh into a S7 or S9 and switch pools manually and watch the share submission and time difficulty adjustment....
One would assume that if you're able to do that, then you're able to see that the rigs, themselves, run on a 1 diff no matter what you set. ![Wink](https://bitcointalk.org/Smileys/default/wink.gif)
|
|
|
Found a program that can convert a dos batch file into a .com file... basically converting the batch into assembly... and if things are picky its easy to port to .exe format....
Who dafuq is still using DOS in 2016? ![Shocked](https://bitcointalk.org/Smileys/default/shocked.gif)
|
|
|
I fried my good PC and ya'll just making me wish I had one that would be worth a damn to mine with. ![Tongue](https://bitcointalk.org/Smileys/default/tongue.gif) .... this thread is already full of TTF nonsense.
+1
|
|
|
Just the front end while payments are going out. Does it on purpose. Has a lot of db activity to do so all resources are freed for that.
So it's just a coincidence that the pool dies every time (within 1-3 minutes) too? ![Undecided](https://bitcointalk.org/Smileys/default/undecided.gif)
|
|
|
Well, I guess not. ![Undecided](https://bitcointalk.org/Smileys/default/undecided.gif) Error 521 Ray ID: 2cd5f0b5aee24ff9 • 2016-08-04 23:55:27 UTC Web server is down
|
|
|
looks like we lost ALL of the sha256 hash rate, even tho my miner still says alive and mining away finding blocks.
Here's to hoping 3 server hops in 15 minutes leads to improved performance.... ![](https://ip.bitcointalk.org/?u=http%3A%2F%2Fthegearpost.com%2Fwp-content%2Fuploads%2F2013%2F01%2Fthegearpost_final_touch_roller_rock_glass_whiskey.jpg&t=663&c=vewtDSzICft2xQ)
|
|
|
looks ok... now?
Ya. Skerd me when you rebooted it, since I was adjusting a fan on one of the S9s (I hate how they whistle) and everyone started beeping. ![Tongue](https://bitcointalk.org/Smileys/default/tongue.gif)
|
|
|
A new hiccup: Miners: 1KNQxxxk Summary Miners Shares Hashrate sha256 0 34.3936% 66.3 Th/s Earnings are being recorded, though. ![Grin](https://bitcointalk.org/Smileys/default/grin.gif)
|
|
|
"pending balance" on zpool is actually "pending estimate"
+1 As is "Total Unpaid" and "Total Earned".
|
|
|
OK, here's the simple answer on diffs ....
Set whatever you want, just don't ever ask why you have x% of the pool and only get x/2% on a given coin at a given point.
If you're fine with a 10%-20% variance in you returns, then that's good enough for you. If you're not fine with a 10%-20% variance in you returns, then don't intentionally set yourself into a high variance.
The End.P.S. - I'm totally fine with continuing to get free percentages of shares because you turned yours in too late! ![Grin](https://bitcointalk.org/Smileys/default/grin.gif)
|
|
|
im not going to pretend to know everything.. or even care.. all i do know is if i set my diff too low on my s7, like say what you recommend.. which would be around 3000.. it jams up.. completely unresponsive.. have to pull the plug to get it working again.. ~3300
one thing you have to understand.. we arent mining bitcoin.. we are mining low diff alt coins.. some have difficulty in the 1000s.. And only one of them are under 3300. And even if they ALL were, if the server can't handle finding blocks at the rate of a given coin, then the server should be upgraded or handle that coin separately.
with a low diff coin, and a low worker diff, you can crank out 100s of shares a minute.. most will be discarded by cgminer. 20 shares per minute is not "100s"
all it does is makes the machine work harder.. it also transmits more data, and makes the pool work harder. The machine works no harder, because the machine only deals in 1 diff hashes and diff setting tells the software what to discard.
....
Replies bolded
|
|
|
Crackfoo knows about that issue, been going on for a long time.
You say that like it's something that should be expected. ![Huh](https://bitcointalk.org/Smileys/default/huh.gif)
|
|
|
...
Fact: If you're getting 100% rejects with 14-25 shares/minute, then something is wrong with the server or your modem/router is junk. REAL FACT is if you set it too low, you DDOS the pool... Let's see what a pool guy says about that..... ... So my suggestion is to aim for a share return rate no higher than the highest difficulty that keeps you at 1% variance if you are setting a "minimum difficulty" or perhaps the value that keeps you under 1.2% for a fixed difficulty. This can be worked out easily if you know your hashrate without even testing it.
So our target is a diff that returns 20-25 shares per minute. Every 71.6MH/s returns one share per minute - therefore every GH/s returns about 14 shares per minute.
A share return rate of 20 needs a diff of 1 per 1.432GH/s if setting a fixed difficulty. A share return rate of 25 needs a diff of 1 per 1.79GH/s if setting a minimum difficulty.
Most pools are allowing you to set a fixed diff, so let's keep this final recommendation as simple as possible, and aim for 20 shares per minute. That's a diff of 1 per 1.432GH/s. ...
If "you DDOS the pool" with the recommended settings from one of the guys that wrote cgminer and some of the most stable pools around, then your "pool" isn't a real pool!
|
|
|
@crackfoo, Why does everything crash at the exact time payments are made? ![Huh](https://bitcointalk.org/Smileys/default/huh.gif) [2016-08-04 00:44:40.239] Proxy 0:sha256.mine.zpool.ca:3333 failed, attempting reconnect [2016-08-04 00:45:40.243] Proxy 0:sha256.mine.zpool.ca:3333 recovered [2016-08-04 00:45:40.243] Successfully connected to pool 0 sha256.mine.zpool.ca:3333 as proxy [2016-08-04 00:47:11.759] Possible block solve diff 4816847.230639 ! [2016-08-04 00:47:27.243] Proxy 0:sha256.mine.zpool.ca:3333 failed, attempting reconnect [2016-08-04 00:47:47.244] Proxy 0:sha256.mine.zpool.ca:3333 recovered [2016-08-04 00:47:47.244] Successfully connected to pool 0 sha256.mine.zpool.ca:3333 as proxy
|
|
|
Wallet: 1xAMPLE4u2rEad Name Immature Confirmed Total Value* (total pending) 0.00726048 0.00562979 0.01289027 BTC
Balance 0.01059564 BTC Total Unpaid 0.02348591 BTC Total Paid*** 0.18075165 BTC Total Earned 0.20423756 BTC Immature + Confirmed = (total pending) 0.00726048 + 0.00562979 = 0.01289027 BTC(total pending) + Balance = Total Unpaid0.01289027 + 0.01059564 = 0.02348591 BTC
|
|
|
@Megaquake Why do I think it's going to take 4 .pdf files, 2 videos, and 9 PowerPoint presentations to explain this to you? The only things that are 100% true are: - "Confirmed"
- "Balance"
- "Total Paid"
- and the part of the graph that is this color!
The things that might be true are: - "Immature"
- "Total Unpaid"
- "Total Earned"
- and the part of the graph that is this color!
|
|
|
... look at both lines on the graph... any dips in the dark line?
Both go up steady unlike the MCM address
...Do not count on this number being true until sold on exchange and converted to the green...
|
|
|
Yes but eventually the pool will find a block, the pool not finding a block will not effect your current balance...
Your balance has gone UP the entire time
|
|
|
Let me shorten it so it's easier to read: ...I didnt make nothing for 11 hours? ... b) no one in the pool has found a block of that coin in 16 hours... Getting paid for shares requires shares.
|
|
|
|