Bug 1577837 Comment 4 Edit History

Note: The actual edited comment in the bug view page will always show the original commenter’s name and original timestamp.

Original comment by
on 
When I tried default `m1.small` instances, the results for 1000 were satisfactory. So, apparently, it depends on the instance type
Provisioning: :17:41 to :17:42 (1 s). Registering: :20:42 to :28:53 (8 mins)
Revision 1 by
on 
When I tried default `m1.small` instances, the results for 1000 were more satisfactory. So, apparently, it depends on the instance type
Provisioning: :17:41 to :17:42 (1 s). Registering: :20:42 to :28:53 (8 mins)
Revision 2 by
on 
When I tried default `m1.small` instances, the results for 1000 were more satisfactory. So, apparently, it depends on the instance type
Provisioning: :17:41 to :17:42 (1 s). Registering: :20:42 to :28:53 (8 mins)
One instance was immediately terminated (`Server.InternalError: Internal error on launch`), no replacement was spun up
Revision 3 by
on 
When I tried default `m1.small` instances, the results for 1000 were more satisfactory. So, apparently, it depends on the instance type
Provisioning: :17:41 to :17:42 (1 s). Registering: :20:42 to :28:53 (8 mins)
One instance was immediately terminated (`Server.InternalError: Internal error on launch`), no replacement was spun up (`Error calling AWS API: RequestLimitExceeded: Request limit exceeded.` in the logs)

Back to Bug 1577837 Comment 4