How Much Memory Does a Database/File/Print/Terminal/Web Server Need?

Here are some very simple guidelines that help determine how much memory a particular server actually needs in order to perform well. Of course, these are just rules of thumb, but nevertheless they might come in handy.

  • Database servers (also domain controllers): The database should fit into physical RAM with some to spare.
  • File servers: The more, the better. Add RAM until response times under heavy load are a little faster than strictly required.
  • Print servers: Not much RAM is needed. 4 GB should be more than enough for typical systems.
  • Terminal servers (with or without Citrix): Add RAM until you cannot increase the user density any more without affecting responsiveness.
  • Web servers: All frequently accessed content should fit into physical RAM with some to spare.

Comments

Related Posts

Why Sizing for Averages is a Bad Idea

Why Sizing for Averages is a Bad Idea
When sizing a new environment it is tempting to use averages. It seems the logical thing to do. But it also guarantees a bad user experience. Example: Sizing an RDS or XenApp Farm Let’s say you’re tasked with building a new Citrix XenApp farm. Being a diligent IT person you set up a pilot: one or two machines with all the right software and settings. Then you carefully select a group of pilot users in such a way that they represent the organization’s employee types statistically correctly. Then you let them work on the new platform, ironing out bugs and such. At the end of that period, you have a great new platform. But there is one big question left: how many servers to buy?!
Logs & Metrics

Latest Posts