views:

183

answers:

2

Hi,

I am currently hosting a low-volume WSS 3.0 application on a virtual server for a client, and soon will be creating a few more sites for different customers. Each customer will only average around 50 users total, no more than a few at a time.

Are there any issues with hosting all of these on the same virtual box? Each would be a separate web application with a separate IP address. Clients are unrelated and shouldn't have any idea that they're on the same machine.

Thanks!

+4  A: 

I would suggest you to TEST this scenario carefully before implementing it, in order to detect which resource bottlenecks (WFE CPU, BE CPU, etc) and do a good capacity planning. I would try to answer questions like

  • Understand your content: is content more static or dynamic, which determines is caching characteristics?
  • What's the pattern of resource consumption? Is WFE- or DB- bound? Disk or CPU?
  • Mostly Read, Write, or a combination?
  • Expected RPS, # of transactions/sec?

Answers to these questions will give you ideas of how to scale your deployment. For ex. if you are WFE-bound (i.e. high CPU/disk consumption in the WFE server(s)) then you may be able to e.g. add more virtual WFE servers to increase the load on the DB.

Also, I'm assuming you are not in a standalone deployment (i.e. WFE and DB in same box), because that won't scale.

And last advice - when in doubt, add RAM. It pays back more than anything else you can add to the system, more than CPU and disk.

Ariel
Small addition to the solid information supplied by Ariel: if custom code is in-play, understand where boundaries do and don't exist. For instance, placing each site collection in a separate web application is a good isolation step, but you may need to go further and ensure that each web application is in its own (IIS) application pool for process-level isolation if custom code could bring the worker process down or force restarts. Just a watch-out :-)
Sean McDonough
A: 

There's also a Sharepoint specific sizing tool - one from Dell and another from HP. You can try those out as well if scaling/bottleneck is a concern.

Also are you trying to setup the same Sharepoint application/feature on different IIS'es i.e. Web Apps? Will SP allow possibly different versions of the same app on a SP farm?