Netflix/p2plab
Logical Components
An overview of source code logical components.

Logical Decomposition #1: PRIMARY

The decompositions is based on the folder structure at level 1 (relative to the source code root).

Bubble Chart | Tree Map
Component Sizes (Lines of Code)
The "primary" logical decomposition has 25 components.

metadata2380 LOC (19%) 12 files
cmd2324 LOC (19%) 22 files
labd2034 LOC (16%) 17 files
pkg599 LOC (4%) 14 files
providers570 LOC (4%) 5 files
transformers479 LOC (3%) 4 files
labagent407 LOC (3%) 5 files
peer406 LOC (3%) 2 files
printer374 LOC (3%) 6 files
nodes319 LOC (2%) 5 files
ROOT311 LOC (2%) 11 files
query310 LOC (2%) 4 files
scenarios287 LOC (2%) 3 files
labapp278 LOC (2%) 3 files
uploaders194 LOC (1%) 3 files
daemon186 LOC (1%) 4 files
cue172 LOC (1%) 3 files
builder172 LOC (1%) 1 file
downloaders159 LOC (1%) 4 files
experiments68 LOC (<1%) 2 files
dag47 LOC (<1%) 1 file
reports45 LOC (<1%) 1 file
actions27 LOC (<1%) 1 file
errdefs26 LOC (<1%) 1 file
version6 LOC (<1%) 1 file

scope details...
  • 135 files, 12,180 LOC (100.0% vs. main code).
Component Commits
Components ordered by number of commits
Total Commits per Component
All commits, some commits may include files from multiple components.
cmd64 commits (41%)
labd58 commits (37%)
metadata47 commits (30%)
ROOT47 commits (30%)
labapp39 commits (25%)
nodes37 commits (23%)
labagent35 commits (22%)
scenarios32 commits (20%)
providers25 commits (16%)
peer21 commits (13%)
pkg20 commits (12%)
transformers19 commits (12%)
printer14 commits (8%)
query10 commits (6%)
daemon9 commits (5%)
builder7 commits (4%)
uploaders7 commits (4%)
dag5 commits (3%)
downloaders5 commits (3%)
errdefs4 commits (2%)
reports3 commits (1%)
actions3 commits (1%)
experiments2 commits (1%)
cue2 commits (1%)
version1 commits (<1%)
Yearly File Updates Trend per Components
The number of file changes in commits
animated commit history: all time cumulative | 12 months window
2026 2025 2024 2023 2022 2021 2020 2019
reports
3
metadata
4
43
ROOT
4
43
labd
3
55
experiments
1
1
scenarios
32
dag
5
pkg
1
19
downloaders
5
peer
2
19
builder
1
6
uploaders
7
errdefs
4
transformers
2
17
labapp
2
37
labagent
1
34
query
10
printer
1
13
version
1
daemon
9
cue
2
nodes
2
35
cmd
2
62
actions
3
providers
1
24


Dependencies between components in same commits (past 180 days)
The number on the lines shows the number of shared commits.
See detailed temporal dependencies report...

No temporal dependencies found.

About This Analysis

Logical decomposition is a representation of the organization of the main source code, where every and each file is put in exactly one logical component.

  • A software system can have one or more logical decompositions.
  • A logical decomposition can be defined in two ways in Sokrates.
  • First approach is based on the folders structure. Components are mapped to folders at defined folder depth relative to the source code root.
  • Second approach is based on explicit definition of each component. In such explicit definitions, components are explicitly named and their files are selected based on explicitly defined path and content filters.
  • A logical decomposition is considered invalid if a file is selected into two or more components. This constraint is introduced in order to facilitate measuring of dependencies among components.
  • Files not assigned to any component are put into a special "Unclassified" component.

2026-10-07 19:11