Project

General

Profile

Feature #4027

optimize multiple PUT statements by deferring call to client until EOL or EOF

Added by Eric Faulhaber about 5 years ago. Updated about 5 years ago.

Status:
New
Priority:
Normal
Assignee:
-
Target version:
-
Start date:
Due date:
% Done:

0%

billable:
No
vendor_id:
GCD
version:

History

#1 Updated by Eric Faulhaber about 5 years ago

Many PUT statements called in rapid succession, such as for report rendering, can produce a performance bottleneck. Each statement causes a round trip to the client, including all of the DAP overhead (marshalling, unmarshalling, etc.) associated with this on both sides.

We should be able to recognize certain idioms (possibly with the help of hints?) to allow us to reduce this traffic. For instance, in a report-writing scenario, where multiple PUT statements are used to compose a line in the report, we should combine multiple payloads into a single message which is sent only when an EOL or EOF marker is encountered. If it is possible to make this communication even coarser (again, maybe through hints) to reduce this back and forth further, even better.

Also available in: Atom PDF