Just rented a new box for our sql server. Should perform about 8x better, plus not share resources with pushpool/nginx/php/memcache.
|
|
|
Siplecoin here is a feature request: -add an api so that an application could create an new worker when he wants(for example you have 5 computers and you want to create an application that when it's run on that computer it will automatically create an new username+password from that computer+link it to you're account, for example that worker to be linked to my account or so)&retrive them from the server.Or if i'm mining with 2 pcs and using the same username+password is there any problem?or this would work to?
While the idea sounds great, it's also seems like it might add an exploit. However, you can use the same miner name/pass on multiple workers.
|
|
|
Can you look at the webserver. I am getting a lot of timeouts (504 errors).
The pool seems okay though.
Yeah, php-fpm is hanging up, I may go back to php-fastcgi Ok, swapped. let's see how it does now UPDATE: switched back, that was worse. I'll dig for the bottleneck.
|
|
|
For anyone who wants a silent box I modified this to adjust fan speed as a second priority to speed. As well as a few display tweaks
FYI, I saw issues with executing pplib commands while mining. Occasionally, the hash rate would drop ~20% on one of the adapters, then recover. There seems to be some interaction between phoenix and aticonfig that I haven't had time to dig into. I've seen that as well, when pushing the mhz wall (usually get a few bad shares at that speed too). However, I'm running this script with cgminer and 4x6870s, there are tiny, quick dips in hashrates but usually only when overheating. I'd rather turn up the fans and have a 1sec dip then downclock as a priority. I use it and have no issues, so I shared YMMV
|
|
|
For anyone who wants a silent box I modified this to adjust fan speed as a second priority to speed. As well as a few display tweaks #!/bin/bash #version 0.011
TARGETTEMP=81 TARGETFAN=60 MAXFAN=80 MAXCLOCK=960
# Get number of adapters export DISPLAY=:0 num=`aticonfig --adapter=all --odgt | grep Temperature | wc | awk -- '{ print $1 }'`
# Set all adapters to maximum clock speed for (( i=0; i<$num; i++ )) do export DISPLAY=:0.$i aticonfig --od-enable aticonfig --odsc=$MAXCLOCK,0 --adapter=$i aticonfig --adapter=$i --pplib-cmd "set fanspeed 0 $TARGETFAN" done
# while true; do sleep 10 clear date
for (( i=0; i<$num; i++ )) do echo ">>>>>> Adapter $i <<<<<<" export DISPLAY=:0.$i
# Collect current clock speed/temperature curtemp=`aticonfig --adapter=$i --odgt | grep "Sensor 0:" | tr -s ' ' | cut -f 6 -d ' ' | cut -f 1 -d '.'` curclk=`aticonfig --adapter=$i --odgc | grep "Current Clocks"|tr -s ' '|cut -f 5 -d ' '` curfan=`aticonfig --pplib-cmd "get fanspeed 0" | grep "Fan Speed:" | tr -s ' '|cut -f 4 -d ' '|cut -f 1 -d '%'`
# Status echo "clock:${curclk}, Temp:${curtemp}C, Fan:${curfan}%" # Lower clock if too hot, raise clock if to slow if [ "$curtemp" -gt "$TARGETTEMP" ]; then if [ "$curfan" -lt "$MAXFAN" ]; then echo "Over target temperature, speeding up fan" let "curfan += 5" aticonfig --adapter=$i --pplib-cmd "set fanspeed 0 $curfan" > /dev/null else echo "Over target temperatre, lowering clock speed" let "curclk -= 1" aticonfig --adapter=$i --odsc=$curclk,0 > /dev/null fi elif [ "$curtemp" -eq "$TARGETTEMP" ]; then echo "Adapter is at target temp" elif [ "$curclk" -lt "$MAXCLOCK" ]; then echo "Adapter can run faster, speeding it up" let "curclk += 1" aticonfig --adapter=$i --odsc=$curclk,0 > /dev/null else if [ "$curfan" -gt "$TARGETFAN" ]; then echo "Lowering fan speed" let "curfan -= 1" aticonfig --adapter=$i --pplib-cmd "set fanspeed 0 $curfan" > /dev/null else echo "Adapter is at optimal targets" fi
fi echo " " done done
|
|
|
1) Let's find a block soon!
2) Can you make the monthly hash history chart always go for the last 30 days to today? It looks funny to have the most recent day be at the beginning of the chart.
1) Agreed! 2) Yes, it always bothered me too
|
|
|
Any reason that you can see that the server load indicator seems to randomly move between high, mid, and low?
Yes, it's almost realtime. whenever a huge mysql query or new block loads up the processor for a second or two it captures the stressed load. That said, I need to recalibrate what I consider low/mid/high/critical. Currently critical doesn't even cause site or pool lag. Also, got my new miner, aka beast online. tuning it now for speed and sound. Using the auto-temp clocking script to ensure max hashrate.
|
|
|
That said, I've posted a discussion on the simplecoin forum if anyone wants to weigh in there.
I wish you didn't have to log into simplecoin and then log in again to the forum I understand... That said... I'm close to pulling the trigger on a bigger server. I'm trying to figure out the best way to handle the load. Migrate sql or pushpool/bitcoin to the box with more cores... which will benefit more... On on hand mysql could run more efficiently, on the other pushpool/bitcoin might announce slightly faster and require zero downtime.. I may just hang on to the older server for the forums, menial tasks and backups.
|
|
|
Looks like my godaddy dns server just took a dump....
Use 74.117.57.70 if you cannot resolve simplecoin.us.
I have a ticket in, but I'm not sure what godaddy's response time is.
|
|
|
So, going forward: It seems the cheat-proof method is no longer the payout-method du jour.
Would anyone prefer Max-PPS, or PayPerLastNShares to the current implementation?
*MPPS is a terrible method. PayPerLastNShares is much better, and cheat-proof, so I would prefer that! The only downfall to maxpps I see is slower payout and a larger balance in the site wallet. That said, I've posted a discussion on the simplecoin forum if anyone wants to weigh in there.
|
|
|
So, going forward: It seems the cheat-proof method is no longer the payout-method du jour.
Would anyone prefer Max-PPS, or PayPerLastNShares to the current implementation?
|
|
|
More behind the scenes tuning. Website response just keeps getting better.
I'd still like to move the main sql server off the website/pool/btc server, but that would be about 15-30 minutes downtime.
|
|
|
Another 1BTC bonus for the next round!
|
|
|
Join us / me at IRC and i possible can help you optimize some queries.
Thanks, I'll take you up on that soon. Gotta get some sleep now though.
|
|
|
I thought my replication server could handle the load of stats. Since it can't, I think I'm going to up the processor 8x. In fact, I may just upgrade all the servers...
So yes, the site is timing out, pool is still up.... I'll have it up again shortly.
UPDATE: It's up. Bonus 2btc paid sent!
|
|
|
I just refreshed the stats page, and my round shares dropped from 300,000+ to 189,892!?! And, stales went from 2% to 3.3% What's up with that? Edit: Now my lifetime shares dropped from 444,000ish to 328,000!!! Congrats on the block! any chance you deleted a worker? That should be the only way to lose shares currently. If you remake the worker you will see them again.
|
|
|
Nothing I can do there except remove the mtgox rate.
Memcache it so you don't have to request it all the time, and set request timeout to 0.5s and no-one would notice. Hell, that goes for all stats. It is, and they are But the cache only saves on success. I may change that for the mtgox.
|
|
|
Let's find a block this weekend!
Yes please! Better yet, find 2 or 3 Also, my quad box is finally shipped after some issues with the seller.... but 4x6870s on the way.
|
|
|
bitcoin upgraded.
Also, current slow page loads are caused by mtgox api timeouts. Nothing I can do there except remove the mtgox rate.
|
|
|
Looks like a script kiddie is trying to mess with the pool. Thankfully the only thing that should be affected is the website requests timing out.
If your account is banned, don't forget you can use password recovery to unban it with an email.
|
|
|
|