The T2 instance type starts consuming CPU credits when you use more vCPUs than the baseline throughput.
Therefore, even if Ghost CMS meets the minimum performance requirements, we believe that if there is a load during installation, the CPU credits will be consumed and the performance will drop to the baseline throughput.
As a result of the performance dropping to the baseline throughput, the installation takes longer, and I think I'm stuck in a loop where I try to force the installation to proceed despite the low performance and the CPU credits never recover.
Therefore, it may be a good idea to consider using an instance size with slightly higher performance when installing. https://aws.amazon.com/ec2/instance-types/?nc1=h_ls
@Riku's suggestion of uplifting the instance type is probably best, but it may be that the increase in CPU usage is a direct consequence of running short of memory - what I mean by this is that the Ghost install has pretty much exhausted the available memory, and so the CPU is working harder and harder as the kernel memory manager looks to find some chunks of memory anywhere that it can free up.
You may want to add some swap space to the system and see if this is enough to get you over this obstacle https://help.ubuntu.com/community/SwapFaq
- asked 21 days ago
- AWS OFFICIALUpdated 2 months ago
- EXPERTpublished 6 months ago