Revert "Serialize Json direct to Http PipeWriter" (#6369)

[benaadams]

Contributes to #6556

Changes

• Revert "Serialize Json direct to Http PipeWriter" (Serialize Json direct to Http PipeWriter #6369)

Types of changes

What types of changes does your code introduce?

• Bugfix (a non-breaking change that fixes an issue)

Testing

Requires testing

• Yes
• No

If yes, did you write tests?

• Yes
• No

[LukaszRozmej]

Can you elaborate where is the leak?

[benaadams]

Can you elaborate where is the leak?

This isn't the leak we are looking for ; as it's not a leak perse more a very large memory reservation due to the sizes of the Json responses, so it has the memory reasdy for the next very large response. It allocates less per request but hangs onto a lot of memory between requests:

[LukaszRozmej]

Can you elaborate where is the leak?

This isn't the leak we are looking for ; as it's not a leak perse more a very large memory reservation due to the sizes of the Json responses, so it has the memory reasdy for the next very large response. It allocates less per request but hangs onto a lot of memory between requests:

200MB is not the end of the world if it is pooled memory as you say so it increases performance and decreases GC. Are there any parameters to control it?

Maybe leave it as is?

[benaadams]

Will keep this as is as other source identified