Someone from the Elastic side might be able to provide some more insight here, but I suspect this "additional" resource overhead comes in 2 forms:
- As mentioned the Elastic Agent is really just a wrapper for Beats, so it will probably just have some more overhead to "exist".
- Some of this might be Golang garbage collection related. If Go doesn't "need" to clean up unused stuff it could just let it stay there, making it seem like it needs more resources then it really does.
If I had to guess, it's probably a mixture of both of the above.