Topic: [XPM] [ANN] Primecoin High Performance | HP14 released! - page 55. (Read 397645 times)

Do take note that difficulty is skyrocketing !

Haven't found a block for the last 4 hours, 40 servers running...

Ok I have a i3 ivy a turion x2 laptop and an A6-3400m laptop. I was able to mine 12 blocks total with them until about a week ago I had nothing for a week prior so I just gave up and went Ypool. I'll start solomining again with my i3 although I'm thinking you got a little lucky finding a block on 3/4 machines in the last 2 days. I probably am wrong and just unlucky.

That's about normal.  PPS is a broken metric to use for calculations.

Hmm from hp8 to hp9 on this 32 core machine, i went from about 13k down to 5k.. :?

Yes, 4 quite ordinary home machines. The only one not to get a block in the last two days is the laptop.

runs very well cause the difficulty is rising (not because mrlt's gpu miner is out)

Runs well on a 300 server farm, or on your home PC?

Is anyone solomining still with a handful of processors, or is it Ypool or nothing?

HP9 runs pretty well with default settings

From OP's posts it looks like they've done a lot more testing of those variables than anyone else, especially me, so I've started to use the HP9 defaults because of this.

Love the script idea, to take it even further, you could build the logic in to the miner so that it adjusts itself automatically, helping keep performance high with the changing network.

I understand that but it would be helpful, at least for me, to understand how to go about optimizing. So we start with default parameters but where do we go from there? I understand that we should try optimizing chains per day but in what manner? Should we be finding the sweet spot for cpd by adjusting sievesize first (to find the highest value), then doing the same for sievepercentage, then roundsievepercentage? If we tweak the first one in and then change another, will it move the potential optimal point for the first variable optimized?

What I'm ideally looking for is some sort of workflow for optimizing the three variables. Like:

But maybe roundsievepercentage and / or sievepercentage are more dependent on cores, cpu speed, or something else. I just don't understand it enough to come up with a good process to try to optimize. Something like this would be very helpful. Once we figure out a good way to optimize, it seems like it would be relatively easy to create some type of optimization script that will run through this process, collect variables & performance from the log, and after a day or two of running through the script, spit out "based on the script, these are your optimal settings for this machine". Even if it takes a day to settle into these figures, over the long term it would be worth it.

You have most competent explanation exactly four posts above yours, from the developer himself.

No one seems to be clear on exactly what metric we're supposed to optimise for?

Can someone from the dev team provide some clarity here? Is it chains per minute, primes per second etc etc?

Apparently. I'm at about 2000, was at about 6000 previously.

PPS went down big time with hp9, was getting 6000-7000 pps previously. This is on 2xE5-2620, so 12 cores total.


Normal?

I'm getting those numbers


getmininginfo shows


something is off. I'm using a 32 core instance and 60GB of RAM. How does it look like when a block was found?

Well, I think we are getting to the point where the optimal settings for mainnet will be different from testnet. That means that most of us won't be able to accurately measure the actual block rate and we will have to rely on whatever performance metrics we have. That's where the chains/day estimate comes in. Instead of counting shorter chains found during the search, it's trying to estimate the chances of finding a full-length chain that may lead to a block. Assuming that the model works, it should be the best performance metric available.

The default settings are my best guesses of what the optimal settings would be for most people. With the latest release I was mainly looking at chains/day and then checking 5-chains/h after that to make sure there's some sense in the new setting.

No, you don't need the official client to run hp*

any need to uninstall the official 1.1 client and install the official 1.2 client prior to using hp9?

Big +1...I've been doing it based on others results since I don't know practical ways to test it myself.