Project

General

Profile

Feature #10769

Switch data collection to use graphs

Added by Richard Neswold about 4 years ago. Updated over 1 year ago.

Status:
New
Priority:
Normal
Assignee:
-
Category:
ACSys/FE Framework
Target version:
-
Start date:
11/04/2015
Due date:
% Done:

0%

Estimated time:
Duration:

Description

In the FIRUS server codebase, data requests are represented by nodes and edges in an Erlang graph. The edges represent the FTD of the request and connect nodes which represent the requestor and the driver access point. There are several benefits to this:

  • Requests to a driver attribute occur only once per FTD -- no matter how many clients specify that attribute and FTD combination.
  • Since similar requests are automatically merged, all clients receive the exact same data and timestamp.
  • The graph data structure (in Erlang) can be queried to return all sorts of interesting formation.

Once the core has been converted, we need to run performance tests to make sure the new approach runs faster, or at least the same, as the current implementation.

History

#1 Updated by Richard Neswold over 3 years ago

  • Tracker changed from Idea to Feature
  • Project changed from 974 to Erlang Front-end Framework

Move to the proper project.

#2 Updated by Richard Neswold over 1 year ago

  • Category set to ACSys/FE Framework

Set category field.



Also available in: Atom PDF