TimelyDataflow / TimelyDataflow/differential-dataflow
Memory allocation in Differential Dataflow
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 3k
- Forks
- 211
- Avg merge
- 10h 42m
- Merged PRs (30d)
- 34
Description
Hi, I am new to dataflow
I am having some trouble with a memory usage of and partitioning methods in differential dataflow.
-
when the new record is inserted/deleted, it should be inserted into the collection trace for the corresponding table. It requires the memory allocation.
Is the dataflow using a specific memory manager? or using the rust built-in memory allocator? -
when running the differential dataflow in a distributed setting, how are the records in each collection partitioned across the machines?
I appreciate your help :D
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
The issue contains questions about memory allocation for collection traces and record partitioning across machines, but names no files, tests, or entry points. Start by locating the documentation or implementation that explains Rust allocation and distributed partitioning; the issue is complete when both questions have authoritative, project-specific answers.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- distributed-systems
- Issue type
- Documentation
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 15/100