I have several Hyper-V VM's hosting WebConnect applications. I know that VFP does not readily handle multiple processors... and I don't think there's a way to assign instances of the same exe to a different processor.

If I have 2 instances of my WebConnect app on a Hyper-V VM, how many 'virtual' processors and how much memory should I assign to it as a starting point?

How about if I have 4 instances of the same exe?

Besides monitoring, administration and FTP, not much else is running on these VM's

I'm thinking just 2 'virtual processors' would be appropriate?

TIA for any advice.

For low loads 2 virtual CPUs is perfectly fine.

For reference, I run on Vultr with 4 CPUs and 8gb of RAM and I run all of my sites using this setup and it's barely moving the CPU needle. I run 19 sites (3 of which run Web Connection including this message board) on this configuration, a few of which are reasonably busy.

You need a minimum of 2 CPUs to ensure you don't lock up the machine, but beyond that the extra CPUs are unlikely to help much unless you have a lot of CPU load or you run a ton of simultaneous instances for your Web Connection app.

Extra CPUs are useful if:

• You have lots and lots of traffic
• You have long running requests that tie up CPUs
• You do heavy duty local data crunching (not Db access which is multi-threaded in most cases even for VFP)

+++ Rick ---