[1050 TH] BitMinter.com [1% PPLNS,Pays TxFees +MergedMining,Stratum,GBT,vardiff]

[psilan]

The server is running very smoothly now. We had 1.8 TH/s earlier today and the server load was pretty low. Sorry for the daily restarts and sometimes high response times the last couple days. Hopefully it will be smooth sailing now. It is certainly looking pretty solid.

Suggestion: Add a clock to the website. Local server time.

Not a bad idea. Is it annoying to have one ticking away at the top of the page?

I suppose better might be to display the timestamps in a timezone chosen by the user, but that would take a bit more work.

Just a digital one with minutes, no seconds. Same colour as your twitter/facebook/etc text. 

No timezone, people are on a computer, they know what time it is.

[WhitePhantom]

I suppose better might be to display the timestamps in a timezone chosen by the user, but that would take a bit more work.

+1 to user customizable timezone so timestamps on shifts and blocks show up as each user's local time.  Just a nice feature for someday, not critical.

[miter_myles]

I suppose better might be to display the timestamps in a timezone chosen by the user, but that would take a bit more work.

+1 to user customizable timezone so timestamps on shifts and blocks show up as each user's local time.  Just a nice feature for someday, not critical.

+1 on user customizable timezone   

[SchmalzTech]

I got a suggestion from PsychoticBoy to change the N in PPLNS from 2x difficulty to 4x difficulty. That would be to double the size of the shifts. Please speak up if you have an opinion on it.

Currently 10 shifts take about 5 hours. Doubling shift size would mean 10 shifts take 10 hours at the current pool hashrate. This would mean it takes longer before a proof of work is fully paid, but also that the variance for a proof of work goes down. 24/7 miners shouldn't notice much, but those who don't mine 24/7 should experience reduced variance.

In other news the testing on port 9000 helped uncover a bottleneck that has now been fixed. A big thanks to all who are mining there to help with testing. The test is still running. I'll try and finish up what will hopefully be the next production version of the mining backend, let it run on the test port for a bit, then bring it over on the regular port.

Being a miner who doesn't mine 24x7 always, I like watching the BTC roll in shortly after I fire up my GPUs - and as I don't pay attention after they're shut down, I would rather see my rewards as I am mining. I would like the "N" to remain the same.

[drekk]

I suppose better might be to display the timestamps in a timezone chosen by the user, but that would take a bit more work.

+1 to user customizable timezone so timestamps on shifts and blocks show up as each user's local time.  Just a nice feature for someday, not critical.

+1 on user customizable timezone   

+1

Also, the Thps counter in the website header still says "Ghps".

And I've always wondered why there's no "cash out now" button, so I have to adjust auto-pay options. Sometimes I'd like to get small amounts earlier.

[DrHaribo]

Also, the Thps counter in the website header still says "Ghps".

Even after clearing the cache in the browser?

And I've always wondered why there's no "cash out now" button, so I have to adjust auto-pay options. Sometimes I'd like to get small amounts earlier.

That's on my TODO list.

[drekk]

Also, the Thps counter in the website header still says "Ghps".

Even after clearing the cache in the browser?

That's probably it. Can't verify ATM, cause server is giving error:

Code:

Proxy Error

The proxy server received an invalid response from an upstream server.
The proxy server could not handle the request GET /members/.

Reason: Error reading from remote server

And I've always wondered why there's no "cash out now" button, so I have to adjust auto-pay options. Sometimes I'd like to get small amounts earlier.

That's on my TODO list.

Yay! You're cool.

~drekk~

[miter_myles]

site down?  

nm, back up now

[WhitePhantom]

The site's down, but my miners are still running fine.

[DrHaribo]

The site's down, but my miners are still running fine.

Back up again. There's a problem with the web server. It locks up randomly with no error message and becomes completely unresponsive. So it's a bit difficult to figure out what the problem is. I'll keep a watch on it and see if I can find out what's going on. Sorry for the instability.

[WhitePhantom]

The site's down, but my miners are still running fine.

Back up again. There's a problem with the web server. It locks up randomly with no error message and becomes completely unresponsive. So it's a bit difficult to figure out what the problem is. I'll keep a watch on it and see if I can find out what's going on. Sorry for the instability.

You're the man Doc.  Your efforts are appreciated by us all.

[loshia]

The site's down, but my miners are still running fine.

Back up again. There's a problem with the web server. It locks up randomly with no error message and becomes completely unresponsive. So it's a bit difficult to figure out what the problem is. I'll keep a watch on it and see if I can find out what's going on. Sorry for the instability.

You're the man Doc.  Your efforts are appreciated by us all.

+1

[DrHaribo]

Thanks, guys

Sorry, had to restart the mining backend just now. A memory leak is causing slow response after it's been running a couple of days.

I'll be working on that memory leak today, and also the issue with the website locking up.

[squid]

Can't wait for ASICS so I can park them on this server

[willphase]

Thanks, guys

Sorry, had to restart the mining backend just now. A memory leak is causing slow response after it's been running a couple of days.

I'll be working on that memory leak today, and also the issue with the website locking up.

perhaps worth just setting the frontend to reboot every so often until you resolve the issue - it seems to go down quite a lot.

Will

[DrHaribo]

Can't wait for ASICS so I can park them on this server

Something tells me I better get the server ready for some big miners. 

perhaps worth just setting the frontend to reboot every so often until you resolve the issue - it seems to go down quite a lot.

I fixed the memory leak in the mining backend. Hopefully it can sit there for a while now without requiring any more restarts or work.

Made some changes just now to the web application as well. Hopefully it will fix the issue with it locking up.

If there is still a problem I'll have a look at writing a script to detect when the website is unresponsive and automatically restart it.

[hahahafr]

Can't wait for ASICS so I can park them on this server

Something tells me I better get the server ready for some big miners. 

perhaps worth just setting the frontend to reboot every so often until you resolve the issue - it seems to go down quite a lot.

I fixed the memory leak in the mining backend. Hopefully it can sit there for a while now without requiring any more restarts or work.

Made some changes just now to the web application as well. Hopefully it will fix the issue with it locking up.

If there is still a problem I'll have a look at writing a script to detect when the website is unresponsive and automatically restart it.

Was the memory leak coming from the 0.7 bitcoind daemon?

[Fortega]

I'm currently having a problem with the client:

Everything looks fine, I'm mining at a normal rate, and suddenly a popup comes up, saying 'wrong username or password'. I press ok, and everything goes back to normal.
A few minutes later, this repeats...

Anybody else with this problem? What can I do? Strange thing is the password is not wrong, as I just press ok and the mining continues (for about 5 mins)


Logs:
2012.10.02 [11:46]  Warning - slow network or server. Request took 52 sec.
2012.10.02 [11:46]  Work rejected. Server says: Duplicate proof of work
2012.10.02 [11:46]  Warning - slow network or server. Request took 43 sec.
2012.10.02 [11:46]  Warning - slow network or server. Request took 66 sec.
2012.10.02 [11:46]  Work rejected. Server says: Stale proof of work
2012.10.02 [11:46]  Warning - slow network or server. Request took 68 sec.
2012.10.02 [11:46]  Work rejected. Server says: Stale proof of work
2012.10.02 [11:48]  Warning - slow network or server. Request took 22 sec.
2012.10.02 [11:50]  Request failed: bad credentials

[DrHaribo]

Was the memory leak coming from the 0.7 bitcoind daemon?

No, it was my own code. I reworked the data structures to increase parallelism. Accidentally ended up with proofs of work being kept in memory indefinitely. After a couple days the mining backend was lugging around 3.7 GB of proofs of work.

Everything looks fine, I'm mining at a normal rate, and suddenly a popup comes up, saying 'wrong username or password'. I press ok, and everything goes back to normal.
A few minutes later, this repeats...

Hmm, I only see one failed login from you in the server logs, at 2012-10-01 11:51:05 UTC, which is 22 hours ago as I write this.

Did you change password on a worker recently?

Does it help if you shut down the client and start it fresh again?

[abeaulieu]

... the mining backend was lugging around 3.7 GB of proofs of work.

That's a lot of proof...