[ANN][The Original Multipool - Scrypt/SHA256/Scrypt-N/X11] multipool.us

[flound1129]

I've just run an interesting 48 hour comparison.  My mining rig runs at about 1460kh/s and I'd been dedicated mining CGB on multipool for about a week.  I was getting about a 0.05 BTC return per day return on profit snapshot.  Got a bit better when CGB went through the roof a couple of days ago.  Exactly 2 days ago I switched back to the multiport for 24 hours and my return dropped to 0.026 BTC a day.  Exactly 1 day ago I switched back to mining CGB and my return for the last 24 hours jumped back up to 0.045 BTC.

What makes this even more surprising is that the CGB exchange rate has dropped ~ 30% in the last 24 hours.  I'm getting about 2 to 3% stales exclusively mining CGB compared to up to 20% stales with the shitcoins.  LTC and NVC are about 1% stales.

Conclusion...  Too much coin switching resulting in down time and too many shit coins with high stales result in lower profitability.  

That was my problem with this pool as well.  Way to many lost shares during pool switching, disconnections almost everyday, and a massive variance in day to day payouts.  I run MultiMiner and use it to switch pools and have found it to be much more reliable in the long run than using multippol sadly.  If the disconnects and the efficiency were more predictable I'd still be mining here.

Was this on US server or EU?

Sadly I have had this problem on both servers and now have finally given up on trying to get it to not disconnect everyday several times.

The problem doesn't happen when we don't switch coins.  Hence why your rig flound had very little SS and rejects, we only switched coins a few times in the time frame you showed.  

My rig that ran for over a month (screenshot on last page) has less than 1% SS and rejects.  There were many switches in the past 18 hours, we switch to CGB on a very regular and predictable basis.  In fact the screenshot with the connection to the EU server shows a switch without any share loss or even a stale.

[skyhigh2004]

I've just run an interesting 48 hour comparison.  My mining rig runs at about 1460kh/s and I'd been dedicated mining CGB on multipool for about a week.  I was getting about a 0.05 BTC return per day return on profit snapshot.  Got a bit better when CGB went through the roof a couple of days ago.  Exactly 2 days ago I switched back to the multiport for 24 hours and my return dropped to 0.026 BTC a day.  Exactly 1 day ago I switched back to mining CGB and my return for the last 24 hours jumped back up to 0.045 BTC.

What makes this even more surprising is that the CGB exchange rate has dropped ~ 30% in the last 24 hours.  I'm getting about 2 to 3% stales exclusively mining CGB compared to up to 20% stales with the shitcoins.  LTC and NVC are about 1% stales.

Conclusion...  Too much coin switching resulting in down time and too many shit coins with high stales result in lower profitability.  

That was my problem with this pool as well.  Way to many lost shares during pool switching, disconnections almost everyday, and a massive variance in day to day payouts.  I run MultiMiner and use it to switch pools and have found it to be much more reliable in the long run than using multippol sadly.  If the disconnects and the efficiency were more predictable I'd still be mining here.

Was this on US server or EU?

Sadly I have had this problem on both servers and now have finally given up on trying to get it to not disconnect everyday several times.

The problem doesn't happen when we don't switch coins.  Hence why your rig flound had very little SS and rejects, we only switched coins a few times in the time frame you showed.  

My rig that ran for over a month (screenshot on last page) has less than 1% SS and rejects.  There were many switches in the past 18 hours, we switch to CGB on a very regular and predictable basis.  In fact the screenshot with the connection to the EU server shows a switch without any share loss or even a stale.

You said in that 18 hour window your rig was on we were mining LTC for almost half the time?  It couldn't have had to many switches if that was the case.  I know with my setup I have it set to change coins an check profitability every 5 mins.  Even though I am switching almost every 5 mins I get a much better payout with the same hash power as on multipool.  So the idea of switching coins often shouldn't affect profitability depending on the payout scheme of the pool. That said the more multipool switches the more stales/rejects I get.  That's not the case when I use separate pools rather than one that port forwards to a different pool/port.

[skyhigh2004]

How are you getting 10%?  1667/(142216+1667) = 0.0116 or about 1.16% stales, not 10%.

Edit: Oh, you're talking about SS:.  What do you have scantime set to?  Try setting it to 30.  Also try upgrading to 3.3.1.

Also I see you're using I:20.  What happens when you decrease intensity to 13?

The only problem with I set to 13 is that you are gonna cut your hashrate down by a lot depending on your card, from my testing with my 7950's it cuts it down by almost 30-35% and the stale/reject rate goes from 3-5% to 2-3%.  Not worth it at all.

I've always gotten terrible hashrates with anything over 13.

What cards do you have?

[flound1129]

How are you getting 10%?  1667/(142216+1667) = 0.0116 or about 1.16% stales, not 10%.

Edit: Oh, you're talking about SS:.  What do you have scantime set to?  Try setting it to 30.  Also try upgrading to 3.3.1.

Also I see you're using I:20.  What happens when you decrease intensity to 13?

The only problem with I set to 13 is that you are gonna cut your hashrate down by a lot depending on your card, from my testing with my 7950's it cuts it down by almost 30-35% and the stale/reject rate goes from 3-5% to 2-3%.  Not worth it at all.

I've always gotten terrible hashrates with anything over 13.

What cards do you have?

7970s

[flound1129]

You said in that 18 hour window your rig was on we were mining LTC for almost half the time?  It couldn't have had to many switches if that was the case.  I know with my setup I have it set to change coins an check profitability every 5 mins.  Even though I am switching almost every 5 mins I get a much better payout with the same hash power as on multipool.  So the idea of switching coins often shouldn't affect profitability depending on the payout scheme of the pool. That said the more multipool switches the more stales/rejects I get.  That's not the case when I use separate pools rather than one that port forwards to a different pool/port.

No I said "we" were mining it, i.e. the multiport.  The point was it's a slow coin so there wouldn't have been a lot of new blocks to cause stales like if we were on WDC or something.  However, the multiport switched coins about the normal amount of times.

[flound1129]

By the way, I'd honestly like to help you solve your issues if you want to come back.  I'm not trying to minimize or deny your issues and I do believe you.  But just saying "multipool sucks because of X, that's why I left", is not very constructive or helpful.

[skyhigh2004]

By the way, I'd honestly like to help you solve your issues if you want to come back.  I'm not trying to minimize or deny your issues and I do believe you.  But just saying "multipool sucks because of X, that's why I left", is not very constructive or helpful.

Oh believe me I never thought you were and you have always been available for any questions I have had in the past.  I don't think multipool sucks because of anything.  It's an awesome service and pool.  I just don't have the time to try and trouble shoot why my rigs work worse on this pool than others.  It was a recurring problem, stratum disconnects that plagued me.  The problem with trouble shooting it is that I am never just sitting in front of my miners when it happens and I have way to much to do to just sit there and wait for the problem to surface each day.

[bluedragon]

How are you getting 10%?  1667/(142216+1667) = 0.0116 or about 1.16% stales, not 10%.

Edit: Oh, you're talking about SS:.  What do you have scantime set to?  Try setting it to 30.  Also try upgrading to 3.3.1.

Also I see you're using I:20.  What happens when you decrease intensity to 13?

I'll try those settings for a while and let you know. Thank you.

It looks like the default scan time is 30.

Changing to I:13 for 2 hours, I had 994 accepted, 26 rejected, and 4 SS discarded, so about 2.9%. But, my hashrate dropped from a hair over 1 MH to about 632 KH. I'll experiment with the intensity more later and see if maybe I can find a happy medium.

With cgminer 3.3.1 (and I:20) for 3 hours, 2661 accepted, 20 rejected, and 124 discarded, about 5%. I'll leave this running until tomorrow and get a longer average before I change any settings.

Thanks for the suggestions, it gives me somewhere to start.

[Torn]

How are you getting 10%?  1667/(142216+1667) = 0.0116 or about 1.16% stales, not 10%.

Edit: Oh, you're talking about SS:.  What do you have scantime set to?  Try setting it to 30.  Also try upgrading to 3.3.1.

Also I see you're using I:20.  What happens when you decrease intensity to 13?

The only problem with I set to 13 is that you are gonna cut your hashrate down by a lot depending on your card, from my testing with my 7950's it cuts it down by almost 30-35% and the stale/reject rate goes from 3-5% to 2-3%.  Not worth it at all.

I have used I19 mostly and have 1-2%. 2x 7950s 680s-700s kh/s ea.
After tweaking for a few hours a day for a month approx. and documenting every little change and result I found that doing it myself gave better results than anyone else's that had ever been posted. Follow the basic setup guide as written in the scryptreadme and take your time. Read it. Read it again each time so you know what you are changing and see the results for a couple minutes with each change before saving a new conf file and tweaking some more. Keep a decent backup of your .conf file
so you can copy paste into new startups or new .conf files etc.

Set port for LTC for new setups so you can pretty much be consistent and tweak it 'til you get maximum hashrate+0 HW errors+comparable WU rate+low stales/rejects+80C or less temp+rig never crashes for any reason+you can live with noise/elect bill etc

GL!

[skyhigh2004]

How are you getting 10%?  1667/(142216+1667) = 0.0116 or about 1.16% stales, not 10%.

Edit: Oh, you're talking about SS:.  What do you have scantime set to?  Try setting it to 30.  Also try upgrading to 3.3.1.

Also I see you're using I:20.  What happens when you decrease intensity to 13?

The only problem with I set to 13 is that you are gonna cut your hashrate down by a lot depending on your card, from my testing with my 7950's it cuts it down by almost 30-35% and the stale/reject rate goes from 3-5% to 2-3%.  Not worth it at all.

I have used I19 mostly and have 1-2%. 2x 7950s 680s-700s kh/s ea.
After tweaking for a few hours a day for a month approx. and documenting every little change and result I found that doing it myself gave better results than anyone else's that had ever been posted. Follow the basic setup guide as written in the scryptreadme and take your time. Read it. Read it again each time so you know what you are changing and see the results for a couple minutes with each change before saving a new conf file and tweaking some more. Keep a decent backup of your .conf file
so you can copy paste into new startups or new .conf files etc.

Set port for LTC for new setups so you can pretty much be consistent and tweak it 'til you get maximum hashrate+0 HW errors+comparable WU rate+low stales/rejects+80C or less temp+rig never crashes for any reason+you can live with noise/elect bill etc

GL!

Yeah I also run mine at 19 mostly, a few 18 because I like my 7950s under 75c. 

[flound1129]

By the way, I'd honestly like to help you solve your issues if you want to come back.  I'm not trying to minimize or deny your issues and I do believe you.  But just saying "multipool sucks because of X, that's why I left", is not very constructive or helpful.

Oh believe me I never thought you were and you have always been available for any questions I have had in the past.  I don't think multipool sucks because of anything.  It's an awesome service and pool.  I just don't have the time to try and trouble shoot why my rigs work worse on this pool than others.  It was a recurring problem, stratum disconnects that plagued me.  The problem with trouble shooting it is that I am never just sitting in front of my miners when it happens and I have way to much to do to just sit there and wait for the problem to surface each day.

I did find one reason for the disconnects a few days ago on the EU server and hopefully fixed it.  The issue was stratum's checking of passwords, every time they would expire it would check every user's password, about 150-200, all at the same time. And it's single threaded so it blocks on every check.  

I thought I had pushed the updated DB code out to the EU server but apparently I hadn't.  The updated code caches all of the passwords in one shot (a simple select all, duh).  So that particular reason for the disconnects, at least, is gone.

[pazor]

@flound
do you plan to active CAP in the next time ?

EDIT
my question is not relevant.
CAP is disabled at cryptsy

[flound1129]

@flound
do you plan to active CAP in the next time ?

EDIT
my question is not relevant.
CAP is disabled at cryptsy

They appear to have gotten most of the issues sorted out with the new client which is pending release (1.5.0).  Once that is released and the network appears stable, I will activate CAP on the mutliport.  But not until it's back on Cryptsy.

[ozoner]

Is it just me or has profitability been *woeful* for the last few days?  My summary was just telling me .035BTC for the last 24 hours. I have 2.7mhash churning away, been getting 0.08 a day or thereabouts for the last week, before that seemed to be getting around the 0.09. 

Is it just getting shittier as BTC diff goes up exponentially?

[dolphin101]

Is it just me or has profitability been *woeful* for the last few days?  My summary was just telling me .035BTC for the last 24 hours. I have 2.7mhash churning away, been getting 0.08 a day or thereabouts for the last week, before that seemed to be getting around the 0.09. 

Is it just getting shittier as BTC diff goes up exponentially?

Yeah, it has been rather disappointing to see the stats from the recent days.. more than just a few days.  I guess that's what we have to come to accept with this game/business.

By the way, I'm sure you're aware already Flound, but it seems the front-end is having database service issues:

Lost connection to MySQL server at 'reading initial communication packet', system error: 0

[Maniac]

Is it just me or has profitability been *woeful* for the last few days?  My summary was just telling me .035BTC for the last 24 hours. I have 2.7mhash churning away, been getting 0.08 a day or thereabouts for the last week, before that seemed to be getting around the 0.09. 

Is it just getting shittier as BTC diff goes up exponentially?

Income dropped very much in recent days.

[Jcw188]

Is it just me or has profitability been *woeful* for the last few days?  My summary was just telling me .035BTC for the last 24 hours. I have 2.7mhash churning away, been getting 0.08 a day or thereabouts for the last week, before that seemed to be getting around the 0.09. 

Is it just getting shittier as BTC diff goes up exponentially?

Yeah, it has been rather disappointing to see the stats from the recent days.. more than just a few days.  I guess that's what we have to come to accept with this game/business.

By the way, I'm sure you're aware already Flound, but it seems the front-end is having database service issues:

Lost connection to MySQL server at 'reading initial communication packet', system error: 0

front end problems for me for an hour or two now

[zepadee]

When trying to load website multipool.us:

Lost connection to MySQL server at 'reading initial communication packet', system error: 0

[zepadee]

I have a couple of suggestions (even if just temporary to try-it-out) and would value feedback:

1. Remove LTC and NVC from the Multipool.

2. Leave LTC, NVC as PPLNS

3. Change all the other Scrypt coins to PPS or PROP (or something similar).

I think this would increase profits dramatically.

[belltown]

Is it just me or has profitability been *woeful* for the last few days?

Something's going on with the pool. My 390 kH/s should produce about 0.01 btc / day if I mine LTC. On multiport I'm getting 0.007 btc - 0.006 btc a day recently. Since we do have LTC on multiport and we do mine LTC, our profitability can't be lower then just mining LTC all day.

Found explains this that we were extremely unlucky. This sounds reasonable, and I'm perfectly fine with having some unlucky days. But this means that some other days should be extremely lucky. If we can get historical data that can show that these extremely lucky day exist too this would put the issue of bad profitability to the rest.