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

Seems the server is down again... not having much luck lately! At least this has taught me to sort out a backup pool!

Hopefully it will be back up soon

DrHaribo you are such a boss. I don't think I could ever mine on any other server.

I restarted the backend and they started over blank. Only lasts a couple minutes after a restart.

what is wrong with the statistics?

Thanks Doc!
Good job. I like the way you keep us updated

Best

Disk change went well, everything back up and running again.

Remember downtime today for a disk change on the server. 12:00 UTC.

I hope the techs do a better job at it this time.

Edit: server now down to have its disk replaced.

OK, thanks DrHaribo

Yes, unfortunately. On nvidia and on older AMD drivers you'll have one CPU core doing 100% for each GPU you are mining on. If you have multiple GPUs you can reduce this problem by forcing the processes/threads onto the same CPU core. Later AMD drivers should function without this silly "busy waiting".


No, it just tries to be smart with the default settings for BFI_INT and vectors. Work size is a bit unpredictable, so I left it at 128 default for any GPU.

Mining with the BitMinter Java client on my work computer seems to use 100% of a single core to mine on my Nvidia FX 580, which only does about 6Mh/s. Just wondering if its normal to use that much CPU?

Funnily enough I get about 18Mh/s from the 8 x 2Ghz (dual quad Xeons) cores using Ufasoft CPU miner, but have to limit it to 7 cores otherwise the GPU mining with the BitMinter client drops really low.

[EDIT]
Also I'm not sure if you keep a database of what settings are best for different cards? But for the FX 580, a work item size of 64 yields much better results than 128 default.

Sounds great. Thanks for the update!

Thanks, WhitePhantom, for your input and for supporting the pool all this time.

The plan is to first add a worker/personal API with API keys, so that you can use existing third party websites and cellphone apps for supervising workers. Later I will build an email notification system into the BitMinter website.

I was thinking of making the worker API a perk that requires 0.5% donation. Currently I need 6 days without orphan blocks to get enough donations to pay for 1 orphan block. It would definitely be a good thing to get donation levels up a bit.

On the other hand, workers stopping reduces the pool hashrate, which I don't like.

Perhaps the solution is to require a donation for the API but have a primitive email notification on the website that is free. The basic stuff free and the good stuff cheap is the idea.

About monitoring individual devices on the same worker separately, I guess this could be done for any miner by detecting a lower hashrate that persists over time (not just the usual ups and downs caused by randomness). I could perhaps also build something into BitMinter client, I'll look into it.

Currently development has been delayed a bit. The server as you know has been having hardware issues, and I've also been attending the JavaZone conference.

The plan right now, in order of priority:

• Finish the new server system with full rollntime support (almost done)
• Worker API (a simple version 1)
• Variable difficulty
• Support for backup pools in BitMinter client

Hi Doc,

This pool owns, but may I request a feature that will make it so I don't suck so bad?

Feature request: On the BitMinter website, could you set it up so a worker has the option to send an E-Mail notification if the worker has been active for a certain period of time and then suddenly no shares have been received in the last X minutes?

When a notification gets sent, the system could disable any further notifications for that worker until after the server starts receiving work from it again.  Also, if the E-Mail address for each worker, or at least for notifications in general, could be customizable, that would allow for people to enter an E-Mail address that gets converted by their cell carrier to a text message.

Why I suck: Not your problem, but this feature came to mind because my mini-rigs' host PC apparently rebooted sometime last night.  It must've been RIGHT after I went to sleep.  A feature like this would've gotten my attention to fix it instead of having idle equipment for nearly 11 shifts.

This feature would even be well worth putting in the perks section...I'd definitely increase my donation level to get it.  I missed out on about 3.6 BTC from blocks that others in the pool generated (and probably more until my last 10 shifts are in good shape) and we all missed out on any blocks that I might have generated.

Again, the ability to enable this feature would be well worth placing in the donation perks section; you deserve to get something extra for it.

Related feature request: A feature that would make the notification system even more potent is if we had the option to assign workers in the BitMinter client at the device level rather the instance level.  I'd love to setup a different worker for each of my devices so if one fails, I'll know about it immediately rather than waiting to notice that my hashing power has dropped 5%.

As always, you rock and all your hard work is very appreciated.  Thank you for bringing to all of us the best mining pool in the world.

Servers are a pain in the ass, especially when they are remote ones you don't have access to! Everythings gone downhill since that lucky 18 block day! 

We are back up. I suspect there's more bad hardware on this server than the dead disk. Might have to move over to a new one later today instead of waiting for disk change tomorrow. Don't want a server that keeps locking up for no reason and with no evidence as to why.

Yes, the server went down. Doing a hardware reset to get it back to life. Shouldn't be long.

Looks like the pool is down again...

@all, thanks for the support. It was my fault. The URL was wrong. I forgot to put "http://" in front... (made a copy&paste of  "mint.bitminter.com:8332" from the account page). Now 6 of my Quads are pointed to Bitminter...

I spoke to Sonny about a card in one of my mini-rigs that fluctuates between 200MH/s and 1440MH/s (I've also tried the slower firmware; the issue remains).  He said it's almost definitely a USB issue and to try moving the USB cable for that card to a different port on the USB hub or to even try hooking it directly up to a USB port on the host computer.  When I eventually get around to doing that, I'll post back about what I found.

yea, one of my miners was kicked off, dont know what happened. all i did was look for all ports and it was found and started mining again... Also, one of my miners that is flashed to run slower than another is actually performing better than the faster one, go figure...