pushpool requirements

[Clipse]

I am curious if I estimate roughly 1000 active users peak on a new private pool I am planning to run with most likely pushpool, what hardware/memory requirements would you suggest?

Would prefer to get the most effective server for a 1000 users from the start rather than having to move/upgrade each time my usercount increases.

[eleuthria]

1000 users (multiple GPU/CPU each) or 1000 miners (1 GPU or CPU each)?

BTC Guild running @ 2,000 workers,  I highly recommend a solid state drive no matter what you do.  Other than that, standard server setup works quite well (Xeon, with 8 - 16 GB of RAM).  2,000 workers uses about 4 mbps up and 3 mbps down.

Take the time to optimize your database if you want any kind of realtime (or even minute delayed) statistics.  Crawling through the default sharelog on a 2m+ round to pull hash rate and share count stats is terribly inefficient.

You're also going to want to make sure you setup your linux distro to cut down on the tcp timeout to get rid of TIME_WAIT connections faster, as well as increase the file descriptor limit to 65k or more.

[Clipse]

Allright, server check.

Now the real headaches begin, but it will be worth it

[SchizophrenicX]

Oh man. I just got to the part about the server. Shed some light on the other stuff I'll need to set up a private pool please.... -.-

[allinvain]

Do you really need a xeon cpu and that many gigs of RAM?

[error]

Do you really need a xeon cpu and that many gigs of RAM?

If your pool gets big, you'll need more than that.

[SchizophrenicX]

So more servers? or is there no limit to upgrading the servers? hmm... Never dealt with servers before...

[NetTecture]

So more servers? or is there no limit to upgrading the servers? hmm... Never dealt with servers before...

The best ou can get round now has about 24 cores Without taxing it - after that it gets expensive. But by then your pool can split into different areas - no sense to have all workers use the same daemon.