Topic: [ANN] profit switching auto-exchanging pool - www.middlecoin.com - page 495. (Read 829908 times)
August 08, 2013, 02:23:36 AM
pool has been down for about an hour for me now
August 08, 2013, 02:10:24 AM
How other users is connected while we can't connect to pool?
August 08, 2013, 01:46:47 AM
down
August 08, 2013, 01:22:49 AM
pool is down?
CGminer report at least 30 minutes from now :/
CGminer report at least 30 minutes from now :/
August 08, 2013, 01:19:24 AM
i cannot connect to pool
August 07, 2013, 11:41:36 PM
i deleted the no-submit-stales arguement and now i can see a huuge rejected rate on your website when mining fast coins
August 07, 2013, 11:35:56 PM
i think that are stales.
August 07, 2013, 11:28:50 PM
Today's profits were 0.0350 BTC per MH/s per day.
Actually, it's slightly less than that, due to something I don't understand yet. The total hashrate drops, whenever our reject rate increases.
You can see it in this graph: http://middlecoin.com/hashratecharttest.html
The hashrate dips when we switch to a high block rate coin.
Here's a scatter plot, showing the relationship of the rejected percentage to the hashrate: http://middlecoin.com/rejectvshashrate.html
I'll be adding this new information into the profit calculation.
My best guess as to why this is happening is that miners are using --no-submit-stale, and the lost hashrate is all stales. But I really doubt stales would account for that much loss. So I really don't know why.
Actually, it's slightly less than that, due to something I don't understand yet. The total hashrate drops, whenever our reject rate increases.
You can see it in this graph: http://middlecoin.com/hashratecharttest.html
The hashrate dips when we switch to a high block rate coin.
Here's a scatter plot, showing the relationship of the rejected percentage to the hashrate: http://middlecoin.com/rejectvshashrate.html
I'll be adding this new information into the profit calculation.
My best guess as to why this is happening is that miners are using --no-submit-stale, and the lost hashrate is all stales. But I really doubt stales would account for that much loss. So I really don't know why.
August 07, 2013, 10:18:44 PM
giving it 1 more day. 
i got .19 today. i even upped my hash to ~8.5. still should be making at least .26 a day just ltcing.
very sad for me, when i joined the pool, nothing at all has changed whatsoever, i was hoping for too much i guess.
i got .19 today. i even upped my hash to ~8.5. still should be making at least .26 a day just ltcing.
very sad for me, when i joined the pool, nothing at all has changed whatsoever, i was hoping for too much i guess.
Did u change these values in cgminer.conf?
queue 0
scantime 5
expiry 5
You will get a ton of rejects if you don't as the pool mines alot of coins with fast block times. I dont see any difference mining coins with higher block times with those settings.
You might also want to check your ping time as it can cause rejects
I make on average around 0.13-0.17btc per day mining with 4,000kh/s
my ping is between 70-80ms.
August 07, 2013, 10:05:31 PM
giving it 1 more day.
i got .19 today. i even upped my hash to ~8.5. still should be making at least .26 a day just ltcing.
very sad for me, when i joined the pool, nothing at all has changed whatsoever, i was hoping for too much i guess.
i got .19 today. i even upped my hash to ~8.5. still should be making at least .26 a day just ltcing.
very sad for me, when i joined the pool, nothing at all has changed whatsoever, i was hoping for too much i guess.
Did u change these values in cgminer.conf?
queue 0
scantime 5
expiry 5
You will get a ton of rejects if you don't as the pool mines alot of coins with fast block times. I dont see any difference mining coins with higher block times with those settings.
You might also want to check your ping time as it can cause rejects
I make on average around 0.13-0.17btc per day mining with 4,000kh/s
August 07, 2013, 09:52:40 PM
giving it 1 more day.
i got .19 today. i even upped my hash to ~8.5. still should be making at least .26 a day just ltcing.
very sad for me, when i joined the pool, nothing at all has changed whatsoever, i was hoping for too much i guess.
i got .19 today. i even upped my hash to ~8.5. still should be making at least .26 a day just ltcing.
very sad for me, when i joined the pool, nothing at all has changed whatsoever, i was hoping for too much i guess.
August 07, 2013, 09:43:49 PM
I appreciate that you believe that they "are in fact" more profitable (I'm sure under some scenario they are), that's just not the results that I and a lot of others experience.
...
...
I definitely want to look at it.
A major flaw right now in the pool, and one that I'm currently working on, is proper reporting. While the math says that a certain coin is more profitable, I don't have any easy way to tell for sure, other than doing painstaking manual database lookups.
What I really need is a profit graph. Then I can see where it dips, and what coin we were at then.
Per your request, I have produced some graphs of your pool's mining productivity for your perusal. Please PM me for info if you are still interested.
August 07, 2013, 05:26:37 PM
h2odysee, tnx for your clear answer.
And for your pool of course, since you made it able to postpone the sale of my last 2 GPU's a bit :-)
And for your pool of course, since you made it able to postpone the sale of my last 2 GPU's a bit :-)
August 07, 2013, 05:09:05 PM
my ip changes often so i think that wouldnt work here
I can get your IP when you connect to the pool. Firewalls would be an issue though, especially with multi-rig setups. Who knows if those settings really need to be changed dynamically anyways. Probably too much work.
One could have a small batch script running that pulls the latest settings from your site and if they changed restarts cgminer...
It would be easy for you to write a small API that returns the settings in JSON from http://middlecoin.com/settings
I could easily write something that's either a bat file or something in Node.JS
August 07, 2013, 05:08:48 PM
How does hashing works?
Is it correct to state that when hashing at 1 khash/s, your device is calculating a hash every millisec? So a block time of even 1 second is no problem per se, since even a slow miner is able to produce many thousand hashes in this time span.
Network latency seems the larger problem to me then, since data transport takes up 'a lot of' millisecs and you ain't hashing useful output just before and useful data just after a new block is accepted by the network. More blocks means more hashing for nothing in between...
Is it correct to state that when hashing at 1 khash/s, your device is calculating a hash every millisec? So a block time of even 1 second is no problem per se, since even a slow miner is able to produce many thousand hashes in this time span.
Network latency seems the larger problem to me then, since data transport takes up 'a lot of' millisecs and you ain't hashing useful output just before and useful data just after a new block is accepted by the network. More blocks means more hashing for nothing in between...
Yeah, at 1 KH/s each hash takes a millisecond. If any of those hashes are below the pool "target", you get a share. If any of those hashes are below the network "target", you've found a block, and the pool gets payed.
Latency is important. Both latency from the miner to the pool, which will produce rejects, and latency from the pool to the network, which will produce orphans.
August 07, 2013, 05:02:59 PM
Shares are not discrete chunks of work like you think they are. They are hashes you find that are less than the target number.
How does hashing works?
Is it correct to state that when hashing at 1 khash/s, your device is calculating a hash every millisec? So a block time of even 1 second is no problem per se, since even a slow miner is able to produce many thousand hashes in this time span.
Network latency seems the larger problem to me then, since data transport takes up 'a lot of' millisecs and you ain't hashing useful output just before and useful data just after a new block is accepted by the network. More blocks means more hashing for nothing in between...
August 07, 2013, 04:06:04 PM
my ip changes often so i think that wouldnt work here
I can get your IP when you connect to the pool. Firewalls would be an issue though, especially with multi-rig setups. Who knows if those settings really need to be changed dynamically anyways. Probably too much work.
August 07, 2013, 04:04:04 PM
my ip changes often so i think that wouldnt work here
August 07, 2013, 03:59:14 PM
if u change e q and s what does this mean for coins like ltc and nvc ?
I would like to know this as well.
Theoretically, you guys could give the pool access to your cgminer API, and I could update your queue/expiry settings optimally whenever we switch coins.
Thats a neat idea.
August 07, 2013, 03:55:22 PM
if u change e q and s what does this mean for coins like ltc and nvc ?
I would like to know this as well.
Theoretically, you guys could give the pool access to your cgminer API, and I could update your queue/expiry settings optimally whenever we switch coins.
Jump to: