CompileStatic Configuration for Low‑Traffic Groovy Workloads

Assess whether applying the @CompileStatic annotation to Groovy classes in a low‑traffic service yields measurable CPU savings without breaking dynamic‑dispatch features such as methodMissing or categories.

Because the absolute runtime reduction is often small, the team must weigh the annotation maintenance cost against the potential gain, while ensuring that any class annotated does not rely on runtime metaprogramming that would become inaccessible after static compilation.

Should @CompileStatic be limited to classes that can be proven free of dynamic calls? Is a package‑level annotation sufficient to capture safety boundaries, or is per‑class granularity required? What automated analysis can help identify safe candidates for static compilation?