{"push_id":679363900,"size":1,"distinct_size":1,"ref":"refs/heads/master","head":"b1f9f0031ca92bcdf01fa6fb8f30d5d5154b9f52","before":"25cfef9d20eb0c5aa1602e01a30844a9b1b55bd4","commits":[{"sha":"b1f9f0031ca92bcdf01fa6fb8f30d5d5154b9f52","author":{"email":"31b6f693a82a5124643a54e11972ee47582d7be9@gmail.com","name":"Conrad Irwin"},"message":"Start 10 client threads. [Fixes #4]\n\nAssuming that latency to us-east from australia is about 250ms,\nposting an https payload could take up to 3s. With one thread\nthat's a maximum of 20/minute, with 10 that's 200/minute.\n\nThis is signficantly higher than the rate-limit applied inside\nthe Bugsnag data-center of 60/minute, but because the Bugsnag rate\nlimit applies only to duplicate instances of the same exception,\nit's a good idea to exceed it.\n\nAssuming that error payloads are around 60kb, which is about\nnormal for those with code inline, this change could push the\nbandwidth requirements up from 150kbps to 1.5Mbps.","distinct":true,"url":"https://api.github.com/repos/bugsnag/bugsnag-agent/commits/b1f9f0031ca92bcdf01fa6fb8f30d5d5154b9f52"}]}