[Discussion] Remove batchSize

[dplewis]

Is your feature request related to a problem? Please describe.
A clear and concise description of what the problem is. Ex. I'm always frustrated when [...]

Features like saveAll and destroyAll uses /batch endpoint. I believe this should send a single request to the server.

Currently the /batch endpoint send multiple requests in the with the number of objects equal to batchSize (default 20). I believe batchSize was added to reduce server load during the parse.com days. Having batchSize will make result in a certain amount of overhead for your client.

batches

Describe the solution you'd like
A clear and concise description of what you want to happen.

Removing batchSize will save resources and as a bonus will allow BeforeSaveAll hooks and the like. There may be query improvements we can add on the server side as well for example Transactions.

Describe alternatives you've considered
A clear and concise description of any alternative solutions or features you've considered.

I have tried setting batch size to a large number (10000) to remove the multiple requests.

What do you think? @acinader @davimacedo

[dplewis]

I did some research, you can remove batchSize from destroyAll easily. But saveAll will have at most 2 calls to batch to prevent batch cycles.

Also the behavior of an error during saveAll would change.

Currently if I have 5 batch calls and the first one fails. The last 4 batches would never happen but all the objects in the first call will save except for the failing ones. The default behavior is to error immediately as per the docs but this isn’t true.

If batchSize is removed all objects will save except the errors. Only one error is thrown regardless of the number of failures (this is also true for the first batch in the example above).

Maybe those 2 calls could be fixed to make them 1 call but this has been there since parse was open sourced and I kinda understand it.