Topic: BiblePay - New Coin Launch - Official Thread - page 137. (Read 119850 times)

I dont understand why my I7 4770 does only 8k hps while your i5 4670 does 157k its like 20 times my hashrate

Pretty much the same speed:

http://cpuboss.com/cpus/Intel-Core-i7-4770-vs-Intel-Core-i5-4670

Awesome coin! I can bet the project will succeeded

this is an interesting coin ... not see one of a kind coin like this ... since i saw it last month i never thought that this coin and the dev will continue the project but as i see it now dev are very active and updated... looking forward to any update soon... as my opinion this project is in path of it success...

At i5-4670 - 80-85% used


But wallet out of sync (0 hours behind) with 8 active connection. - upd - ok now.

BiblePay
1.0.1.9 Non-Mandatory Release

http://www.biblepay.org

- More efficient Miner
- Miner crash prevention rule
- Biblepay Pool Miner inside client (pool coming soon)

* Note: After you install this version, before starting the program, edit your config file and lower the genproclimit by 50%, and slowly increase it later to your personal preference, otherwise you may not be able to move the mouse
on windows as this miner is more CPU consuming. *

So last night being concerned about the hashPS discrepancy between the XEON and my windows box (Note I dont even have the XEON yet), I experimented with the miner and found a significant increase in HPS on Windows Vs Linux by changing the order in which we hash the X11 hash,
 changing the windows threading priority, and then finally hashing the Bible Hash -> After the X11 hash, and in light of this, wanting to ensure the community receives total transparency and honesty I am creating an emergency release with this hash speed increase now - it will be available within 2 hours for download.

After this is available I would like to see if Kotbi will test the new version and let us know if we are now on par with you.  Also Kotbi please share with us your OS flavor and if you compile BBP from scratch with or without any change to optimizations.

Since the launch on July 23, I see this coin has a very good development, you have a lot of interest in the near future, and now it's ANN update, I think this will be a successful project, I'm very interested to join

Thanks, I was able to reproduce this and a fix will be out today.

Luckily, it only happens once every 12 hours or so, so it didnt become a huge nuisance yet.

The pool is still in testing. If you try to pool mine on the main blockchain it'll just revert to solo mining.

as i know pool is still in testing phase.

https://bitcointalk.org/index.php?topic=2070177.40

IS the pool mining started ?
Can someone guide me of how to do pool mining ?

I am currently on version 1.0.1.7

Looks like wallet die after this error:

 ** TestBlockValidity FAILED - pindexNew->pprev != chainActive.Tip() (assert(pindexNew->pprev == chainActive.Tip())); **
2017-08-08 05:05:06
BiblepayMiner -- runtime error: CreateNewBlock: TestBlockValidity failed:  (code 0)

Hi Dev,

  Managed to get the code compile, but it builds a biblepay-qt but not the .exe version, all the other binaries are compiled in .exe, only this one is missing.

Ive seen someone else saying the same thing on the board a few days ago.  Any idea why it would be missing?

Thanks a lot.  Yea, what I would like to get to the bottom of the hash discrepency on the Xeon (lol), 10* faster is smoking us on the quad core xeon.  Looking at the specs, the dell server pulls about 400 watts, so its on par with the gaming machines out there.  The only noticeable difference I found so far, is a relative hash biblepay running on an intel (a newer model, dont know the proc off hand) and it ran at about 12,000 hps, vs my old amd 6 core: 8500 hps, vs my linux box : 8000 hps, but the XEON really stands out.

I will have to set up multiple scenarios to get to the bottom of it, thanks a lot for sharing the info, we want this to be fair for everyone.  I would expect different OSs to be off by 10% or so, and results to be more wattage based, but in your case you pull the same watts roughly.  Dont get me wrong, high end servers could technically hash somewhat faster, I would think if it had multiple CPU's, possibly 4 * faster.

Its also going to be necessary for us to pull the libs out and really log the hash flow through the lib versions over cross compile types, as its possible the thread model in linux with slightly different dependencies could be a major contributing factor.  

I forgot to ask you, which OS are you running and do you build biblepay from scratch, without any particular optimizations or code changes?

Thanks!

I have a quad core xeon E3-3225 v5. It was from dell.com. It has 8GB memory and 8GB swap. 1TB harddrive I installed linux on it. It performs quite smooth for every thing.

both of them have pros and cons. But in the long term, do you expect to get the same amount of blocks? Let's say in one year.

C-CEX Update:

The exchange was in contact with us earlier today, and is now auditing the code.

I filled out their required questionnaire.

They have our logo.

I just ordered a quad processor, quad core xeon server (4 CPU, 2.9ghz speed with 4 cores per proc), so I can do some heavy duty algorithm testing on our PoBh algorithm.

Btw, for the person who had the xeon earlier, could you please share the specs with us? Model, proc count, core count, ram, disk drive type?

Thanks.

Im thinking in the future, we finely tune the algorithm to benefit full nodes based on work done by the node for biblepay, and watts consumed, but we will have a discussion as we go.

Super nice project maybe i will invest in it!

I prefer solo, even though it is more difficult