Has there been any definitive solution to this? I'm running into the exact same problem on an m1.medium, which I'd think would have enough horsepower for this. I am running WAL-E 0.6.9.
On Friday, February 21, 2014 4:27:52 PM UTC-8, Daniel Farina wrote: > > On Fri, Feb 21, 2014 at 4:21 PM, <[email protected] <javascript:>> > wrote: > > I've actually been running the most recent master > > (0fd248c9c305e7b1bca086be1e883b5d47430e99) on these instances. > > > > I agree that CPU steal on t1.micros is a likely culprit. Fortunately I'm > not > > using such a handicapped instance in production; it was just a throwaway > > test server. :) > > Welp. Maybe turning down concurrency would help (-p1 instead of -p4, > the default). But alright, I'm glad to hear you are testing the > latest release. I'm doing some of my own and then after I'm done I > think I'll call this beta (but really closer to a RC). > -- You received this message because you are subscribed to the Google Groups "wal-e" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
