4 ms·
The AWS medium tested is a single core. The Azure is dual core. Context switching could account for the difference in preformance. Just because they are both l
by forgotAgain 13y ago
The AWS medium tested is a single core. The Azure is dual core. Context switching could account for the difference in preformance.
Just because they are both labeled medium doesn't mean they're comparable. The Azure is also about %50 more the AWS last time I looked..
Edit: I was wrong about the pricing. They are similarly priced.
- MBCook 13y agoThey both cost $0.12/hour unreserved, so it's a fair comparison if you are thinking performance per dollar.
- forgotAgain 13y agohttp://www.windowsazure.com/en-us/pricing/details/virtual-machines/ http://www.windowsazure.com/en-us/pricing/details/virtual-ma... Azure is listed at $0.18/hour. Edit: My mistake. Windows is $0.18/hour, Linux is $0.12. Edit2: Now that's interesting, Microsoft charges more for a Windows VM.
- felixrieseberg 13y agoIt's an honest approach: Windows VMs include a license.
- velodrome 13y agoPerformance/dollar: Azure wins - 3.1:1 on demand Azure wins - 3:1 on 1 year reserved (author is incorrect here - does not account for initial reserve payment) Less noisy neighbors? I am not sure. Seems like a good deal though.
- ihsw 13y ago> The AWS medium tested is a single core. The Azure is dual core. Context switching could account for the difference in preformance. Redis is mostly single-threaded. http://redis.io/topics/latency http://redis.io/topics/latency
- dvirsky 13y agothe benchmark still has to run somewhere :) and it takes up CPU as well. running both the server and benchmark on one CPU reduces performance dramatically. On a 2 core EC2 machine the results are much closer. However if you ran the benchmark from a remote node, you can really compare apples to apples. But given that they both cost more or less the same, having one CPU still sucks just the same.
- gingerlime 13y agohttp://redis.io/topics/latency http://redis.io/topics/latency : Redis is mostly single threaded since actually from Redis 2.4 we use threads in Redis in order to perform some slow I/O operations in the background, mainly related to disk I/O Could this affect the benchmarks then? I don't know if it does, but if the benchmark is also writing to disk, wouldn't a dual core machine perform better?