Beaflag VonRathburg
|
|
July 31, 2013, 03:20:22 AM |
|
a dual core i7 laptop and two weeks of non-stop mining, and i got a block ! woot. now i just have to wait for the price to rise again. ypool might get you 2+XPM/day. no more than 0.2/day I think in 25.5 hours I went from 5.28 to 13.66 XPM on ypool. 4 systems running mumus' 3.0 miner. With the pool miner I had a total of 11.5k PPS, mumus says I'm getting almost 90, but I think the calculation is off. I compared Cabin's miner to mumus' and the SPH are very similar. Haven't tried the pool miner for shares, but I see they have .35 out. You had a SUPER lucky streak then. You're the only one reporting these large gains. I am using Mumus' miner over 5 machines with slightly less PPS and in 25.3 hours made 0.933045 XPM. Hitting high share values has a lot to do with it. I wouldn't expect that your trend to continue.
|
|
|
|
xTachibana
Full Member
Offline
Activity: 164
Merit: 100
The All-in-One Cryptocurrency Exchange
|
|
July 31, 2013, 09:37:29 AM |
|
a dual core i7 laptop and two weeks of non-stop mining, and i got a block ! woot. now i just have to wait for the price to rise again. ypool might get you 2+XPM/day. no more than 0.2/day I think in 25.5 hours I went from 5.28 to 13.66 XPM on ypool. 4 systems running mumus' 3.0 miner. With the pool miner I had a total of 11.5k PPS, mumus says I'm getting almost 90, but I think the calculation is off. I compared Cabin's miner to mumus' and the SPH are very similar. Haven't tried the pool miner for shares, but I see they have .35 out. You had a SUPER lucky streak then. You're the only one reporting these large gains. I am using Mumus' miner over 5 machines with slightly less PPS and in 25.3 hours made 0.933045 XPM. Hitting high share values has a lot to do with it. I wouldn't expect that your trend to continue. i have 1 cpu, a 3570k, i average 1-4 coins per day and i have been mining for 5 days so its not luck for the most part, you just fucked up your settings somehow
|
|
|
|
bcp19
|
|
July 31, 2013, 11:38:24 AM |
|
a dual core i7 laptop and two weeks of non-stop mining, and i got a block ! woot. now i just have to wait for the price to rise again. ypool might get you 2+XPM/day. no more than 0.2/day I think in 25.5 hours I went from 5.28 to 13.66 XPM on ypool. 4 systems running mumus' 3.0 miner. With the pool miner I had a total of 11.5k PPS, mumus says I'm getting almost 90, but I think the calculation is off. I compared Cabin's miner to mumus' and the SPH are very similar. Haven't tried the pool miner for shares, but I see they have .35 out. You had a SUPER lucky streak then. You're the only one reporting these large gains. I am using Mumus' miner over 5 machines with slightly less PPS and in 25.3 hours made 0.933045 XPM. Hitting high share values has a lot to do with it. I wouldn't expect that your trend to continue. I may have had a little luck, current amount is 16.67...(~3 in the last 12 hours?) PPS seems to be a BS stat to go on now, but here are total running avgs across my machines: 380 SPH, 19.2 VPH, 1549 5ch/h, 104 6ch/h, 8.1 7ch/h, PPS 81k. Since 19.2/380=.05052, which is 4x the 5ch value and .4 times the 6ch value, I have not had 'super luck'. I think too many people are trying to pump up their PPS values at the cost of either shares or share values. It's obvious we need a new metric to look at, PPS is not it. I think a lot of people have used something -s 100000 to maximize PPS at a loss of VPH. 11.5kPPS = 4.3 VPS on a C2Quad, 15kPPS = 5.4 VPS on an i7, 27kPPS = 9.2 VPH on i5 2400, 28.2k = 9.7VPH on i5 2500k. From these numbers, it appears the C2Quad is doing best on VPH/PPS with stock settings, maybe the others need some tweaks. I have a second C2Quad running YAC, maybe it's time to switch it over and do some testing since I have a baseline to compare against.
|
I do not suffer fools gladly... "Captain! We're surrounded!" I embrace my inner Kool-Aid.
|
|
|
bcp19
|
|
July 31, 2013, 09:55:28 PM |
|
Got home from work and did some preliminary testing (Data is very rough due to short testing time, though both CPUs are Q6600's with 8GB ram):
Baseline C2Q(40 hours): 11.5kPPS, 60SPH, 4.3VPH, 235-5ch/h, 17-6ch/h, 1.5-7ch/h -s 200000 C2Q(1 hour): 15.9kpps, 44SPH, 2.3VPH, 140-5ch/h, 14.6-6ch/h, 0-7ch/h -s 400000 C2Q(1 hour): 14.3kPPS, 65SPH, 2.9VPH, 270-5ch/h, 17.5 6ch/h, 0-7ch/h -s 600000 C2Q(1 hour): 13.1kPPS, 49SPH, 2.6VPH, 232-5ch/h, 6.33-6ch/h, 1.27-7ch/h
I was about to start -s 800000 when I noticed mumus put out V4.
WOW! what a change. The 4 systems went from 90k to 105k PPS, but I still dislike using that as a guide (test 1 above proves more PPS doesn't = more SPH or VPH)
So, combined SPH went from 380 to 460. VPS went from 19.2 to 42.3 (only 90 min into run, so these may be artifically high due to luck), 5ch/h went from 1549 to 2810, 6ch/h was 104, now 246, 7ch/h from 8.1 to 19.
Looks like I will have to restart testing tomorrow after a good burn-in of V4, but I'm still making XPM. Currently up to 20.38, if I am reading forum time right, that's not quite 7 XPM in the last 21 hours.
All I can say at this point: THANKS mumus!
|
I do not suffer fools gladly... "Captain! We're surrounded!" I embrace my inner Kool-Aid.
|
|
|
Tuck Fheman
|
|
July 31, 2013, 11:01:23 PM |
|
a dual core i7 laptop and two weeks of non-stop mining, and i got a block ! woot. now i just have to wait for the price to rise again. ypool might get you 2+XPM/day. no more than 0.2/day I think I'm averaging 2+XPM/day with mumu's latest miner. It's well worth a shot if you're not hitting blocks solo. They now have a system that runs like PPLNS. His new one uses mikaelh's updates as well.
|
|
|
|
ivanlabrie
|
|
July 31, 2013, 11:05:09 PM |
|
a dual core i7 laptop and two weeks of non-stop mining, and i got a block ! woot. now i just have to wait for the price to rise again. ypool might get you 2+XPM/day. no more than 0.2/day I think I'm averaging 2+XPM/day with mumu's latest miner. It's well worth a shot if you're not hitting blocks solo. They now have a system that runs like PPLNS. His new one uses mikaelh's updates as well. It uses gmp?
|
|
|
|
hasle2
|
|
August 01, 2013, 02:18:07 AM |
|
a dual core i7 laptop and two weeks of non-stop mining, and i got a block ! woot. now i just have to wait for the price to rise again. ypool might get you 2+XPM/day. no more than 0.2/day I think I'm averaging 2+XPM/day with mumu's latest miner. It's well worth a shot if you're not hitting blocks solo. They now have a system that runs like PPLNS. His new one uses mikaelh's updates as well. It uses gmp? Yep, they added it a week ago: https://github.com/jh000/jhPrimeminer/commits/master
|
|
|
|
Lauda
Legendary
Offline
Activity: 2674
Merit: 2965
Terminated.
|
|
August 01, 2013, 10:56:11 AM |
|
|
"The Times 03/Jan/2009 Chancellor on brink of second bailout for banks" 😼 Bitcoin Core ( onion)
|
|
|
paulthetafy
|
|
August 01, 2013, 03:54:15 PM |
|
Okay I'm looking at the 5-chains/m and chain/d stats in debug.log. I can tweak my settings to either get higher 5-chains values OR higher chain/d values. So which should I be looking at, i.e. which is it better to have higher?
|
|
|
|
mikaelh (OP)
|
|
August 01, 2013, 04:26:51 PM |
|
Okay I'm looking at the 5-chains/m and chain/d stats in debug.log. I can tweak my settings to either get higher 5-chains values OR higher chain/d values. So which should I be looking at, i.e. which is it better to have higher?
The chains/day estimate is an upcoming feature added by Sunny King. It's a probabilistic model that is supposed to give a more realistic measure of the actual chain finding performance. Right now it's not producing fully accurate estimates. On testnet the estimate was at least 12% higher than observed rate. Assuming that the model is correct, you can still use for comparative purposes including tuning the parameters. There were a few issues with the model earlier but I've been working with Sunny to fix them. In short, chains/day should be the best performance metric so far.
|
|
|
|
paulthetafy
|
|
August 01, 2013, 04:33:27 PM |
|
Okay I'm looking at the 5-chains/m and chain/d stats in debug.log. I can tweak my settings to either get higher 5-chains values OR higher chain/d values. So which should I be looking at, i.e. which is it better to have higher?
The chains/day estimate is an upcoming feature added by Sunny King. It's a probabilistic model that is supposed to give a more realistic measure of the actual chain finding performance. Right now it's not producing fully accurate estimates. On testnet the estimate was at least 12% higher than observed rate. Assuming that the model is correct, you can still use for comparative purposes including tuning the parameters. There were a few issues with the model earlier but I've been working with Sunny to fix them. In short, chains/day should be the best performance metric so far. That's very interesting. As I said, tweaking the sievesize/percent/roundpercent I have settings that result in higher 5-chains values but lower chains/d and vice versa, so something doesn't seem quite right there - you would expect them to both rise / fall wouldn't you? Also why is it a decimal value (my values are in the 0.5-2.0 range)?
|
|
|
|
mikaelh (OP)
|
|
August 01, 2013, 05:16:38 PM |
|
Okay I'm looking at the 5-chains/m and chain/d stats in debug.log. I can tweak my settings to either get higher 5-chains values OR higher chain/d values. So which should I be looking at, i.e. which is it better to have higher?
The chains/day estimate is an upcoming feature added by Sunny King. It's a probabilistic model that is supposed to give a more realistic measure of the actual chain finding performance. Right now it's not producing fully accurate estimates. On testnet the estimate was at least 12% higher than observed rate. Assuming that the model is correct, you can still use for comparative purposes including tuning the parameters. There were a few issues with the model earlier but I've been working with Sunny to fix them. In short, chains/day should be the best performance metric so far. That's very interesting. As I said, tweaking the sievesize/percent/roundpercent I have settings that result in higher 5-chains values but lower chains/d and vice versa, so something doesn't seem quite right there - you would expect them to both rise / fall wouldn't you? Also why is it a decimal value (my values are in the 0.5-2.0 range)? The problem with primes/sec and 5-chains/h is that they're not actually measuring anything useful as far as solo mining is concerned. They are more like coincidental byproducts of the mining process. Those byproducts don't really mean anything by themselves (unless you're doing pooled mining at ypool.net). You can quite easily find lots of primes/sec or 5-chains/h if you want to but solo miners should only be concerned with improving the chances to find actual blocks. That's why I performed numerous tests on testnet to test the default parameters of the client. By now it is pretty commonly known that primes/sec does not directly correlate with the block rate and I have also seen some evidence that a higher 5-chains/h does not result in more blocks. The key idea behind the chains/day model is to estimate the probability that a candidate produces a full-length prime chain and then multiply that probability with the number of tests that are performed. As it turns out, all 3 tuning parameters supported by my client also influence this probability. They also effect the speed at which the candidates are produced and how fast they can be tested. Ideally you want to balance those settings out so that you expect to find more blocks. For example, if you adjust the settings so that the probability would be increased by 50% while the testing speed would go down by 10%, you will still get more blocks in the end. It doesn't really matter if you're finding 20% less 5-chains/h. The reason why chains/day is a decimal number is because it's trying to represent the expected number of full-length qualifying chains that you would find in a day (i.e. chains that will result in a block if they also meet the fractional difficulty). That number is typically very low when solo mining with the current difficulty on mainnet.
|
|
|
|
Lyddite
Member
Offline
Activity: 98
Merit: 10
|
|
August 01, 2013, 05:26:27 PM |
|
Is there some regression in the latest version? I realize that the rate of finding primes is not the only thing to consider.
Here is some data from a machine running a clone of CVS from a few hours ago today ( "version" : "v0.1.1xpm-93-g0751bbd-beta-hp8" )
2013-08-01 17:01:15 primemeter 7875206 prime/h 162190130 test/h 120 5-chains/h 0.178356 chain/d 2013-08-01 17:02:15 primemeter 7855064 prime/h 162149863 test/h 240 5-chains/h 0.179119 chain/d 2013-08-01 17:03:15 primemeter 7809919 prime/h 161926985 test/h 300 5-chains/h 0.177141 chain/d 2013-08-01 17:04:15 primemeter 7877955 prime/h 162077455 test/h 300 5-chains/h 0.177752 chain/d
And data from hp8 ("version" : "v0.1.1.0-unk-beta-hp8")
2013-08-01 17:06:52 primemeter 11272017 prime/h 96159859 test/h 240 5-chains/h 2013-08-01 17:07:52 primemeter 11382319 prime/h 97891766 test/h 240 5-chains/h 2013-08-01 17:08:52 primemeter 11387602 prime/h 97631808 test/h 600 5-chains/h 2013-08-01 17:09:52 primemeter 11423666 prime/h 97832785 test/h 420 5-chains/h
More tests are being run per hour which I suppose is a good thing. The sievesize remained the same.
--Lyddite
|
- Lyddite -
|
|
|
paulthetafy
|
|
August 01, 2013, 05:35:57 PM |
|
Okay I'm looking at the 5-chains/m and chain/d stats in debug.log. I can tweak my settings to either get higher 5-chains values OR higher chain/d values. So which should I be looking at, i.e. which is it better to have higher?
The chains/day estimate is an upcoming feature added by Sunny King. It's a probabilistic model that is supposed to give a more realistic measure of the actual chain finding performance. Right now it's not producing fully accurate estimates. On testnet the estimate was at least 12% higher than observed rate. Assuming that the model is correct, you can still use for comparative purposes including tuning the parameters. There were a few issues with the model earlier but I've been working with Sunny to fix them. In short, chains/day should be the best performance metric so far. That's very interesting. As I said, tweaking the sievesize/percent/roundpercent I have settings that result in higher 5-chains values but lower chains/d and vice versa, so something doesn't seem quite right there - you would expect them to both rise / fall wouldn't you? Also why is it a decimal value (my values are in the 0.5-2.0 range)? The problem with primes/sec and 5-chains/h is that they're not actually measuring anything useful as far as solo mining is concerned. They are more like coincidental byproducts of the mining process. Those byproducts don't really mean anything by themselves (unless you're doing pooled mining at ypool.net). You can quite easily find lots of primes/sec or 5-chains/h if you want to but solo miners should only be concerned with improving the chances to find actual blocks. That's why I performed numerous tests on testnet to test the default parameters of the client. By now it is pretty commonly known that primes/sec does not directly correlate with the block rate and I have also seen some evidence that a higher 5-chains/h does not result in more blocks. The key idea behind the chains/day model is to estimate the probability that a candidate produces a full-length prime chain and then multiply that probability with the number of tests that are performed. As it turns out, all 3 tuning parameters supported by my client also influence this probability. They also effect the speed at which the candidates are produced and how fast they can be tested. Ideally you want to balance those settings out so that you expect to find more blocks. For example, if you adjust the settings so that the probability would be increased by 50% while the testing speed would go down by 10%, you will still get more blocks in the end. It doesn't really matter if you're finding 20% less 5-chains/h. The reason why chains/day is a decimal number is because it's trying to represent the expected number of full-length qualifying chains that you would find in a day (i.e. chains that will result in a block if they also meet the fractional difficulty). That number is typically very low when solo mining with the current difficulty on mainnet. Thanks for the explanation mikael. I think I've managed to find optimum values now - or at least values that work well for me - and they are different to the defaults.
|
|
|
|
mikaelh (OP)
|
|
August 01, 2013, 05:54:05 PM |
|
Is there some regression in the latest version? I realize that the rate of finding primes is not the only thing to consider.
Here is some data from a machine running a clone of CVS from a few hours ago today ( "version" : "v0.1.1xpm-93-g0751bbd-beta-hp8" )
2013-08-01 17:01:15 primemeter 7875206 prime/h 162190130 test/h 120 5-chains/h 0.178356 chain/d 2013-08-01 17:02:15 primemeter 7855064 prime/h 162149863 test/h 240 5-chains/h 0.179119 chain/d 2013-08-01 17:03:15 primemeter 7809919 prime/h 161926985 test/h 300 5-chains/h 0.177141 chain/d 2013-08-01 17:04:15 primemeter 7877955 prime/h 162077455 test/h 300 5-chains/h 0.177752 chain/d
And data from hp8 ("version" : "v0.1.1.0-unk-beta-hp8")
2013-08-01 17:06:52 primemeter 11272017 prime/h 96159859 test/h 240 5-chains/h 2013-08-01 17:07:52 primemeter 11382319 prime/h 97891766 test/h 240 5-chains/h 2013-08-01 17:08:52 primemeter 11387602 prime/h 97631808 test/h 600 5-chains/h 2013-08-01 17:09:52 primemeter 11423666 prime/h 97832785 test/h 420 5-chains/h
More tests are being run per hour which I suppose is a good thing. The sievesize remained the same.
--Lyddite
What you're seeing is mostly caused by this commit made by Sunny: https://github.com/primecoin/primecoin/commit/2f6545476673f6438df41ca190ca6867a730c77bThat removes some redundant chain tests. Essentially it doesn't try to test for a Cunningham chain of the second kind if the candidate should only result in a chain of the first kind. I tested that block rate goes up by about 30% on testnet. I also saw that primes/sec dropped and that 5-chains/h dropped on mainnet. But again it's just less byproducts that don't matter.
|
|
|
|
zax983
|
|
August 01, 2013, 08:40:59 PM |
|
My best profit from 1 month = 0 XPM Being retard is not something you should be proud of My best profit from 1 month = 0 XPM You got what you deserve My best profit from 1 month = 0 XPM Damn dude! My Timex Sinclair TS1000 has found 3 blocks already! You really suck! No man. I will call you what is suck!!! Suck is when you found from first day coin that song good like XPM. And you start mining it, make 200 XPM = $200-300 just for a week, next week no 1 confirmation and next week all steal and called orphanes... I had exp with dozen more coins and no one SCAM me like this... But I continue to see what will happen and what, just 2 more weeks no 1 block found. It's not just bad luck, it's VERY SUCK COIN.
|
|
|
|
paulthetafy
|
|
August 01, 2013, 08:53:11 PM |
|
My best profit from 1 month = 0 XPM Being retard is not something you should be proud of My best profit from 1 month = 0 XPM You got what you deserve My best profit from 1 month = 0 XPM Damn dude! My Timex Sinclair TS1000 has found 3 blocks already! You really suck! No man. I will call you what is suck!!! Suck is when you found from first day coin that song good like XPM. And you start mining it, make 200 XPM = $200-300 just for a week, next week no 1 confirmation and next week all steal and called orphanes... I had exp with dozen more coins and no one SCAM me like this... But I continue to see what will happen and what, just 2 more weeks no 1 block found. It's not just bad luck, it's VERY SUCK COIN. Jees man you are the ONLY person complaining about this. Nobody else is having trouble mining this coin. Clearly, you have issues
|
|
|
|
zax983
|
|
August 01, 2013, 08:57:19 PM |
|
It's can't be my faul, coz I use recomended software from owner. So it's steal my ~200 XPM. It's all...
He or who think it's not fair, can correct this in any time with sending me any compensation here: AYt9xqb8vCDEQoL6W1hKxJmLwwQ6BvjFA6
Thanks in advance!
|
|
|
|
gigawatt
|
|
August 01, 2013, 09:06:32 PM |
|
I've updated my awk command to include the new chains/day statistic: grep primemeter ~/.primecoin/debug.log | awk '{s1+=$4;s2+=$6;s3+=$8;s4+=$10} END {printf"%10s: %10d\n%10s: %10d\n%10s: %10d\n%10s: %10.5f\n","Prime/h",s1/NR,"Test/h",s2/NR,"5-Chain/h",s3/NR,"Chains/day",s4/NR}' I apologize for the fact that it's an abominable one-liner. If you don't know what grep or awk are, this probably isn't for you.
|
|
|
|
Dsfyu
Member
Offline
Activity: 75
Merit: 10
|
|
August 01, 2013, 09:10:21 PM |
|
It's can't be my faul, coz I use recomended software from owner. So it's steal my ~200 XPM. It's all...
He or who think it's not fair, can correct this in any time with sending me any compensation here: AYt9xqb8vCDEQoL6W1hKxJmLwwQ6BvjFA6
Thanks in advance!
There is never a guarantee that you will get a block. Mining is mostly luck and you can get a block at any time on any computer. At the same time you can be really unlucky and not get any blocks. I started mining and in the first few days I didn't get anything. I suddenly got a block each day for three days on my desktop and haven't gotten any blocks on it in the last week. Nobody is at fault here - how is it a scam if you don't get any blocks? It all comes down to how lucky or unlucky you are - if you are lucky you can get several blocks a day on a bottom of the line cpu and if you are unlucky you could end up getting nothing for over a month. It just sounds like you have either been unlucky or made a small mistake in your configuration somewhere along the way. We all could get mad if we aren't getting blocks but it doesn't do anything for us - no matter how mad we get it doesn't change that we are all playing a game of chance by mining and nobody has a guaranteed return even if they mine a block.
|
Don't just trade, get paid to Atomic⚛Trade !!!Disclaimer: I am a noob. Assume I know nothing until proven otherwise.
|
|
|
|