@KimcheeGUN 

Good morning

We're talking about a 1 router, 1 AP home use setup right now, so no SLA whatever involved.

From a technical standpoint there has to be a reason why the new setup uses that much more resources. We're not talking about a bit more, the difference,:

Before 5.12: 1vcpu and disk usage barely 1%

On 5.12: 3vcpus 100% and disk fully utilized.

So the difference is huge!

In the meantime I could dig a bit deeper on that issue and found out that the main problem isn't CPU here - it's actually memory.

It seems that the memory got fully used and then the kswapd0 tries to put some stuff into swap (that's where the IOPs are coming from) which kind of lead to the problems I've seen. This also explains why just increasing the vcpus didn't really help as the bottleneck stayed the same.

I re-created my docker container, restored from a backup and this time didn't enable cloud access - since then everything is working properly (memory footprint has been reduced from 0.9G to 0.8G which is just enough to work). However I don't consider that as a final solution - seems I just need more resources at the end.

So from my point of view this doesn't really seem to be an issue with the SW itself - it's just increased resource requirements. Based on the official requirements I'd call myself lucky that it's working at all with these reduced resources ;)

https://www.tp-link.com/us/support/faq/2967/