File Complexity Overall
  • There are 34 files with units, with 3,998 lines of code.
    • 1 very complex files (McCabe index sum 251+; 1,010 lines of code)
    • 0 complex files (McCabe index sum 126-250; 0 lines of code)
    • 3 medium complex files (McCabe index sum 51-125; 774 lines of code)
    • 4 slightly complex files (McCabe index sum 26-50; 856 lines of code)
    • 26 simple files (McCabe index sum 1-25; 1,358 lines of code)
  • 23 main files have no units (e.g. languages without unit analysis, or files without functions) and are not classified.
system25% | 0% | 19% | 21% | 33%
Legend:
251+
126-250
51-125
26-50
1-25


explore: grouped by folders | grouped by complexity
File Complexity per Extension
251+
126-250
51-125
26-50
1-25
js41% | 0% | 13% | 19% | 25%
py0% | 0% | 34% | 35% | 29%
java0% | 0% | 23% | 14% | 61%
File Complexity per Logical Decomposition
primary
251+
126-250
51-125
26-50
1-25
web-ui41% | 0% | 13% | 19% | 25%
jes0% | 0% | 34% | 35% | 29%
trace-mr20% | 0% | 39% | 0% | 60%
trace-mr10% | 0% | 0% | 36% | 63%
Most Complex Files (Top 34)

The McCabe index of a file grows with its size: per 100 lines tells a large but plain file from a dense one, and most complex unit whether the complexity sits in one unit or is spread over many.

File# lines# unitsMcCabe index
(sum)
per 100
lines
most complex
unit
pager.js
in web-ui/public/lib/pager-1.0.1
1010 81 255 25 15
TraceJobHistoryLoader.java
in trace-mr2/src/main/java/com/netflix/bdp/inviso/history
207 9 63 30 32
cluster.js
in web-ui/public/js
320 27 55 17 11
handler.py
in jes/inviso
247 23 54 22 7
monitor.py
in jes/inviso
253 18 48 19 8
series.widget.js
in web-ui/public/js/charts
281 11 34 12 8
search.js
in web-ui/public/js
198 20 28 14 4
TraceJobHistoryLoader.java
in trace-mr1/src/main/java/com/netflix/bdp/inviso/history
124 7 26 21 7
stream.widget.js
in web-ui/public/js/charts
228 5 18 8 10
profile.js
in web-ui/public/js
77 7 12 16 3
workflow.widget.js
in web-ui/public/js/charts
168 6 12 7 6
TraceService.java
in trace-mr2/src/main/java/com/netflix/bdp/inviso/history
103 3 10 10 6
publish.py
in jes/inviso
28 6 9 32 3
81 5 9 11 3
TraceService.java
in trace-mr1/src/main/java/com/netflix/bdp/inviso/history
95 3 9 9 5
LogService.java
in trace-mr2/src/main/java/com/netflix/bdp/inviso/log
75 1 8 11 8
57 4 7 12 2
dateline.widget.js
in web-ui/public/js/charts
96 7 7 7 1
utils.js
in web-ui/public/js
22 3 7 32 4
WrappedCompressionInputStream.java
in trace-mr2/src/main/java/com/netflix/bdp/inviso/fs
36 7 7 19 1
WrappedCompressionInputStream.java
in trace-mr1/src/main/java/com/netflix/bdp/inviso/fs
36 7 7 19 1
jes.py
in jes
33 1 4 12 4
Job.java
in trace-mr2/src/main/java/com/netflix/bdp/inviso/history/job
23 3 4 17 2
Task.java
in trace-mr2/src/main/java/com/netflix/bdp/inviso/history/job
22 3 4 18 2
Job.java
in trace-mr1/src/main/java/com/netflix/bdp/inviso/history/job
23 3 4 17 2
Task.java
in trace-mr1/src/main/java/com/netflix/bdp/inviso/history/job
22 3 4 18 2
BucketedHistoryLocator.java
in trace-mr2/src/main/java/com/netflix/bdp/inviso/history/impl
28 3 3 11 1
S3DelegateFS.java
in trace-mr2/src/main/java/com/netflix/bdp/inviso/fs
20 3 3 15 1
BucketedHistoryLocator.java
in trace-mr1/src/main/java/com/netflix/bdp/inviso/history/impl
34 3 3 9 1
settings.js
in web-ui/public/js
25 1 2 8 2
util.py
in jes/inviso
6 1 1 17 1
aws.py
in jes/inviso
4 1 1 25 1
TaskAttempt.java
in trace-mr2/src/main/java/com/netflix/bdp/inviso/history/job
7 1 1 14 1
TaskAttempt.java
in trace-mr1/src/main/java/com/netflix/bdp/inviso/history/job
9 1 1 11 1
About This Analysis
  • File complexity is the sum of the McCabe indexes (conditional complexity) of the units (methods, functions...) in a file.
  • Files are classified in five categories based on that sum: 1-25 (simple files), 26-50 (slightly complex files), 51-125 (medium complex files), 126-250 (complex files), 251+ (very complex files). The default bands are five times the unit complexity bands, as a file is a group of units.
  • Only main code files with units are classified. Files without units (languages without unit analysis, or files without functions) have no complexity to measure and are left out rather than counted as simple.
  • A very complex file holds many decisions, which often means it has too many responsibilities: a candidate to split, and a place where changes need more testing.
Learn more...