I'm interested in how other developers are other handling 503 errors when using the email migration API. I consistently start seeing 503 errors around 650 imported messages (I'm using the C# Batch API with a batch size of 50.) If I use exponential backoff, as suggested in the Google documentation, I end up with a delay time of several minutes, which is not a viable strategy as this yields an import rate of less than 2000 messages per hour.
I've found that the best strategy is to throttle the upload rate until less than 25% of the messages return 503 errors. Shooting for zero 503 errors is not viable. It also appears that the maximum allowed upload rate has a dependency on the total number of users. When I tried to test my 503 handling over the weekend, I didn't see any 503 errors. I tried again on Monday with the same code and the errors started again. Other opinions/observations? Jim --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Google Apps APIs" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/google-apps-apis?hl=en -~----------~----~----~----~------~----~------~--~---
