Hi Frank! Our Reddot / WSM - Server runs virtualized since ~2007. (VMWare ESX) In our environment with our projects this works very well. We got a good performance - boost when we steped from V10 to V11.
There is one different: Our database server runs on enterprise-scale physical hardware, but it is some kind of "shared service". We don´t have the database server (sql server 2008; migration to sql server 2012 planed) exclusive for WSM. We have to share the database server with a huge amount of other applications. Our system guys prefere this because they only need to care about one big unit. (In detail this are two physical server at seperate locations to ensure high availability.) This is some kind of tradeoff. If one application generates real high load on the database server the other applications suffer to some degree. So our database-admins need to monitor database-load und hunt down "bad" applications which put extraordinarily load on our database-server. Most time this works fine. If your organisation runs a virtualized environment (like VMWare ESX) the admins of this environment need to keep an eye on how much virtualized servers are put to one physical server. And look at their workloads, .... Our ESX-admins tell me CPU is no issue. The CPU of our ESX-Hosts ist almost always underutilized by a fair margin.On the memory-side it´s kind of the strategy to "overload" the physical servers. Because some of the virtualized servers only use a part of the memory they have assigned most time. Virtualization should save money so it makes sense to do this. :-) On the storage side our organisation uses a centralised storage system. Virtual harddisks provided by the storage system are assigned to the virtualized servers. I agree with you this is some kind of bottleneck. But with WSM V11 we are able to hold the pagecache most time in memory. So WSM fetches most data from memory or from the database server. A virtualized environment has some real strong aspects. Assign more memory. --> A few mouseclicks. Need a larger harddisk. --> Make your existing harddisk´s larger with a few mouseclicks. You update your WSM and need to take backups. --> Take a snapshot and you can rollback if something fails... >From my experience virtualisation is a good thing. It helps to keep costs down and offers good performance for many (not all) scenarios. Our WSM eats most resources during night when all our projects are published. At this time a good amount of our other (virtualized) system are almost idle because the people are in their spare time or they sleep. We have up to 25 conurrent authors working on our WSMS, splitted up to about 40 projects. Average workload durring working hours are about 10 or 15 concurrent authors. Do you trust in your colleagues which run your virtualized environment? Do they have enough physical hardware? If you can answers this two questions with yes --> give it a try! Kind regards, Christoph -- You received this message because you are subscribed to the Google Groups "RedDot CMS Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/reddot-cms-users. For more options, visit https://groups.google.com/groups/opt_out.
