JSON Support : Optimize writing large JSON data by sending chunks

[apoorvdeshmukh]

This issue is to track the follow-up work needed for JSON write performance optimization as suggested here in this thread.

We need to either use the convert function or Encoder instance for the optimization as suggested here and here.

[Wraith2]

I'm not sure this is a ClientX feature, it's part of the main sql client json support.

I had a thought. If every packet array that was created was just slightly larger than we really needed then we could always write directly into the packet buffer and only copy out any remainder bytes that we need to keep. It would only need+3 bytes to each packet. The downside is that this would be a constant additional cost even when users aren't using json so it isn't pay-for-play.