I've updated it to 128, it'll be active at the next scheduled restart of the stratum (in about 5h)
Thanks!
And the daemon is slow because diff adjust is too smooth, hence block time can descrease sensibly for long periods of time.
Topic: XCN Cryptonite Pool xcn.suprnova.cc M7 POW NVIDIA/CPU - page 2. (Read 4667 times)
Thanks!
And the daemon is slow because diff adjust is too smooth, hence block time can descrease sensibly for long periods of time.
I've updated it to 128, it'll be active at the next scheduled restart of the stratum (in about 5h)
In order to lower server load, may I suggest higher initial diff? 64 is way too low, I'd use 256 or more.
64 is only the initial diff and it's usually ramping up pretty fast after the first 15 seconds, so that isn't a big problem.
The main load is done by the daemon itself, not the stratum here surprisingly. (mem leak ?)
on initial connect, and on a stratum disconnect, it may hang and send tons of stale shares, then the worker gets banned, rinse and repeat.
please at least 128 :-)
the daemon is heavier than usual and I think this is due to the minichain (additional work for every block received, and block time is pretty low).
In order to lower server load, may I suggest higher initial diff? 64 is way too low, I'd use 256 or more.
64 is only the initial diff and it's usually ramping up pretty fast after the first 15 seconds, so that isn't a big problem.
The main load is done by the daemon itself, not the stratum here surprisingly. (mem leak ?)
In order to lower server load, may I suggest higher initial diff? 64 is way too low, I'd use 256 or more.
This coin is killing me... Never had to babysit a pool so much like XCN...
down again 
Pool up
Down again. 5 hours mining lost :-(
Pool Down
Down again, same time in the night as the last time it blocked.
Now the pool is finding blocks again, but I have old unconfirmed balance.
Some orphans again..
It's unbelievable how time consuming this half dead coins is.. It's a pool ops nightmare
Hehe I see by solo mining what you mean.
Btw, how's the bits json field of getwork a float? Is it the difficulty instead?
Yes,thats the diff
Down again, same time in the night as the last time it blocked.
Now the pool is finding blocks again, but I have old unconfirmed balance.
Some orphans again..
It's unbelievable how time consuming this half dead coins is.. It's a pool ops nightmare
Hehe I see by solo mining what you mean.
Btw, how's the bits json field of getwork a float? Is it the difficulty instead?
Down again, same time in the night as the last time it blocked.
Now the pool is finding blocks again, but I have old unconfirmed balance.
Some orphans again..
It's unbelievable how time consuming this half dead coins is.. It's a pool ops nightmare
Down again, same time in the night as the last time it blocked.
Now the pool is finding blocks again, but I have old unconfirmed balance.
Down again, same time in the night as the last time it blocked.
Up again...
DOWN for many hours.
Hey what's happening the unconfirmed didn't confirm for a day then disappeared!
Hey pallas,
I've checked those were oprhans (cryptonite silently stops reporting the block next time you do "listtransactions")
I've already overpaid some older blocks which explains the minusbalance in my wallet
that's ok, thanks for the update.
Hey what's happening the unconfirmed didn't confirm for a day then disappeared!
Hey pallas,
I've checked those were oprhans (cryptonite silently stops reporting the block next time you do "listtransactions")
I've already overpaid some older blocks which explains the minusbalance in my wallet
Jump to: