Batch put () Limitations

Question

Is there a limit or performance limit for batch packages updating existing records? I have a task queue process that processes several thousand existing records. At the end of the process loop, the BooleanProperty index that is being indexed changes from False to True for all records. Are there implications for 5,000 records at a time compared to package attachment, so that 10 iterations of updates are performed 500 at a time 10? TIA -stevep

Answer 1

The batch processing API will take care of breaking up large requests, so you don’t need to do this yourself. The library manages such restrictions as the total size of the service call and the number of objects that can be placed in one call, and makes the corresponding number of calls to the service. (According to the library code, this is apparently 1 megabyte and 500 entities in one call, but your application does not have to know this, and this can change.) There is no advantage to splitting your put () calls, and you might accidentally make more service calls than necessary if you try.