Virtualize JDE environments - multiple vcpu's required

[java_cat33]

We're in the process of planning 4 new JDE environments for 75 users. I have a few questions in regards to VM spec requirements for JDE application, web and and deployment servers. The JDE consultant has advised to use 2 cpus on the web, app and deployment servers.

I'd prefer not to assign multiple vcpus unless I really have to, due to the fact if the ESX server is fairly busy - scheduling time slices could cause issues while the VM waits for CPU cycles -causing performance issues etc

Has anyone deployed JDE VM's with single CPU's? Any issues? Performance?

We can obviously test this however I'm just trying to establish whether we need more resource etc before we begin.

ESX server cpu's are 3Ghz

Any feedback is appreciated.

[mcowger]

Well, given that its free to turn them into 2vCPU VMs, why not just start with 1?

--Matt

[java_cat33]

That's my approach too.

[weinstein5]

That is beauty of virtualization - add vcpus if you need them -

[lamw]

Agreed, but as of 3.x they actually switched from "strict co-scheduling" to "releaxed co-scheduling"

You definitely don't want to add more vCPU's if you don't need it and if especially when you're looking at adding 2 or 4. This article does a pretty goog job of explaining it and I've always thought that all vCPUs had to get schedule before it got it's slice else it will wait.