Author

Topic: [1050 TH] BitMinter.com [1% PPLNS,Pays TxFees +MergedMining,Stratum,GBT,vardiff] - page 282. (Read 837122 times)

hero member
Activity: 938
Merit: 501
Can't wait for ASICS so I can park them on this server Cheesy

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

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?
legendary
Activity: 2730
Merit: 1034
Needs more jiggawatts
Can't wait for ASICS so I can park them on this server Cheesy

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

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.
hero member
Activity: 767
Merit: 500
Thanks, guys Smiley

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
member
Activity: 112
Merit: 10
Can't wait for ASICS so I can park them on this server Cheesy
legendary
Activity: 2730
Merit: 1034
Needs more jiggawatts
Thanks, guys Smiley

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.
legendary
Activity: 1610
Merit: 1000
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. Sad

You're the man Doc.  Your efforts are appreciated by us all.
+1
sr. member
Activity: 348
Merit: 250
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. Sad

You're the man Doc.  Your efforts are appreciated by us all.
legendary
Activity: 2730
Merit: 1034
Needs more jiggawatts
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. Sad
sr. member
Activity: 348
Merit: 250
The site's down, but my miners are still running fine.
hero member
Activity: 742
Merit: 500
site down?  

nm, back up now
member
Activity: 70
Merit: 10
Who shot who in the what now?
Also, the Thps counter in the website header still says "Ghps". Wink
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. Smiley
Yay! You're cool. Smiley

~drekk~
legendary
Activity: 2730
Merit: 1034
Needs more jiggawatts
Also, the Thps counter in the website header still says "Ghps". Wink

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. Smiley
member
Activity: 70
Merit: 10
Who shot who in the what now?
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   Wink
+1 Grin

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

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.
newbie
Activity: 18
Merit: 0
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.
hero member
Activity: 742
Merit: 500
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   Wink
sr. member
Activity: 348
Merit: 250
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.
sr. member
Activity: 364
Merit: 250
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.  Smiley

No timezone, people are on a computer, they know what time it is.
legendary
Activity: 2730
Merit: 1034
Needs more jiggawatts
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.
sr. member
Activity: 364
Merit: 250
Suggestion: Add a clock to the website. Local server time.
legendary
Activity: 2730
Merit: 1034
Needs more jiggawatts
could it be compromised and we get virus?

Is this for only people using the bitminter mining client or anyone using site to check live stats etc.?

If you have Java plugin activated in your browser then a hacker could leave something on a webpage to take control of your computer if you view that webpage. It can happen to anyone using a browser with Java plugin turned on.

It's a bit annoying because Java is how BitMinter client is so easy to start, just clicking on a webpage. If you turn off Java in the browser to protect yourself from hackers then you can't start the miner that way. But as long as Java is still installed it should be possible to start it from commandline with "javaws http://bitminter.com/client/bitminter.jnlp". So you can protect yourself and still use the client.

Why are rejects so high right now?

I just restarted the mining server, that causes some rejects. Sorry about that, I try to keep it to a minimum.

Update now is faster authentication, which should speed up response a bit especially just after a restart when all users have to get re-authenticated. Also turned off rollntime for cgminer and bfgminer below version 2.7. Please upgrade to the latest version if you use one of those two miners.

Once in a while when those old miners start DDoSing the server some miners experience response times up to 30 seconds. It is worst in the "slow response queue", so those miners are mostly DoSing each other. But hopefully this update will help reduce the problem.
Jump to: