Most reliable way to test uploading a 5GB object.

Upload it on a network local to the cluster? I'm not sure I entirely understand the question though.

On the local network, with Swift installed with default settings, I occassionally get timeouts on files several GB in size. I assume this is due to the rate limiting settings. I was thinking as S3 does an alternate mechanism for uploading large files, possibly theres more than one way with Swift. If there is only the one way, I can just look into the rate limiting settings/network.

Ah gotcha, yeah there's just the one way right now. What are the optional ways with S3? We could investigate such features for Swift.

I take this back, Amazon has a service for S3 that lets you send in portable storage for them to manually load. Sorry for the confusion, and thanks for your help.

epochasset: Did you figure out the proper rate limiting settings?

Internal tests seemed to have enough bandwidth to where it wasnt a problem. When I ran tests from a remote office I believe their usage caused it.

I'm uploading to the localhost and getting this error (only 1 node in this zone, maybe that's a problem).
What setting should I change?

The example config appears to have ratelimiting off. But I also think the ratelimiting is by request, so a single operation is likely unaffected. At that point I would wonder what storage you are using, what size object times out in write, and how long it takes before failure.