[THIN] Re: VMware & CPS 4.5

  • From: "TSguy92 Lan" <tsguy92@xxxxxxxxx>
  • To: thin@xxxxxxxxxxxxx
  • Date: Thu, 31 Jan 2008 10:34:23 -0800

Our current production CTX environment = MPS 4.0, Win2k3 sp2 hosts on VMware
ESX 3.5.

Our standard VM build has 2 procs, 3gb ram and we average about 45+ user
connections per host. Our environment is published app based, which lets us
spread the load around a bit better, no full desktop. Physical boxes running
VMware are HP blades, 16gb ram, 4 proc. Dependant on app load and usage, (we
silo off the heavy use stuff) your mileage may vary.

That link Greg sent has some good recommendations; from my own experience:

- the vmware tools install by default adds a component into user profiles "
hgfs.dat" which can be a pain to deal with. (greg's article covered this).
Sort out how to handle this before allowing users to login.
- Use manual DRS automation if you have a Citrix specific cluster setup in
your ESX environment. Automated DRS vmotion during production hours with
dozens of users connected can hang up a VM.

We have virtual MPS 4.5 boxes in testing, but I can't say we've put any
serious user load on them yet.

HTH

Lan



On Jan 31, 2008 7:07 AM, Kelsey, John <JCKelsey@xxxxxxxx> wrote:

>  We tried it in an ESX 2.5 environment and the performace was horrible.
> Supposedly its been greatly improved in an ESX 3 environment but we haven't
> gotten back to try it yet.
>
>
> *******************************
> *John C. Kelsey
> *DuBois Regional Medical Center
> (:  814.375.3073
> *:   jckelsey@xxxxxxxx
> *******************************
>
>  -----Original Message-----
> *From:* thin-bounce@xxxxxxxxxxxxx [mailto:thin-bounce@xxxxxxxxxxxxx] *On
> Behalf Of *Chris White
> *Sent:* Thursday, January 31, 2008 08:58
> *To:* thin@xxxxxxxxxxxxx
> *Subject:* [THIN] VMware & CPS 4.5
>
>          Hi,
>
> I've a customer who wants to run CPS 4.5 in a VMware ESX environment. This
> will be for production.
>
> Has anyone set this up in a live environment before? I've only ever set it
> up for a dev environment. Any tips or recommendations? Should I discourage
> them for doing this and use straight tin instead?
>
> Thanks for any help,
> Chris.
>
>
> *Basilica Computing Ltd *is registered in England, Registered Office
> Number 1, Avenue One, Letchworth Business Park, Letchworth Garden City,
> Hertfordshire, SG6 2HB, Company Number 2624451, VAT Number 245719348*
> Confidentiality:* This email, sent from Chris.White@xxxxxxxxxxxxxx to
> thin@xxxxxxxxxxxxx on Thu Jan 31 14:01:51 2008 , is confidential and may
> contain privileged or copyright information. You may not present this
> message to another party without consent from the sender. If you are not
> thin@xxxxxxxxxxxxx please notify Chris.White@xxxxxxxxxxxxxx and delete
> this email and you are notified that disclosing, copying, distributing or
> taking any action in reliance on the contents of this information is
> strictly prohibited. *2) Liability:* This email is not a binding agreement
> and does not conclude an agreement without the express confirmation by the
> sender's superior or a director of the Company. *3) Viruses: *The Company
> does not certify that this email is free of viruses or defects. *4)
> Requested:* The Company does not consent to its employees sending
> non-solicited emails which contravene the law. In the event that you feel
> this email is such, please notify the Company in order for the appropriate
> corrective action to be taken. *5) Advice: *Any views or opinions
> presented in this email are solely those of the author and do not
> necessarily represent those of the company. Any actions taken on the basis
> of this email are at the readers own risk. *6) Other: *The sender of this
> email is expressly required not make any defamatory statements. Any such
> communication is contrary to company policy and outside the scope of the
> employment of the individual concerned. The company will not accept any
> liability in respect of such communication, and the employee responsible
> will be personally liable for any damages or other liability arising.
>
>

Other related posts: