Topic: [~1000 GH/sec] BTC Guild - 0% Fee Pool, LP, SSL, Full Precision, and More - page 87. (Read 379078 times)

I guess I misunderstood the hide feature to begin with.  Seems as if that is how it was built from the beginning (although you make it sound like it doesn't work right now). I never hit hide, thinking it would be gone forever from the stats page.  just created a dummy did the hide button and it said i could unhide it. Can't check to see if it worked, b/c the site seems to be down (just hit a few blocks so he said it would take a while for the calculations to go through).

Now I would love to see if it were possible to wipe out a worker. Wondering if it can't be done because he may track which shares were done by which worker, thus unable to delete any workers that have done any work. Maybe the move is to rename them to z0001 and hide them at the bottom of the list.

@BitMinerN8, what are you using as your monitoring app?

Or is the main issue the TCP stack overhead, and using seven VM's is a way to 'cheat' around it ?

Sorry for PMing this to you eleuthria and posting here (just got my noob training wheels off and finally able to post elsewhere), but I wanted to see what the rest of the users thought of my ideas so you could gauge the demand for them (I think they are good, but others may not see the benefit).

Couple of feature requests/ideas:

• Definitely need a way to sort the workers alphabetically (doesn't have to be selectable, just always sorted). Now it is sorted by when you created the workers. I have mine labeled 1x1, 1x2, 1x3, 2x1, 2x2, etc where the first number is the PC number and the 2nd is the GPU number within that PC. So if I add another GPU to a pc, they arent grouped together which makes it a little difficult to see what is going on.

Let me and everyone else know if these feature could be useful to you. Maybe if enough people want them, we can ask eleuthria to see about implementing them.

Thanks for everything. love the pool.

Yes, these are all great ideas.

@Eleuthria, when you have time it would be nice if you could check into getting the hide/unhide feature working again under Manage Workers. I have clicked it and unclicked it on a miner hoping to reset it. Either way it still show up on the My Account page and API queries which my monitoring app keeps kicking out "miner down" alerts...  Thanks.

Sorry for PMing this to you eleuthria and posting here (just got my noob training wheels off and finally able to post elsewhere), but I wanted to see what the rest of the users thought of my ideas so you could gauge the demand for them (I think they are good, but others may not see the benefit).

Couple of feature requests/ideas:

• Definitely need a way to sort the workers alphabetically (doesn't have to be selectable, just always sorted). Now it is sorted by when you created the workers. I have mine labeled 1x1, 1x2, 1x3, 2x1, 2x2, etc where the first number is the PC number and the 2nd is the GPU number within that PC. So if I add another GPU to a pc, they arent grouped together which makes it a little difficult to see what is going on.
• Ability to set workers between active and inactive just for showing up in the stats and API. Example, I had a PC stop working and had to order a new PSU and it would be nice to go in and set the workers for that PC inactive until I get it back up and running. Could be as simple as a check box in the manage workers that changes from 0 to 1 and then setting the stats and API to only show workers with a status of 1...
• If you implement the active/inactive workers, it would be nice to have a way to permanently delete workers. before i came up with my numbering/naming scheme I created a few miners that I would love to just wipe out.
• why not come up with a forum for just BTC Guild members instead of relying on this one thread. I think it could be more productive, although i suspect you haven't done it because of the time required to run it

Let me and everyone else know if these feature could be useful to you. Maybe if enough people want them, we can ask eleuthria to see about implementing them.

Thanks for everything. love the pool.

The main bottlenecks for the pool are actually the TCP stack overhead in dealing with pushpool<->bitcoind traffic, as well as bitcoind which has some performance issues when getworks/second start to get very high.  New server will be running Dual Quad Xeon's, 16 or 32 GB of RAM, split into a 7 server VM system.  5x pool servers, 1 MySQL server, and one front-end load balance server to manage the internal communications.

Interesting stuff. Do you feel like sharing some info on server specs and load factors? I'd love to hear what the main bottlenecks are for a btc pool.

Would the DE server happen to be a hetzner dedicated server, btw? Great value for money, might be worth considering if that's not what you're thinking of.

NL was back up a few hours ago (didn't remember to post on this forum from work).  Problem was found and fixed.  EU (DE) and US West (#2-sort of) are being readies for being added as servers this evening.

After these new servers come up, I will not be adding any additional servers.  Leasing new servers is not sustainable and adds a lot of overhead to the My Account/API pages.  After the new US West and DE servers come up, I'm going to begin working on getting setting up a custom server solution with a single high power server, split into multiple sub-server VMs and a load balance VM to balance the connections between them.  I have been putting this off due to the high initial cost, but I can almost afford to get the hardware and begin testing.

Once I have this new setup ready and colo'd at a data center, eventually the pool will shift into "two" servers, US and EU.  They will sync up rounds just like they do now.  Each server will actually be equivalent to 4-6 of the current servers in capacity, and will be able to scale significantly better than the current setup.  This means a single server going down will get caught by the internal load balancer and the work will be redirected to a different VM.

If we hit major performance issues before this new solution is ready, I will be capping registrations until it is ready.  We should be able to handle roughly 3.5 TH/sec before that is needed.

"You generated 1.73603316 BTC in the last 24 hours."

Statisticly I should get 1.21 BTC per 24h. This means luck !! Thanks eleuthria for your great job

Damn i my cards always loose connecting and to geht them back i need to press stop minig and then start mining manualy -.-