What criteria should be used when deciding how to segment BulkMutateJob operations across multiple JOBS, PARTS, and OPERATION STREAMS?
After reading the BMJS overview (http://code.google.com/apis/adwords/ v2009/docs/bulkjobs.html), the limits appear to behave as follows: * CLIENTS may contain up to 10 JOBS * JOBS may contain up to 100 PARTS * JOBS may contain up to 500,000 OPERATIONS across all of its PARTS * PARTS may contain up to 25 OPERATION STREAMS * PARTS may contain up to 10,000 total OPERATIONS across all its OPERATION STREAMS * OPERATION STREAMS may contain up to 10,000 OPERATIONS So, if the above limitations are correct, are there any best practices for "when" to separate OPERATIONS across JOBS, PARTS, and OPERATION STREAMS? For example, you could segment a job with 500,000 operations in many ways, such as in the following three example: * EXAMPLE 1 (500,000 total OPERATIONS): - 1 JOB - 100 PARTS per JOB - 25 OPERATION STREAMS per PART - 200 OPERATIONS per OPERATION STREAM * EXAMPLE 2 (500,000 total OPERATIONS): - 1 JOB - 50 PARTS per JOB - 1 OPERATION STREAM per PART - 10,000 OPERATIONS per OPERATION STREAM * EXAMPLE 3 (500,000 total OPERATIONS): - 10 JOBS - 5 PARTS per JOB - 2 OPERATION STREAM per PART - 5,000 OPERATIONS per OPERATION STREAM Is there any reason why either EXAMPLE 1, EXAMPLE 2, or EXAMPLE 3 might be more appropriate for deploying the same number of operations? And again, more specifically, what criteria should be used when judging where to segment the operations? Thanks! -- =~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~ Also find us on our blog and discussion group: http://adwordsapi.blogspot.com http://groups.google.com/group/adwords-api =~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~ You received this message because you are subscribed to the Google Groups "AdWords API Forum" 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/adwords-api?hl=en
