Topic: BiblePay - TestNet Thread - Pool Testing for Proof of Bible Hash Pool (PoBh) - page 4. (Read 13211 times)

On 1.0.2.5 something is different, this is what I see in that line:


But CPU usage is still chaotic and not nearly fully utilized.

The hashrate is half as before and at pollinfo3 it says that is down and returning to minningpolo.

Does need to upgrade the wallet to the latest version of 1.0.2.5? How i do the upgrade in windows?

There is a problem with this and I'm talking about the main net. Mining constantly switches between pool and solo (true/false) and it definitely affects performance. Even in the short periods of time when "poolmining" says "true", there's always the "POOL DOWN-REVERTING TO SOLO MINING" error in the "poolinfo3". With the constant switching we are not mining the same as without switching (e.g. number of shares submitted), because I see that CPU usage is all over the place, at times even dropping to less than 10% instead of the constant 99%. The hash rate also plummets during the constant jumping from solo to pool and vice versa. This probably also affects solo mining because I'm not sure how effective is to solo mine for only a few seconds and then get interrupted again.

Also, when I stopped mining on one of the computers and then resumed, it could never go back to its previously established hash rate, but only around 60% of it, while other identical machines are still on the same hash rate, as though there's some kind of an age priority. If it's of any significance, on the restarted machine, "miningpulse" parameter is around 6000, while on the uninterrupted ones it's about 500K.

Isn't all this just a simple issue with the lack of CPU power on the server? I mean, it could be easily solved by employing a more powerful server and I bet that a few people here would be willing to donate for the costs, myself included. Or simply open source the pool and somebody will host it on a higher-end machine.

Thanks!

I first updated all my wallets to 1.0.2.5. and then I did a reindex on the mainchain wallets. This went without any issues.
I then started a testnet wallet with no blocks etc, and that also synced without any problems. It's poolmining on testnet now

The pool still does seem to have some issues though. It seems my miners jump on and off the pool at seemingly random intervals.

This is the mininginfo I got from my four mainnet miners at about the same time:

{
  "blocks": 5411,
  "currentblocksize": 2059,
  "currentblocktx": 4,
  "difficulty": 0.06419642745191464,
  "errors": "",
  "genproclimit": 7,
  "networkhashps": 168700.7953206531,
  "hashps": 34141.63594535423,
  "minerstarttime": "08-30-2017 16:30:29",
  "pooledtx": 4,
  "testnet": false,
  "chain": "main",
  "biblepay-generate": true,
  "poolinfo1": "",
  "poolinfo2": "",
  "poolinfo3": "CFW 08-30-2017 19:40:11; ",
  "miningpulse": 12081,
  "poolmining": true
}



{
  "blocks": 5411,
  "currentblocksize": 2059,
  "currentblocktx": 4,
  "difficulty": 0.0641964274519146get4,
  "errors": "",
  "genproclimit": 10,
  "networkhashps": 168700.7953206531,
  "hashps": 57553.43191954364,
  "minerstarttime": "08-30-2017 16:31:57",
  "pooledtx": 4,
  "testnet": false,
  "chain": "main",
  "biblepay-generate": true,
  "poolinfo1": "B9LeH2D3pxTHcssNhgBqseJekonk1q36w8; B9LeH2D3pxTHcssNhgBqseJekonk1q36w8; B9LeH2D3pxTHcssNhgBqseJekonk1q36w8; B9LeH2D3pxTHcssNhgBqseJekonk1q36w8; B9LeH2D3pxTHcssNhgBqseJekonk1q36w8; B9LeH2D3pxTHcssNhgBqseJekonk1q36w8; B9LeH2D3pxTHcssNhgBqseJekonk1q36w8; B9LeH2D3pxTHcssNhgBqseJekonk1q36w8; ",
  "poolinfo2": "RM_08-30-2017 19:38:57; RM_08-30-2017 19:39:13; RM_08-30-2017 19:39:20; Submitting Solution 08-30-2017 19:39:25; RM_08-30-2017 19:39:16; RM_08-30-2017 19:38:50; RM_08-30-2017 19:39:20; RM_08-30-2017 19:38:53; ",
  "poolinfo3": "POOL DOWN-REVERTING TO SOLO MINING; POOL DOWN-REVERTING TO SOLO MINING; POOL DOWN-REVERTING TO SOLO MINING; POOL DOWN-REVERTING TO SOLO MINING; POOL DOWN-REVERTING TO SOLO MINING; POOL DOWN-REVERTING TO SOLO MINING; POOL DOWN-REVERTING TO SOLO MINING; POOL DOWN-REVERTING TO SOLO MINING; POOL DOWN-REVERTING TO SOLO MINING; ",
  "miningpulse": 20495,
  "poolmining": true
}




{
  "blocks": 5411,
  "currentblocksize": 2059,
  "currentblocktx": 4,
  "difficulty": 0.06419642745191464,
  "errors": "",
  "genproclimit": 9,
  "networkhashps": 168700.7953206531,
  "hashps": 57725.4744221154,
  "minerstarttime": "08-30-2017 16:31:29",
  "pooledtx": 4,
  "testnet": false,
  "chain": "main",
  "biblepay-generate": true,
  "poolinfo1": "B9LeH2D3pxTHcssNhgBqseJekonk1q36w8; B9LeH2D3pxTHcssNhgBqseJekonk1q36w8; B9LeH2D3pxTHcssNhgBqseJekonk1q36w8; ",
  "poolinfo2": "RM_08-30-2017 19:39:53; RM_08-30-2017 19:39:49; RM_08-30-2017 19:39:57; ",
  "poolinfo3": "POOL DOWN-REVERTING TO SOLO MINING; CFW 08-30-2017 19:39:32; ",
  "miningpulse": 20364,
  "poolmining": true
}



{
  "blocks": 5411,
  "currentblocksize": 2059,
  "currentblocktx": 4,
  "difficulty": 0.06419642745191464,
  "errors": "",
  "genproclimit": 3,
  "networkhashps": 168700.7953206531,
  "hashps": 53349.53213422249,
  "minerstarttime": "08-30-2017 17:30:51",
  "pooledtx": 4,
  "testnet": false,
  "chain": "main",
  "biblepay-generate": true,
  "poolinfo1": "B9LeH2D3pxTHcssNhgBqseJekonk1q36w8; ",
  "poolinfo2": "RM_08-30-2017 19:32:52; ",
  "poolinfo3": "",
  "miningpulse": 20053,
  "poolmining": true
}



The hashrate in the pool is also lower than expected. But maybe that's because they are jumping on and off.
The "poolmining" tag also sometimes switches to 'false'.

NVM.  I figured it myself

I didn't do upgrade on linux yet . 
installed it from 1.0.2.3  sources. 
 that's  why I'm asking for help upgrading it further

this is really below the belt.   nobody hates anybody here and the DEVs are doing great job . 

it's just the about the team work here .  If we are doing a common job we should be in sync .

Dev dont worry about the haters, youre doing fantastic work!

LOL, that would be hilarious if we had "In the beginning, God created..." in the Genesis block, dang I wish I would have thought of that before we went live while mining the genesis block.  I could have probably left it mine until it hit a verse from Genesis.


Good, thanks for all the testing.  My tests pretty much are equivalent to yours as far as resyncing and reindexing.

Looks like we are close to make a 1.0.2.6 version for the mandatory, unless someone raises an issue within 2 days or so.

EDIT:
Hey, I think you just gave an idea for a new feature.  We can probably hardcode In the beginning in the Prod chain for block 0, that would be a nice twist for this coin.

First of all, I will definitely be giving a notice for maintenance when the pool is in Prod and its going to go down.
The pool is not even in Prod yet.

As far as today is concerned, I had to move the rack and I left it plugged in and it went down without me knowing - sorry about that.

Anyway, your clients will solo mine when you lose the pool connection, so its not really a problem.  The latest version doesnt have the issue where it slows down as it only checks on pool health once every 5 minutes or so.  

The same way you upgrade from 1.0.1.9 to 1.0.2.3, upgrade your client before mining.

Yeah, sorry I didn't have time until this morning to sit down and crank the numbers.

So I did two -reindexes under 1.0.2.3, and they were pretty successful, just wouldn't sync the last block or two very timely.

Went into /AppData/Roaming/Biblepaycore/testnet3/...  Blocks/ .... Chainstate/ and Blocks/Index.  Deleted all the files in those folders.  Restarted wallet, it got to the "no block sources available" message in about 20 seconds, again under 1.0.2.3.

Downloaded 1.0.2.4, installed, -reindex worked quickly, syched.  Shut it down, deleted the files again, restarted.  It rebuilt everything in under 1 min.  Synched.  Did one more -reindex, took a lot longer and wouldn't full sych, but I shut it down, the restarted without the -reindex and it got the last bit and was successful.  My test balance was unfazed by all of this (no issues).

Used showblock on a handful of blocks, noticed I just narrowly missed testblock 666 (got 665 and 667).  And noticed the genesis block does not contain a verse from Genesis.  I'm still not very adept at reading the showblock stats, other than the very obvious ones.  I wasn't sure on the block how to see "who" mined it to verify the blocks I mined in test showed that, but other than that, it was good.

For me is working now, be sure that you have the latest wallet version 1.0.2.4

DEVs can probably give at least a few hours notice before cutting off people . 
now we have 100s CPUs running and not hitting the pool .
 it gets pretty frustrated .

Is there an official limit threads of yousing pool?

all my workers < v.1.0.2.4 are cut off. 

could you point to clear instructions how to upgrade linux clients ? 

On the pool issue, I had to throw the switch to enforce the new version.
Ensure you have 1.0.2.4+ running, and it should run fine.

On reindex block chain, start the wallet with '-testnet -reindex' and ensure it recovers with no errors to the top.
Then start in -testnet mode with no blocks, database, and chainstate and ensure it syncs to the top?

Could you (or happy_merchant) explain how to do this? I'd be happy to do it, but I don't know where to start.

Also: the pools on both testnet and main seem to have issues at the moment. All my miners have reverted to solo-mining. And it looks like a lot of other miners also disappeared from the leaderboard.

So everything is passing in test?  Westwarmoth, has anyone tried reindexing there blocks file yet in testnet?

I believe there is currently a limit of 24 threads to use the pool