Netflix/tcplog_dumper
File Size
The distribution of size of files (measured in lines of code).
File Size Overall
  • There are 5 files with 1,952 lines of code.
    • 1 very long files (1,668 lines of code)
    • 0 long files (0 lines of code)
    • 0 medium size files (0 lines of code)
    • 1 small files (110 lines of code)
    • 3 very small files (174 lines of code)
85% | 0% | 0% | 5% | 8%
Legend:
1001+
501-1000
201-500
101-200
1-100


explore: grouped by folders | grouped by size | sunburst | 3D view
File Size per Extension
1001+
501-1000
201-500
101-200
1-100
c87% | 0% | 0% | 5% | 7%
h0% | 0% | 0% | 0% | 100%
File Size per Logical Decomposition
primary
1001+
501-1000
201-500
101-200
1-100
ROOT85% | 0% | 0% | 5% | 8%
Longest Files (Top 5)
File# lines# units
1668 2
110 1
95 -
41 -
38 -
Large Files That Change Often (Top 5)
To change a file, an AI coding agent (or a person) has to read it: these files are read the most for the changes in the past year (lines × changes).
File# lines≈ tokens
to read		# changes
(1y)		≈ lines edited
per change		lines read per
line changed
1668 ~10k–30k 1 ~150 ~15
110 ~700–2k 1 ~3 ~30
95 ~500–1.5k 1 ~3 ~30
41 under 1k 1 ~3 ~15
38 under 1k 1 ~2 ~20

Tokens are lines × 7 to 14 (analysis.fileReadsForChanges). Lines edited per change are the file's lines added and deleted divided by its commits over the whole history. Agents read about 2,000 lines at a time: when a 17,000-line file was split into modules, the tokens an agent read for the same change fell by 83% (The Economic Benefit of Refactoring, 2026).

Files With Most Units (Top 2)
File# lines# units
1668 2
110 1
Files With Long Lines (Top 0)

There are 0 files with lines longer than 120 characters. In total, there are 0 long lines.

File# lines# units# long lines
Correlations

File Size vs. Commits (all time): 5 points

tcplog_dumper.c x: 3 commits (all time) y: 1668 lines of code tcplog_dumper.h x: 2 commits (all time) y: 38 lines of code tcplog_idcache.c x: 1 commits (all time) y: 95 lines of code tcplog_writev.c x: 1 commits (all time) y: 41 lines of code tcplog_xz.c x: 1 commits (all time) y: 110 lines of code
1668.0
lines of code
  min: 38.0
  average: 390.4
  25th percentile: 39.5
  median: 95.0
  75th percentile: 889.0
  max: 1668.0
0 3.0
commits (all time)
min: 1.0 | average: 1.6 | 25th percentile: 1.0 | median: 1.0 | 75th percentile: 2.5 | max: 3.0

File Size vs. Contributors (all time): 5 points

tcplog_dumper.c x: 2 contributors (all time) y: 1668 lines of code tcplog_dumper.h x: 2 contributors (all time) y: 38 lines of code tcplog_idcache.c x: 1 contributors (all time) y: 95 lines of code tcplog_writev.c x: 1 contributors (all time) y: 41 lines of code tcplog_xz.c x: 1 contributors (all time) y: 110 lines of code
1668.0
lines of code
  min: 38.0
  average: 390.4
  25th percentile: 39.5
  median: 95.0
  75th percentile: 889.0
  max: 1668.0
0 2.0
contributors (all time)
min: 1.0 | average: 1.4 | 25th percentile: 1.0 | median: 1.0 | 75th percentile: 2.0 | max: 2.0

File Size vs. Commits (30 days): 0 points

No data for "commits (30d)" vs. "lines of code".

File Size vs. Contributors (30 days): 0 points

No data for "contributors (30d)" vs. "lines of code".

File Size vs. Commits (90 days): 0 points

No data for "commits (90d)" vs. "lines of code".

File Size vs. Contributors (90 days): 0 points

No data for "contributors (90d)" vs. "lines of code".

About This Analysis
  • File size measurements show the distribution of size of files.
  • Files are classified in four categories based on their size (lines of code): 1-100 (very small files), 101-200 (small files), 201-500 (medium size files), 501-1000 (long files), 1001+(very long files).
  • It is a good practice to keep files small. Long files may become "bloaters", code that have increased to such gargantuan proportions that they are hard to work with.
Learn more...