Purely in the spirit of "because I can", I fired up a 244GB EC2 instance: 1MB -- 0.310421895981 seconds 10MB -- 0.317299044132 100MB -- 0.409169948101 1GB -

Purely in the spirit of "because I can", I fired up a 244GB EC2 instance: 1MB -- 0.310421895981 seconds 10MB -- 0.317299044132 100MB -- 0.409169948101 1GB -- 1.3299703002 10GB -- 10.8254830956 100GB -- 133.936514747 I noticed during the 100GB loop that the process oscillated between 100GB and 200GB, making me suspect that the 100GB string is actually being copied somewhere, which is inefficient and surely has a significant effect on the timings at larger string sizes. As such, I didn't go for a 200GB string. And just 'cause most of us don't see 200GB python processes every day: https://dl.dropboxusercontent.com/u/14571816/python%20200gb.png https://dl.dropboxusercontent.com/u/14571816/python%20200gb....