=?Utf-8?B?Qm9yaXM=?= said:
I thought with IIS6's ability to support multiple .NET application
pools it is not going to be a problem. Also, using the local user
Its not a matter of running them. But developers need to test and do a lot of admin things - and
putting 50 *devlopers* on the same box is not something I would wnat to do.
accounts will simplify the deployment of VS (this was also recommended
by Microsoft). I'm just trying to figure out what hardware platform I
Microsoft recommended you run Visual Studio over terminal services? I know for end users it
makes a lot of sense - but for developers it rarely makes sense for developers not to have
their own machines.
Are there some other circumstances I dont know about?
processor, 4GB of RAM, 2 mirrored SCSI disks. Would like to build a
4 GB of RAM to run 50 users? I would not ask any of my developers to run on less than 1 G JUST
for their local machine. 512 is slow... I have 2G. And you are going to run 50 developers in 4 GB or
RAM?
RAID 5, not sure if budget allows to spend another $2K on the disks).
What do you think hardwarewise - will it support it?
Not in my opinion. I dont know the basic foot print of a terminal service session, but Im not sure
you'd get 50 normal users in that memory foot print. Thats 80 megabytes a piece, not including what
the system will use. Now Im sure TS will share some of that RAM and use it efficiently - but
have you ever un an XP box on 128? Its not very fast - and you want to run a developer environment
in this?
I'll be honest - I dont think it will even work. And if it does, I cannot imagine it will be anthing but
tragically slow. I could be wrong - but it just sounds very bad to me. I cant see any reason why
developers should not have their own machines, developers are not lightweight users.
--
Chad Z. Hower (a.k.a. Kudzu) -
http://www.hower.org/Kudzu/
"Programming is an art form that fights back"
Make your ASP.NET applications run faster
http://www.atozed.com/IntraWeb/