This message was deleted.

From the code base what i have found as of now is that it runs a go routine for every plan/apply command to make main thread available for other requests, this is what i think is making it more CPU intensive + the check performed inside atlantis also.

Not at this time, the maintainer team is focusing on addressing bug regressions and issues with locking during Clones. PRs are welcome if you notice unoptimized code.

there has been some optimizations done by the community but very little