Server Fault is a question and answer site for system and network administrators. Join them; it only takes a minute:

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

I work as a Solution Architect, and I'd like to get some support in sizing hardware for (mainly) bespoke applications (some COTS as well).

The recommended sizing for any given project is usually done by someone else, but I'd like to be able to verify the sizings myself (sometimes the sizings are from vendors); or be able to provide a ball-park sizing when "kite flying" new ideas.

Ideally I'd like a tool (exe or website is fine) that I could plug various parameters into and get a rough answer. Alternatively, any guidance on how to "manually" come up with a decent sizing.

Bonus points for useful info that takes virtualisation into account.

I know to do this isn't trival.


locked by HopelessN00b Jan 22 '15 at 6:50

This question exists because it has historical significance, but it is not considered a good, on-topic question for this site, so please do not use it as evidence that you can ask similar questions here. This question and its answers are frozen and cannot be changed. More info: help center.

closed as off-topic by HopelessN00b Jan 22 '15 at 6:50

This question appears to be off-topic. The users who voted to close gave this specific reason:

If this question can be reworded to fit the rules in the help center, please edit the question.

up vote 0 down vote accepted

As you've most likely discovered, Google will have all sorts of suggestions on sizing tools for whatever type of application/server/storage/etc you're looking at. Most ever vendor (whether hardware or software) has some sort of estimation application you can use. Sure, given good information, they may be able to get you into the ballpark as far as how much hardware you'll need. In order to get closer than that, though, you just need to rely on experience and a "sixth sense" that comes with working in the infrastructure business.

tl;dr: While hardware sizing apps may get you a very rough estimate of the needs of a certain app, there are far too many variables to consider. Raw experience and intuition are needed to go the last mile.

Thanks - I guess I'm a bit screwed then, I definatley don't have the sixth sense as far as sizing goes! I come from a software development background not an infrastructure one. I assume I just need to spend lots of time on projects - and pay special attention to sizing discussions, etc. – Adrian K Jun 29 '10 at 0:47
Yeah, it is more of a black art than a science. The number of variables are huge. We had one home grown app that went live with what was thought to be 25% overage of needed hardware. It was nowhere near enough. We doubled the CPU/memory and it still was not enough. We doubled them again, and it was then OK. 6 months later the developers realized their build script still had all the debugging code live. When this got turned off, we were able to remove 2/3 to 3/4 of the hardware. Good luck. – Kevin K Jun 29 '10 at 1:34

Not the answer you're looking for? Browse other questions tagged or ask your own question.