On the other hand we don't know how comparable it really is because there is no "Mosso compute unit" to compare to the "EC2 compute unit" (defined @ http://aws.amazon.com/ec2/instance-types/ )
Not only the processor used and how many vcpus the VM has, but the timeslice you're given (best determined by your own experimentation). The CPU scheduler rations can have profound effects on how your application runs, we've run into some issues with this on CPU intensive physics jobs.
For example, if a "compute unit" is around 1.0 GHz, it's not really the same thing to give you a 2.0 GHz chip scheduled on the real processor just half the time (competing with another VM), some thrashing can occur, especially when I/O is involved.
Anyhow, it all depends what you're after. For a lot of applications it makes no sense to pay for that much RAM per machine. Or in many cases it's not the CPU that's important. And so on.
Not only the processor used and how many vcpus the VM has, but the timeslice you're given (best determined by your own experimentation). The CPU scheduler rations can have profound effects on how your application runs, we've run into some issues with this on CPU intensive physics jobs.
For example, if a "compute unit" is around 1.0 GHz, it's not really the same thing to give you a 2.0 GHz chip scheduled on the real processor just half the time (competing with another VM), some thrashing can occur, especially when I/O is involved.
Anyhow, it all depends what you're after. For a lot of applications it makes no sense to pay for that much RAM per machine. Or in many cases it's not the CPU that's important. And so on.