guardian/elasticsearch-node-rotation
File Size The distribution of size of files (measured in lines of code). |
File Size Overall
- There are 21 files with 1,306 lines of code.
- 0 very long files (0 lines of code)
- 1 long files (549 lines of code)
- 0 medium size files (0 lines of code)
- 0 small files (0 lines of code)
- 20 very small files (757 lines of code)
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
File Size per Logical Decomposition
primary
Longest Files (Top 21)
| File | # lines | # units |
|---|---|---|
| 549 | - | |
| 95 | 5 | |
| 87 | 6 | |
| 65 | - | |
| 65 | 5 | |
| 58 | 1 | |
| 53 | 5 | |
| 52 | 3 | |
| 44 | 2 | |
| 31 | 1 | |
| 27 | 1 | |
| 23 | - | |
| 22 | 2 | |
| 21 | 1 | |
| 20 | - | |
| 20 | 1 | |
| 17 | 1 | |
| 15 | 1 | |
| 15 | 1 | |
| 15 | 1 | |
| 12 | 1 |
Large Files That Change Often (Top 12)
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 |
|---|---|---|---|---|---|
| 549 | ~3k–10k | 5 | ~20 | ~20 | |
| 95 | ~500–1.5k | 3 | ~50 | ~2 | |
| 58 | ~300–1k | 4 | ~20 | ~2 | |
| 87 | ~500–1.5k | 2 | ~20 | ~5 | |
| 52 | ~300–1k | 3 | ~10 | ~5 | |
| 44 | under 1k | 3 | ~10 | ~3 | |
| 20 | under 1k | 2 | ~7 | ~2 | |
| 31 | under 1k | 1 | ~30 | ~1 | |
| 27 | under 1k | 1 | ~20 | ~2 | |
| 23 | under 1k | 1 | ~10 | ~2 | |
| 21 | under 1k | 1 | ~15 | ~2 | |
| 20 | under 1k | 1 | ~20 | ~1 |
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 17)
| File | # lines | # units |
|---|---|---|
| 87 | 6 | |
| 65 | 5 | |
| 95 | 5 | |
| 53 | 5 | |
| 52 | 3 | |
| 44 | 2 | |
| 22 | 2 | |
| 17 | 1 | |
| 15 | 1 | |
| 21 | 1 | |
| 20 | 1 | |
| 15 | 1 | |
| 27 | 1 | |
| 12 | 1 | |
| 15 | 1 | |
| 31 | 1 | |
| 58 | 1 |
Files With Long Lines (Top 8)
There are 8 files with lines longer than 120 characters. In total, there are 21 long lines.
| File | # lines | # units | # long lines |
|---|---|---|---|
| 549 | - | 8 | |
| 95 | 5 | 4 | |
| 65 | 5 | 3 | |
| 58 | 1 | 2 | |
| 44 | 2 | 1 | |
| 17 | 1 | 1 | |
| 52 | 3 | 1 | |
| 53 | 5 | 1 |
Correlations
File Size vs. Commits (all time): 21 points
|
|
549.0 | lines of code min: 12.0average: 62.19 25th percentile: 18.5 median: 27.0 75th percentile: 61.5 max: 549.0 |
|
| 0 | 115.0 | ||
|
commits (all time) min: 2.0 | average: 21.48 | 25th percentile: 10.0 | median: 18.0 | 75th percentile: 25.0 | max: 115.0
|
|||
File Size vs. Contributors (all time): 21 points
|
|
549.0 | lines of code min: 12.0average: 62.19 25th percentile: 18.5 median: 27.0 75th percentile: 61.5 max: 549.0 |
|
| 0 | 16.0 | ||
|
contributors (all time) min: 1.0 | average: 6.57 | 25th percentile: 4.5 | median: 6.0 | 75th percentile: 8.0 | max: 16.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...
- To learn more about bloaters and how to deal with long code structures, Sokrates recommends the following resources:
- Refactoring bloaters, sourcemaking.com
- The Blob Software Development Anti-Pattern, sourcemaking.com