Author

Topic: [POOL][Scrypt][Scrypt-N][X11] Profit switching pool - wafflepool.com - page 144. (Read 465716 times)

newbie
Activity: 52
Merit: 0

Did something new happend? Why are we seeing this kind of value crash?

Nothing is crashing, the value is going down, then it goes back up. Please, do some research on what a crash is, and then look at how [un]stable cryptocoins have been. People sell in mass quantities, which affect the value, people mine in mass quantities, etc..

Now is the time to buy bitcoins since it's low.
full member
Activity: 129
Merit: 100
Whoa...
I have been out a few days in work, and have returned...

I have auto-worked my farm, but after i analise the data, is just me, or the value of the crypto coins, have plunged?
The profitability is really on the line of water (0.005 per 1 Mh for the KWh that is needed to mine it).

Also BTC is loosing value really fast! 556 Dolars?

Did something new happend? Why are we seeing this kind of value crash?

In my case if the value lowers to 0.004 i will shut down the farm, and wait for the coins to recover some value...

Best Regards,

LPC
newbie
Activity: 1
Merit: 0
Is it just me whose stats have flatlined for the last 7h or so? My miner still reports shares being accepted and my Wafflepool stats page indicates 0khs submitted since 1:00AM EST

I have had the exact same thing!!!  What is going on Wafflepool?  My miner was still hard at work but luckily I opened the Wafflepool stats page and noticed that my reported hashrate was 0.00khs for the past 9.5 hrs or so.  I have reported shares according to my miner but not according to Wafflepool.  Has anyone else had this experience?
newbie
Activity: 6
Merit: 0
mine did the same thing at the same time
newbie
Activity: 5
Merit: 0
Is it just me whose stats have flatlined for the last 7h or so? My miner still reports shares being accepted and my Wafflepool stats page indicates 0khs submitted since 1:00AM EST
full member
Activity: 168
Merit: 100
Quote
author=comeonalready

And it is payout per MHD!

I see you insist... Ok. Let me show you my reasoning for why IT IS NOT MHD and then you can just slam down your irrefutable proof and I'll stand rebuked.

let's say that your hashrate is 1 MHs. Meaning that your computational power can "solve" 1 million hashes in a second. Analogous to active power being measured in kW, the energy consumption is measured based on the consumption of power in a unit of time thus the kWh unit of measure. When you want to see how much energy you consumed in a DAY you just count the kWh which means you consumed 24 kWh/day (for 1 kWh).

when you use BTC/MHD you are implying that your hash rate is 1 "MH per day" which is false. your hash rate is an average of 1 MHs over a day's time and you contributed with 3600* 1 MH in a day's time. WP states [0.01 btc/(average MHs) in a day] and not the amount of hashes in a day. And lastly, the unit of measure is MHs. you can twist that figure to show a day or a year but it's still MHs as reported by your miners.


BTC/Day      BTC    s       1 Day        BTC
--------  =  --- x ---  x  -------  =  --------
1MH / s      Day   1MH     86400 s     86400 MH


For convenience I suggested that we create a unit named MegaHashDay (or MHD) to equal 86400 MH, but that has proven to be anything but convenient.  So let's call it a Thump instead, as that is the sound you hear when you bang your head against a wall.  Until you hear nothing at all that is...

BTC / Thump



Doesn't that prove it is BTC/MH*D? The point being the D is not in the lower part of the fraction...

Has no one here taken middle/high school level math classes and actually passed them?  For an answer to your question, please refer to www.mathisfun.com.

Basic math? lol...

So you're saying 5/(5*5) = 5/5*5? If so, sorry for even wasting your time because you're lost. :p


And as for zSprawl, on his order of operations argument and retarded analogy proving absolutely nothing...

You are correct that a specific order of operations in the denominator would be necessary if the denominator still contained an irreducible operation.  But what you failed to realize is that both Day in the numerator of the larger fraction and s in the denominator of the larger fraction are both units of time in different scales, and 1 Day always equals 86400 seconds.  So either time unit contained in the denominators of the smaller fractions can be rewritten to share a time scale with the other, and the larger fraction can be further reduced to a point at which there is no operation remaining its denominator because time can be factored outside of it, hence order of operation restrictions would no longer apply as there are no operations remaining in the denominator of the larger fraction.  Do it if you don't believe me because I know you won't want to.



As I have not heard back from zSprawl, I will assume that he simply convinced himself that he was right and the rest of the world is dumber than him.  And as I know the rest of you are dying to pick this up again, I will show you all what he missed (though I think a lot of you already understood perfectly.)  Admittedly, I did purposefully present it the way I did earlier in order to get someone to fall into that order of operations argument trap, as it is usually much more fun that way!


The original unit expression of daily value is shown here:


 BTC  
 ---  
 Day  
=======
 1MH  
 ---  
  s  



Notice how at first glance it appears to be reduced to its most simple form, but if you examine it closer you will notice that it includes two different time scales in the denominators of both the upper and lower fractions,  one of which can be converted to the other, as 1 Day = 86400 seconds.  After conversion it looks like this:


  BTC  
 -------
 86400 s
=========
  1MH  
  ---  
   s    



Then just multiply the entire expression by 1, which we can choose to represent as ((86400s/1) / (86400s/1)):


 BTC          86400 s         BTC                
-------      -------         ---            BTC  
86400 s         1             1                  
=========  x  =========  =  =========   =  =========
 1MH          86400 s       86400MH              
 ---          -------       -------        86400MH
  s             1             1                  


Because I recognized that this reduction was possible earlier, but did not demonstrate it visually, I was able to ignore order of operations for division, because there are no divisional operators in either the numerator or denominator in the expression's most reduced form.

In an effort to be perfectly clear, this is not to suggest 1 BTC / 86400 MH, but it is only the proper unit name for the variable amount of value paid in BTC for 86400 MH generated daily by a 1 MH/s miner.  Earlier I had suggested that we call 86400MH a MegaHashDay, or MHD for short, but it is obvious no one wants to do that.

And in recognizing that I am not perfect, if anyone finds a problem with any of this, please do let me know.  But do not try to make your case with a false analogy.
full member
Activity: 168
Merit: 100
Too short a time testing but looks like new switcher working Smiley ... gaining profitability Smiley Good work PW.

You admit to having too little data to make a statement of fact, but then you proclaim the new switcher is working anyway?  I don't get it.  We'll know when we know.  And that will take time to gather a proper sample set size.
hero member
Activity: 630
Merit: 500
Too short a time testing but looks like new switcher working Smiley ... gaining profitability Smiley Good work PW.
Qxw
full member
Activity: 203
Merit: 100
GPUs GAME OVER

<0.005 BTC/Day/Mh

GOOD BYE

GPU mining is not at all over but perhaps soon with ordinary Scrypt.
But it need know what to with GPU's.

But if someone know where is free gold to pick up - why tell it to others how to find it?



full member
Activity: 168
Merit: 100
пoгoвopкa - кoпeйкa pyбль бepeжeт, нe знaю кaк y вac.
sorry, left

I'm going to take a wild stab at it and suggest that this might be an idiomatic expression similar to "every penny counts", but I'm really not sure.

Anyone here who can translate properly?

Update: I was close.  He is right to a degree, as if the pool were able to exploit every small opportunity, they all might add up to something more significant.  But as each new coin daemon and trading market creates another possible point of failure and additional component to manage daily, combined with the propensity of many coins to lose all value and leave miners with nothing to show for their efforts, we should leave the discretion to poolwaffle to act in the best interest of the pool.  He has shown himself to be very responsible overall.  If he fails to maintain a decent level of profitability, we are all free to try other pools if we think we can do better elsewhere.

sr. member
Activity: 411
Merit: 250
A penny saved is a penny earned.
sorry.
full member
Activity: 168
Merit: 100
sorry do not know English. Google helps

Coming soon forks only for video cards (Asic stable) and it should be considered in the development of a pool.

The pool has no way of knowing if a user is an ASIC, a GPU, or some guy manually writing down numbers and sending them in...

Yes. we need to specify how we work, what is important for the development of the basin. If not specified, then work on a simple Scrypt, while others may include innovative Scrypt.

He his trying, so I deleted my previous message which I hope did not offend him.  But have you considered registering the name wafflebasin.com?
sr. member
Activity: 322
Merit: 254
Fluttercoin (FLT)
Network Hashrate: 4.19 GH/s

And again, if we literally mined _every_ last coin, we would increase our daily intake by 1.5btc (1%).
sr. member
Activity: 411
Merit: 250
Fluttercoin (FLT)
Network Hashrate: 4.19 GH/s
sr. member
Activity: 411
Merit: 250
sorry do not know English. Google helps

Coming soon forks only for video cards (Asic stable) and it should be considered in the development of a pool.

The pool has no way of knowing if a user is an ASIC, a GPU, or some guy manually writing down numbers and sending them in...

Yes. we need to specify how we work, what is important for the development of the basin. If not specified, then work on a simple Scrypt, while others may include innovative Scrypt.
sr. member
Activity: 322
Merit: 254
sorry do not know English. Google helps

Coming soon forks only for video cards (Asic stable) and it should be considered in the development of a pool.

The pool has no way of knowing if a user is an ASIC, a GPU, or some guy manually writing down numbers and sending them in...

Why is my reported hashrate so low?  Haven't you been receiving my letters via postal mail?

I have, but your chicken-scratch takes a while to verify.  Plus I make a lot of typos when punching them in...
full member
Activity: 168
Merit: 100
sorry do not know English. Google helps

Coming soon forks only for video cards (Asic stable) and it should be considered in the development of a pool.

The pool has no way of knowing if a user is an ASIC, a GPU, or some guy manually writing down numbers and sending them in...

Why is my reported hashrate so low?  Haven't you been receiving my letters via postal mail?
sr. member
Activity: 322
Merit: 254
sorry do not know English. Google helps

Coming soon forks only for video cards (Asic stable) and it should be considered in the development of a pool.

The pool has no way of knowing if a user is an ASIC, a GPU, or some guy manually writing down numbers and sending them in...
sr. member
Activity: 411
Merit: 250
sorry do not know English. Google helps

Coming soon forks only for video cards (Asic stable) and it should be considered in the development of a pool.
sr. member
Activity: 322
Merit: 254
So, I made some major changes to our profitability switcher a couple hours ago.

Short synopsis is that it more accurately gauges the amount of hash power is on each individual section of the pool, and assigns them more appropriately to various coins.  It should end up being a bit more aggressive on small coins than it was before (and more accurate).  Previously for efficiency, it was treating all segments of the pool as static sizes (we have 24 switchable servers, so each was counted as 1/24 of the pool), this was just meant to be an estimate, and only really became a problem when our servers got horribly lopsided (mostly a few days ago when we switched to the new stratum servers).  Pool is split roughly: 60% usw, 25% use, 14% eu, 1% sea.  Which meant any time we switched use/eu, everything worked out pretty correctly, but when sea/usw got switched, we'd see higher orphan rates than we wanted (or less blocks than we'd want).

The other major switch is that we now switch pieces of the pool that match up closest with what we're mining.  If our switcher says "We need 2GH on coin X", it was previously randomly assigning segments of the pool (again, we counted them as even), but now tries to find the right combination of servers to switch to closest match the goal.

Ideally this means a bump in profitability, and so far I've seen a significant bump over the last 2 hours, however, its damn near impossible to tell if this is based on a better script, or just random luck (which is the next major upgrade - tracking luck).  So we'll see as the day progresses and luck evens itself out.
Jump to: