[5gh/s]Bitcoinmonkey.com(3BTC Bonus for current block, no fees, API, LP, Full 8)

[bitcoinaddict]

Alright, I added Worker Totals.  For some reason the total MH/s for all workers was looking artificially low, and I suck at math, so I left it out for now.  Also fixed it so that it will still display your shares and stales even if your worker is idle.  The only way you know it's idle is when it says "0 MHashes/s".  I will style that page later on to make it more obvious a worker is idle.  Also, SMS notification of idle workers is on the to-do list, maybe with a small donation % required for the feature, something bitcoinaddict and I have been talking about.

I've noticed this about the worker mh/s rate.  I think it has to to with just random luck, because you may submit a share once every so many seconds with a worker, and lets say in one five minute period you submit 50 shares, but in the next 5 minute period you submit 45 shares, and then after that the next 5 minute period you submit 55 shares.  So in that case you could show anywhere from 95-105% of what you are actually submitting.  I don't know if the variance for a single miner can be that high, I would think it is rather constant, but with network communications involved also, that may be the reason the value fluctuates.  I don't know enough about the technical inner-workings of bitcoin to figure all of that out...

[1715119068]

1715119068

[1715119068]

1715119068

[d3c0n808]

Alright, I added Worker Totals.  For some reason the total MH/s for all workers was looking artificially low, and I suck at math, so I left it out for now.  Also fixed it so that it will still display your shares and stales even if your worker is idle.  The only way you know it's idle is when it says "0 MHashes/s".  I will style that page later on to make it more obvious a worker is idle.  Also, SMS notification of idle workers is on the to-do list, maybe with a small donation % required for the feature, something bitcoinaddict and I have been talking about.

I've noticed this about the worker mh/s rate.  I think it has to to with just random luck, because you may submit a share once every so many seconds with a worker, and lets say in one five minute period you submit 50 shares, but in the next 5 minute period you submit 45 shares, and then after that the next 5 minute period you submit 55 shares.  So in that case you could show anywhere from 95-105% of what you are actually submitting.  I don't know if the variance for a single miner can be that high, I would think it is rather constant, but with network communications involved also, that may be the reason the value fluctuates.  I don't know enough about the technical inner-workings of bitcoin to figure all of that out...

Could the interval at which it updates the speed be increased from x ammount of seconds to something a little more stable like 20 minutes or even a half an hour?  Sorry I've been moving so I had to take down all my miners for a day to move them to our new location.  Back up since last night going full blast haha.  Looking good I like how you updated the active workers,

[phorensic]

The worker MH/s are OK and on par with how other pools calculate, it was when I tried to add all the worker speeds together I ran out of programming talent, hehe.  I think if I calculated the average over 30 minutes the speed would be lower actually.

Funny, one of my friends in the pool was moving to a new house also.  And during that period my computer at home crashed while I was at work and I don't have remote power cycle capabilities on it, dangit.  Pool speed starting to look better.  Still trying to get my friend's two 6870's stable.

[d3c0n808]

The worker MH/s are OK and on par with how other pools calculate, it was when I tried to add all the worker speeds together I ran out of programming talent, hehe.  I think if I calculated the average over 30 minutes the speed would be lower actually.

Funny, one of my friends in the pool was moving to a new house also.  And during that period my computer at home crashed while I was at work and I don't have remote power cycle capabilities on it, dangit.  Pool speed starting to look better.  Still trying to get my friend's two 6870's stable.

Hahahaha At least I made sure I had the internet switched over before I moved them.  I run a proxy so I can switch pools at the drop of a dime.  Getting cards stables is time consuming.  Took me couple days to figure out how to edit my bios and to find what settings are stable(have to flash bios because I all the miners are linux)  set it and forget it!

[bitcoinaddict]

I think the shorter you average the worker stats the better so you can pick up on lost miners more quickly.  If you average it out over 30 minutes, that's thirty minutes to 0!  If it's averaged over five you can tell if you have problems sooner.

[phorensic]

Good point, I didn't even think about it that way.

[bitcoinaddict]

Good point, I didn't even think about it that way.

It would be nice if we could average out how long a worker takes to submit a single share, add 20% to it, and do an alert system based off of that.  But that's probably way more difficult.

[d3c0n808]

1.4 Million shares, come on monkeys lets find this block before the difficulty increase! hahaha Gl

[phorensic]

Long round is making this monkey very angry.  We've already lost some hashrate to pool hoppers, grrr.

Reminder:  You can't win the bounty if you pool hop!  You have to submit the winning share that finds the block.

[bitcoinaddict]

Well we were VERY lucky on our first two blocks, so this kind of makes up for it. We've just barely hit the average.

[phorensic]

Well we were VERY lucky on our first two blocks, so this kind of makes up for it. We've just barely hit the average.

That's the Truth Truth!

[phorensic]

Just got done doing some major performance upgrades to the software on the server.  We were only down for about 15mins (phew!).

• do-release-upgrade to Ubuntu Natty Narwhal
• increased ext4 commit time
• custom compiled bitcoind v0.3.24 + pool patches by Joel Katz
  

The release upgrade (+kernel) and commit time increase was to fix a kernel bug that was causing constant writes to the storage.  The custom complied bitcoind is for performance increases and provisioning for major scaling.  I will be monitoring the server for the next few hours.

Update:  Went a little more aggressive on the ext4 tuning and it helped a ton.  Not so much immediate performance, more for future scalability.

[bitcoinaddict]

Site is definitely faster!

[phorensic]

Amazing what 8 hours of tuning a mysql database can get you, lol.

Mr. 80.243.158.233, your hacking attempts at my Apache install are hilarious.  I do not run phpmyadmin and your message you leaving in my logs is interesting "w00tw00t.at.blackhats.romanian.anti-sec".

Update 7/23/2011 @ 8:36PM PST:  Woohoo! Our first DDoS attack!  Pretty weak attack on Apache port 80 only, but fun to watch nonetheless.  Only 10 unique IP's so far.  Is that all you got?  

Update 7/25/2011 @ 8:40AM PST:  Source of "DDos" identified as BitHopper project hammering the main page for stats.  Working on JSON feed to solve the problem.  If you are a BitHopper user, please stop pointing your software at our main page for stats refreshes every 2 seconds.  I will unblock IP's as soon as this is all sorted out.

Update 7/25/2011 @ 12:41PM PST:  Created JSON api for pool stats at https://bitcoinmonkey.com/json/api.php.  Please point your bitHopper script at this URL instead of the main page.  I will start to slowly unblock IP's that were hammering our main page.

[bitcoinaddict]

This block is killing me, larry

STILL A 3 BTC BONUS FOR THE NEXT BLOCK!!!

[d3c0n808]

no bonus for 2nd block that was found?

[phorensic]

no bonus for 2nd block that was found?

Yeah there was.  It was paid out already.

[d3c0n808]

so then

This block is killing me, larry

STILL A 3 BTC BONUS FOR THE NEXT BLOCK!!!

is actually a 2 btc bonus correct?

[phorensic]

Hehe, no I paid $20 in BTC for block #1.  I guess you could call it block #0?  Bitcoinaddict put up bounties for the blocks after that.

[d3c0n808]

ah ok no just wondering