Uploaded image for project: 'Blazegraph (by SYSTAP)'
  1. Blazegraph (by SYSTAP)
  2. BLZG-197 BlazeGraph release 2.1 (Scale-out GA)
  3. BLZG-246

Separate data flow from message flow in the scale-out API.

    XMLWordPrintable

    Details

      Description

      The scale-out API (com.bigdata.service.IDataService) does not impose a clear separation between message flow and data flow. This has several undesirable consequences, including: the server can not drop messages without first materializing the data payload; the server can not throttle clients by deferring materialization of the data payload; new threads are allocated for each RMI request and will remain until the message has been accepted and a Future for that operation returned to the caller; there is no provision for flow control on the data payloads; and the network representation currently uses the same coding (aka compression) as the B+Tree representation, which may be a poor trade off of time and space.

        Attachments

          Activity

            People

            Assignee:
            Unassigned Unassigned
            Reporter:
            bryanthompson bryanthompson
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

              Dates

              Created:
              Updated:
              Resolved: