Looking forward to see that in an upcoming stable release.
Especially as I discovered this, one central question is if this resource usage is related to this issue: