Performance benefits of API chaining
Not sure about the internals of how chaining works in API 4 but wondering if there is a performance benefit to it, or just a syntactical one.
Personally, I have never got into API chaining, and I think that there is a benefit to the clarity of doing a get and then and update (for example).
But if there is a performance gain that might change my mind in some instances.
Maybe it is more of an issue when using Ajax and considering round trips to the server?
I'm adding this as the documentation issue, since I think it is worth adding the answer to https://docs.civicrm.org/dev/en/latest/api/v4/chaining/.
But I think it is worth a quick discussion before doing so.
@colemanw - can you help answer this question?