aws-samples / monitor-java-gc-on-aws-lambda
With this solution you collect JVM garbage collector activity of your AWS Lambda functions. You can visualize out-of-memory situations in a Kibana dashboard and gain insights into your application???s memory consumption for troubleshooting and optimization.
Summary
   |
|||
| Main Code: 504 LOC (4 files) = JS (60%) + TS (29%) + PY (10%) Secondary code: Test: 20 LOC (1); Generated: 14,747 LOC (2); Build & Deploy: 16 LOC (2); Other: 15,014 LOC (11); |
|||
| File Size: 0% long (>1000 LOC), 56% short (<= 200 LOC) | |||
| Unit Size: 31% long (>100 LOC), 16% short (<= 10 LOC) | |||
| Conditional Complexity: 0% complex (McCabe index > 50), 82% simple (McCabe index <= 5) | |||
|
|
Logical Component Decomposition: primary (4 components) | ||
|
|
1 year, 4 months old
|
||
|
|
0% of code updated more than 50 times Also see temporal dependencies for files frequently changed in same commits. |
||
| Goals: Keep the system simple and easy to change (4) | |||
Latest commit date: 2021-09-17
|
0
commits
(30 days)
0
contributors
(30 days) |
|