Avoid validating the JsonPatchDocument itself (AFAIK this is not required as an end user is not going to validate it but should be validating his model....that said validating the model while patching is an open question currently as we do not validate the model)
For the following typical
replace
operationBefore:
After: After making the following couple of changes, I see a 30% reduction in memory usage
JsonPatchDocument
itself (AFAIK this is not required as an end user is not going to validate it but should be validating his model....that said validating the model while patching is an open question currently as we do not validate the model)