█▓▒░-< [ZPOOL.CA][BTC Multipool] The miners multipool >-░▒▓█ Paid 925+ BTC

[AngryDwarf]

@JaredKaragen - How is the income holding up? Last test over on hashpower.co took about 14-15 hours for 1 mBTC for me, which is on par with the recent zpool BTC mining test, which did seem to be a massive improvement on less recent earnings.

Still going strong.  I am really kind of baffled at the differences between a month ago and now given the fact that the pool's code hasn't really changed.   The major difference is I moved my S3 from my parents house to my house;  My internet here was very crappy last month and I moved it there to see what the latency difference of a fiber connection would have... if any.   it was very minor;  just fewer rejected shares due to a block found during transmission to the pool.

I am still seeing two payments/day for at lease 2.2-2.8mBTC;  which yesterday got me just above 5.5mBTC during both periods that there are 2 payments in the 24/hour earnings graph.  I noticed the pool's short-term earnings estimate in the upper right for SHA was 0.0033/Gh;  yet luck/profitability seemed to be right about where it normally is (maybe one device more profitable in that time?).

So by this figure ~0.165BTC/Mo (~$72) if the current profitability holds true... again;  I being lucky enough to have an unfettered power connection at my residence =)

Just cleared 1 mBTC in 8 hours. I'll assume that is definitely on the good luck side. I suppose we should thank crackfoo for what he didn't do!

[tmpwhore]

Any update on the SHA256 dropout issue? I will say it's happening less and less but it's still annoying as hell and cutting into earnings.

[bitwonder]

hello there sir, how do i setup to mine only adz coin, i rent nicehash to mine. it just gave me too many different coin

stratum+tcp://mine.zpool.ca:3533 -u adz WALLET_ADDRESS -p c=adz

is this the right setup ? please help sir.

[bitwonder]

hello there sir, how do i setup to mine only adz coin, i rent nicehash to mine. it just gave me too many different coin

stratum+tcp://mine.zpool.ca:3533 -u adz WALLET_ADDRESS -p c=adz

is this the right setup ? please help sir.

i just got it right, thank you sir

[JaredKaragen]

Just cleared 1 mBTC in 8 hours. I'll assume that is definitely on the good luck side. I suppose we should thank crackfoo for what he didn't do!

Lol; yeah.  And the SHA profitability estimate is hanging around 0.0035 which is on par with what it should have been when it was reporting 0.0054.

I just got the S7 hooked up an hour ago;  it's mining to its own address; so I can keep its profit separate from the rest of my little farm.

I'll report earnings as they reach milestone points

[JaredKaragen]

i think I've seen a dropout on my s7 already.  They weren't noticeable on my s3.

Strange; may be an avenue to consider.... Although i myself can't see how it would apply.

[Arsenay]

work today



./cpuminer -a X15  -o stratum+tcp://mine.zpool.ca:3733 -u VDPG63qruJXpC9QMYANDdBmy9RWZ5gWcPv -p c=VRC -t 4

work yesteday - ok

amazing stability ))

[crackfoo]

work today



./cpuminer -a X15  -o stratum+tcp://mine.zpool.ca:3733 -u VDPG63qruJXpC9QMYANDdBmy9RWZ5gWcPv -p c=VRC -t 4

work yesteday - ok

amazing stability ))

I'm mining with X15 as well and don't see any issues... Has there been any problems with your connection?

[tmpwhore]

i think I've seen a dropout on my s7 already.  They weren't noticeable on my s3.

Strange; may be an avenue to consider.... Although i myself can't see how it would apply.

Maybe the stratum server has a hard time with any miner connecting over a terahash or so? But when it goes tits up I see that EVERYONE is dumped not just me. I see that haspower.co uses the same front end, if they use the same statum server maybe crackfoo can give them a shout out and see if they have the same problem? Or maybe they'll have insight into what's going on?

[crackfoo]

i think I've seen a dropout on my s7 already.  They weren't noticeable on my s3.

Strange; may be an avenue to consider.... Although i myself can't see how it would apply.

 I see that haspower.co uses the same front end, if they use the same statum server maybe cockaroo can give them a shout out and see if they have the same problem? Or maybe they'll have insight into what's going on?

with 16 coins and 10TH, I doubt they have encountered the issue.

We have 23+/- coins and 100+TH

The problem is seems to stem from shit coin wallets. It's not a resource or connection issue, but need to find a way to handle those crappy wallets. Still an issue that is on top for us, and still working towards a fix but it has improved considerably.

[tmpwhore]

i think I've seen a dropout on my s7 already.  They weren't noticeable on my s3.

Strange; may be an avenue to consider.... Although i myself can't see how it would apply.

 I see that haspower.co uses the same front end, if they use the same statum server maybe cockaroo can give them a shout out and see if they have the same problem? Or maybe they'll have insight into what's going on?

with 16 coins and 10TH, I doubt they have encountered the issue.

We have 23+/- coins and 100+TH

The problem is seems to stem from shit coin wallets. It's not a resource or connection issue, but need to find a way to handle those crappy wallets. Still an issue that is on top for us, and still working towards a fix but it has improved considerably.

Yes I've noticed a lot less dropouts. Maybe if we can identify which shitcoin wallets are the problem. Maybe there is a way to increase the timeout variable on those coins? I've also noticed that the reconnect speed is alot faster as well. Onward and upward. Damn you shitcoins!

[Arsenay]

work today

./cpuminer -a X15  -o stratum+tcp://mine.zpool.ca:3733 -u VDPG63qruJXpC9QMYANDdBmy9RWZ5gWcPv -p c=VRC -t 4

work yesteday - ok

amazing stability ))

I'm mining with X15 as well and don't see any issues... Has there been any problems with your connection?

problem resolved  adding option --no-extranonce
in this time ))

ps:
not resolved

[smilodon]

I too have problem with payment. My balance was reached, but there was no payment. Collect a small fee even stopped due injury. My wallet is this. 15TZv5B7Bq6G9keCBYR6tTD7vvTbwtnhEY

[crackfoo]

I too have problem with payment. My balance was reached, but there was no payment. Collect a small fee even stopped due injury. My wallet is this. 15TZv5B7Bq6G9keCBYR6tTD7vvTbwtnhEY

Payments look ok... not sure what you're missing.  Your balance is only 0.00008760

[smilodon]

I too have problem with payment. My balance was reached, but there was no payment. Collect a small fee even stopped due injury. My wallet is this. 15TZv5B7Bq6G9keCBYR6tTD7vvTbwtnhEY

Payments look ok... not sure what you're missing.  Your balance is only 0.00008760

before days was, not today! Now I have picked another! Anyway the attention and do a pretty good job congratulations!

[JaredKaragen]

Yeah;  the disconnects on sha256 must have to do with higher hashrate connections...

My S3 isn't seeing the disconnects at all;  but my S7 regularly seems to start beeping and drop its fans while at the same time I can see it's output in MinerMonitor drop to the 100-300Gh range;  then less than a minute later it pops right back up to speed and is hashing fine.    Its acting like I yanked it's internet access for a short bit....   I put a failover pool #2 to solo.ckpool;  but the miner stayed locked on the solo pool instead of switching back to zpool.

I wonder how a wallet can cause this... very strange.   Seems to happen when my share % has peaked for 10-30 min.

http://zpool.ca/?address=1GCXCFihv74gusaM9fHNgbeH5ogk9sPhMC

Most of my rentals had nice linear profitability slopes on the 24hr earnings graph;

My s7 is rather... jagged.

Note:  setting difficulty manually to a value too low, just right, or too high;  had zero effect.

[crackfoo]

the pool needs to always know the current block template, so it has call through RPC, <coind> getblocktemplate this somehow is causing a problem... but quite randomly and seemingly not any particular coin. But sometimes the response comes back invalid, or not at all, and for whatever reason, stratum decides it needs to restart, rather than close the call and move on.

Still priority for us to find how to handle this situation gracefully. Have talked to another dev who thinks they may re-write it in another language, but no decision yet.

[AngryDwarf]

I do get the disconnects on my usb miners, so I don't think it is anything to do with hash rate. I generally only see the problem on the sha256 port (but don't use scrypt). I wonder what the specs of the server are? There are a lot of wallets running on the server, and a lot of stratum client connections to serve. That means a large number of active threads, and even with a lot of cores there is going to be a large run queue. Also, all those wallets are going to use a lot of RAM, so the system maybe swapping. I've only started learning about wallet RPC calls, but I have noticed that sometimes they can be slow to respond, and that's with only a handful of wallets running.
So it sounds like crackfoo may be right about the stratum processes needing to handle the situation more gracefully.

EDIT: And I suppose a lot of fast coins require more frequent getblocktemplate calls?

FURTHER EDIT: It's over 15 years since I was analysing performance issues on an 8 CPU server on a system that run 100's of processes. The system was only using 80-90% CPU, so it took quite a bit of convincing to get them to spend a few $million on upgrading to a 24 CPU server. The performance issues where solved on the new box. So it just goes to show, that on a complex interdependent system, processing capacity can be hit without seeing 100% CPU usage. They where big boxes in those days!

In the case of the RPC call being called in user space by the stratum process, this has to be served by a system thread in the kernel, to be served by the wallet user threads, for a response to be sent through another system thread, to be picked up again by the stratum user threads. On a system with a large run queue to be served, that may take some time.

[JaredKaragen]

http://www.intel.com/content/www/us/en/processors/xeon/xeon-phi-detail.html

This option is a nice thing to have nowadays compared to buying a whole new system;  I have been considering buying one just because of how much of a processor bottleneck I am having on my main system consisting of 2X SLAED (3.0G 8M 4Core) and 24Gb of ECC Reg...  Even though the core freq is 1333;  I still need more power so to speak.

My PC not only runs my miner processes on my GPU; recently been using all my spare threads on Argon2 mining;  sometimes it will control some USB miners such as gridseeds/U series antminers as well;  and also, mainly it's my home media center hooked to my TV... so... its normally working balls-to-the-wall 24/7... And surprisingly Win10 has been super stable and keeping uptimes well past a month with no issues at all.

[crackfoo]

I do get the disconnects on my usb miners, so I don't think it is anything to do with hash rate. I generally only see the problem on the sha256 port (but don't use scrypt). I wonder what the specs of the server are? There are a lot of wallets running on the server, and a lot of stratum client connections to serve. That means a large number of active threads, and even with a lot of cores there is going to be a large run queue. Also, all those wallets are going to use a lot of RAM, so the system maybe swapping. I've only started learning about wallet RPC calls, but I have noticed that sometimes they can be slow to respond, and that's with only a handful of wallets running.
So it sounds like crackfoo may be right about the stratum processes needing to handle the situation more gracefully.

EDIT: And I suppose a lot of fast coins require more frequent getblocktemplate calls?

FURTHER EDIT: It's over 15 years since I was analysing performance issues on an 8 CPU server on a system that run 100's of processes. The system was only using 80-90% CPU, so it took quite a bit of convincing to get them to spend a few $million on upgrading to a 24 CPU server. The performance issues where solved on the new box. So it just goes to show, that on a complex interdependent system, processing capacity can be hit without seeing 100% CPU usage. They where big boxes in those days!

In the case of the RPC call being called in user space by the stratum process, this has to be served by a system thread in the kernel, to be served by the wallet user threads, for a response to be sent through another system thread, to be picked up again by the stratum user threads. On a system with a large run queue to be served, that may take some time.

zpool started off on one machine and is now running on 3. The stratum server has only the stratum and front end/db processes running on 8 core Xeon , 32gb ram & ssds. Coins are split up over 2 machines, each, 12 core Xeons, 64 gb, just not on SSD's simply because bitcoin is an ass of a blockchain and the SSD's weren't big enough to be comfortable especially in a RAID configuration. None of them swap out at all and carry a load of ~0.4, ~15-20% CPU usage and ~30% RAM usage. All housed within the same data center.

ulimits have been adjusted way out to 102400 and a couple of the stratums use ~50k of the limit.

They appear to handle it without issue... but I wouldn't be surprised if there is something with the threading...