TimelyDataflow / TimelyDataflow/differential-dataflow

Specialize Spine for default times

Open
#35 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
Rust
Stars
3k
Forks
211
Avg merge
10h 42m
Merged PRs (30d)
34

Description

The current Spine implementation tracks a list of batches, each of which can hold arbitrary updates. At the same time, we often see the bulk of updates are at times in the past which are equivalent to <T as Lattice>::min(), the smallest possible time. These "updates" are essentially describing the current dataset.

The set of updates with times equivalent to the smallest possible time have a few important properties:

  1. They all have the effectively the same time. We can remove the (large) time field from the updates, economizing on storage.

  2. They accumulate up to positive counts, when the ring is the integers. In this case, we can use the multiplicity of the record to indicate the diff field.

These two optimizations, the first making lots of sense and the second being useful for some data, bring the in-memory size for graph collections down to pretty close to the adjacency list representation.

To implement such a specialized spine, we need to extract the appropriate updates from the general batches, as we cannot accommodate more general updates. This means we need to write some specialized merging, and take some care when we do it.

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by locating the Spine implementation and its general batch-merging path; the issue provides no file or test names. Trace how default-time updates can be extracted and merged separately. Done means a specialized spine handles these updates while preserving the stated storage and multiplicity optimizations.

Written by the indexing model from the issue text.

Assessment

Tech stack
rust
Domain
data-engineering
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
30/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.