Hacker News new | past | comments | ask | show | jobs | submit login

There appears to be a pretty big gap between the pricing of the WorkSpaces Windows machines and the same(?) machines purchased through EC2. For example, an m3.medium is 1 vCPU, 3.75GiB and is ~$126/mo. The Standard WorkSpaces machine is 1 vCPU, 3.75GiB and $35/mo.

Are there reasons not to move Windows workloads from EC2 to WorkSpaces?




Probably WorkSpaces is not designed to be active 24/7. Desktop CPU usages are also usually much lighter than server usages.


The windows EC2 machines are also designed for web traffic (IIS servers). I suspect these machines will still get traffic but not at the volume of a web server.


Maybe the impending EC2 price drop (predicted by many in light of the new Google cloud pricing) will bring it in line.


They just announced the new pricing [0]. It's much cheaper, but still about 2x the price of the WorkSpaces. The only difference I can see is the local storage: 4 GB SSD on EC2 vs. 50 GB on WorkSpaces. I have to assume WorkSpaces is using a spinning HDD in that case.

[0] http://aws.amazon.com/ec2/pricing/effective-april-2014/


it's probably priced assuming 40hrs/week usage, not 168hrs/week usage.




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: