dotnet/orleans

[PERF] Investigate optimizations for large graphs

Open

#8,140 opened on Nov 12, 2022

View on GitHub
 (1 comment) (1 reaction) (0 assignees)C# (2,123 forks)batch import
area-performancearea-serializationenhancementhelp wanted

Repository metrics

Stars
 (10,777 stars)
PR merge metrics
 (Avg merge 2d 2h) (64 merged PRs in 30d)

Description

See this twitter thread for reference: https://twitter.com/neuecc/status/1589902671540256771?s=20&t=AcVRk8mwSdMyQJT2c5jyDg

Note: we could also consider avoiding reference tracking for types by default. There are some complexities involved, like what do you do with built-in types, eg string, byte[], List<object>. You could potentially have ref-tracking variants of the codecs or pass a reference tracking preference to the codec and have an attribute per-property to indicate a reference tracking preference.

Contributor guide

Research direction
Analyze the referenced Twitter thread and investigate potential optimization strategies for large graphs in Orleans, such as avoiding reference tracking for certain types. Consider the complexities with built in types like string, byte[], List<object> and evaluate the trade offs of ref tracking variants or per property attributes.
Tech stack
csharp
Domain
backendperformance
Issue type
Performance
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
3
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
3-5 days
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
Active
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
Mostly clear
Prerequisites
C#Orleans
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
30