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

"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

Website and US West were lagging badly because we found 5 blocks in about 10 minutes.  Sync'ing shares across the 6 servers, scanning the US West pool server DB for block info, running the calculations, then pushing them into the DB (while all of it is being read from API requests/users freshing block lists/my account) can cause some drastic slowdowns when the blocks are being found in rapid succession.

This is why I'm going to be spending my day tomorrow splitting the US West (pool) from the website server.

Everything (pool/website) is down?

Edit: Pool seems to be back after just 6 minutes.

Exchanges are easy.  Clearing houses are not.  The pressing need right now is not for more exchanges, but for more clearing houses.

I've thought about it many times.  It would be so easy, and it would be crazy how much I could do with an exchange that had some integrations with the pool to facilitate fast sells/buys.  After dealing with how to scale these pools, the kind of traffic an exchange would get is nothing.

However, I simply don't know what kind of legal trouble it could cause running an exchange, since I live in the US.  And there is no way I could keep working my day job (which I do enjoy, most the time) while running this pool AND an exchange.

eleuthria:

Have you thought about running a currency exchange? I hear there is an opening. 

Great work as usual! Thanks for all your work in providing the best pool out there!

EU (DE) server is now online, and is the default for 'btcguild.com', 'eu.btcguild.com', and the now inaccurate 'uk.btcguild.com'. 

A fix was made to US Central's TCP stack settings, and another fix to NL's MySQL settings which were reset after the restart this morning.  All 6 servers are now running smooth.  The website is experiencing moderate slowdown when a new block is found.  This will hopefully be resolved tomorrow when the US West pool migrates off of the webserver into a Seattle based data center.

As stated before, these are the last pool servers that will be coming online until a completely new setup is prepared and colo'd at a datacenter.  The current goal is to setup two servers, each able to support 5 VM pool servers equivalent to our current servers, with a load balancer in front of them.  One for EU, one for US.  These are also easily expandable by adding another 1U server in the same rack at significantly less cost (per month) than the current setup.

How about 2xdifficulty shares solution? Do u still consider it? More servers means harder DDOS attacks I guess.

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.

This guide is working great for my rigs. Simple and it works.
http://www.overclock.net/folding-home-guides-tutorials/384733-30-second-dummy-plug.html

Take a look at my post above.

Just use 2 miners per GPU. One on BTC Guild and one somewhere else. Using GUIminer, this is very easy to do.
This means you have to run 6 miners, but once you set it, you can forget it.

Hell, for even more redundancy, you can setup 3 miners per GPU (I do this). I never have idle time.

The problem is i am using 3 GPUs but mining under Windwos.

The dummy plugs doesnt work so i have to switch the monitors all the time :S

yea i dont babysit my miner. I have a fall over set. In GUIminer I have btcguild set with the -f 0 flag and another pool with the -f 15 flag.

If btc goes down my secondary pool goes up to near max so rarther than loosing my massive 200mhash it transfers over to another pool. when btc comes back it goes back to that.

I was going to set it to use the different btc servers ie if nl1 goes down it goes to nl2. but I think its just a little safer using someone else for backup

You can also just start phoenix a second time, and specify a lower AGGRESSION value. Of course, you should also let the second phoenix instance connect to a different pool that should be used in case the first is offline.

If you are using command line poclbm.exe (and an ATI/AMD based video card) try this:



And then run poclbm.exe again with you other pool worker sign-on info.



If you are using GUIminer (adn ATI/AMD video cards) do this:
Go to "File" menu and choose "New OpenCL miner"
A pop-up windows will appear to name the miner. You can name it what even you want. I named it "Guild."
This will create a new tab in the GUIminer window. Click on it so we can start configuring.
In the "Server dropdown box, choose "BTC Guild."
In the Username box, type in your username_workername. Fill in your password in the password box.
In the Device name, choose your GPU. If you have multiple GPUs, they will be listed in there. They are numbered starting with 0. You will also see your CPU as a usable device. (This is a hint that you can use your CPU to mine, but it will slow your system to a crawl.)
In the "Extra Flags" box you can type in:

You can tweak these numbers to try to get as many Mhash/sec as you can.
Remember to go back to the "File" menu and "Save Settings"

Now, repeat these steps again. This time using a different pool. When you get to "Device" just use the same device again.
In the "extra flags" box, just use -f60  or any higher number.

---

The main point is to use two miner per GPU. If you have 2 video cards, setup 4 miners.

If you found this helpful and feel generous, a gratuity would be appreciated at: 1JJjL5nxzBfjFjJWoviU9mzrY3fQKxJfvV

Where can i get it?

yeah.. no.
Its called a Python script, which checks and auto changes server.

Currently i am using VECTORS BFI_INT AGGRESSION=13 FASTLOOP=false WORKSIZE=256
What should i change when i set up the second worker i am using Phoenix

He means babysitting the rigs, and running double the amount of miner instances on the OS, with varying "F" factor [lower priority for the backup instances]

Because normally its not a problem and because current method of backuping sucks ass, very inefficient.