• Share
  • Email
  • Embed
  • Like
  • Save
  • Private Content
Cloud Storage Cross Test
 

Cloud Storage Cross Test

on

  • 1,002 views

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

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

Statistics

Views

Total Views
1,002
Views on SlideShare
1,002
Embed Views
0

Actions

Likes
0
Downloads
0
Comments
0

0 Embeds 0

No embeds

Accessibility

Categories

Upload Details

Uploaded via as Microsoft PowerPoint

Usage Rights

© All Rights Reserved

Report content

Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
  • Full Name Full Name Comment goes here.
    Are you sure you want to
    Your message goes here
    Processing…
Post Comment
Edit your comment

    Cloud Storage Cross Test Cloud Storage Cross Test Presentation Transcript

    • Initial Cloud Upload Tests
      Randomly-generated files 50 tests per data point
    • Overview
      These data represent the initial results from a file upload test to both Amazon’s S3 and Azure’s Blob storage
      There are three sources:
      Work via the standard proxy
      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
      Home – a standard Comcast home Internet connection as a reference for “standard” connectivity.
      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)
    • It is interesting to note that at this file size, not only is Azure faster, it also appears to have
      a smaller variation in transfer speeds
    • Particularly interesting is the amount of affect that the proxy server has on the Azure
      traffic – specifically in relation to the affect on Amazon traffic.
    • With the proxy server removed and as the file size grows, the level of variation seems
      to decrease.
    • Continued indication of a specific hit on the Azure platform by the proxy server
    • This is the first size, at which (for the non-proxied work network) Amazon’s transfer
      rate is higher than Azure’s. This is a trend that continues as the sizes grow.
    • The delta b/t the non-proxied work network transfer rate for Amazon and Azure continues
      to grow.
    • This is the first chart that shows a trend that emerges as the file sizes get larger – the
      transfer rate for Amazon is consistently higher, but so is the variability.
    • In this case, you see that the variability in the rate for Amazon makes it less interesting due
      to the fact that even though the average is better than Azure, the upper bound of the first
      standard deviation is significantly worse than the same for Azure.
    • Similar to the case for the 50MB size. The average for Amazon is higher, but the variation
      band is significantly broader.
    • As you can see, the proxy server has a dramatic effect, especially as the file size gets larger.
      Note that I was unable to collect data from larger file sizes due to constant timeouts due
      to the interference of the proxy server.
    • I don’t have a good explanation for this chart. For all but the smallest file sizes are
      limited to 0.2mbs for Azure – nearly constant whereas Amazon’s traffic appears gated
      at a much higher rate (delta of nearly 1mbs)
    • This chart would make it appear that Azure itself is gating inbound traffic at around 5mbs.
      However, the increase at the 50 and 100 MB sizes pulls this into question. It might be
      interesting to see how that changes as the file size grows further.
      The S3 test had a pretty wild jump at the 5MB size, but seemed to be taming back down. It
      would be similarly interesting to see how this changes as file sizes grow.