We have maxResultSetSize setting currently which defines maximum number of documents which can be returned in a single call. If the documents are large, it can still lead to OutOfMemory errors in the crud nodeset.
I would rename current maxResultSetSize to maxResultSetCount and introduce maxResultSetSizeB (in bytes) to put a cap on the response size and protect crud resources from exhaustion.
We have maxResultSetSize setting currently which defines maximum number of documents which can be returned in a single call. If the documents are large, it can still lead to OutOfMemory errors in the crud nodeset.
I would rename current maxResultSetSize to maxResultSetCount and introduce maxResultSetSizeB (in bytes) to put a cap on the response size and protect crud resources from exhaustion.