Cloud Storage Cross Test


Published on

Initial data from tests run comparing upload rates to both Amazon's S3 and Microsoft's Azure

Published in: Technology
  • Be the first to comment

  • Be the first to like this

Cloud Storage Cross Test

  1. 1. Initial Cloud Upload Tests<br />Randomly-generated files 50 tests per data point<br />
  2. 2. Overview<br />These data represent the initial results from a file upload test to both Amazon’s S3 and Azure’s Blob storage<br />There are three sources:<br />Work via the standard proxy<br />Work with no proxy/filter in place – initial testing indicated that the proxy was negatively affecting the tests leading us to test without the proxy/filter in place<br />Home – a standard Comcast home Internet connection as a reference for “standard” connectivity.<br />In each case, there were 50 files (randomly generated) per each stated file size. Data is presented for as many ranges as were collected (test duration prevented execution of all sizes on all networks)<br />
  3. 3.
  4. 4. It is interesting to note that at this file size, not only is Azure faster, it also appears to have<br />a smaller variation in transfer speeds<br />
  5. 5. Particularly interesting is the amount of affect that the proxy server has on the Azure<br />traffic – specifically in relation to the affect on Amazon traffic.<br />
  6. 6. With the proxy server removed and as the file size grows, the level of variation seems<br />to decrease.<br />
  7. 7. Continued indication of a specific hit on the Azure platform by the proxy server<br />
  8. 8.
  9. 9.
  10. 10.
  11. 11. This is the first size, at which (for the non-proxied work network) Amazon’s transfer <br />rate is higher than Azure’s. This is a trend that continues as the sizes grow.<br />
  12. 12.
  13. 13.
  14. 14.
  15. 15.
  16. 16.
  17. 17. The delta b/t the non-proxied work network transfer rate for Amazon and Azure continues<br />to grow.<br />
  18. 18.
  19. 19.
  20. 20.
  21. 21.
  22. 22. This is the first chart that shows a trend that emerges as the file sizes get larger – the <br />transfer rate for Amazon is consistently higher, but so is the variability.<br />
  23. 23.
  24. 24. In this case, you see that the variability in the rate for Amazon makes it less interesting due<br />to the fact that even though the average is better than Azure, the upper bound of the first<br />standard deviation is significantly worse than the same for Azure.<br />
  25. 25.
  26. 26. Similar to the case for the 50MB size. The average for Amazon is higher, but the variation<br />band is significantly broader.<br />
  27. 27. As you can see, the proxy server has a dramatic effect, especially as the file size gets larger.<br />Note that I was unable to collect data from larger file sizes due to constant timeouts due <br />to the interference of the proxy server.<br />
  28. 28.
  29. 29. I don’t have a good explanation for this chart. For all but the smallest file sizes are <br />limited to 0.2mbs for Azure – nearly constant whereas Amazon’s traffic appears gated <br />at a much higher rate (delta of nearly 1mbs)<br />
  30. 30. This chart would make it appear that Azure itself is gating inbound traffic at around 5mbs.<br />However, the increase at the 50 and 100 MB sizes pulls this into question. It might be <br />interesting to see how that changes as the file size grows further.<br />The S3 test had a pretty wild jump at the 5MB size, but seemed to be taming back down. It<br />would be similarly interesting to see how this changes as file sizes grow.<br />