Investigate long loading times

[zoey-kaiser]

Environment

No response

Reproduction

No response

Describe the bug

After deploying https://nuxt-auth-example.sidebase.io we noticed that the initial loading time is very high. This issue is to track down the reason and fix it, or add a loading indicator for when the page has not loaded yet.

Additional context

No response

Logs

No response

[BracketJohn]

I think the main reason for this is because we're using so small servers. I asked @DeusAvalon to have a look into this and scale up the instance. If the problem persists afterwards, we can investigate more, but I don't think it will.

[DeusAvalon]

Im currently in the progress of snapshotting the instance but checking the CPU metrics doesnt show any shortage of resources at all:

We havent even touched our burst capacity once in the last 2 weeks. So i wouldnt be too sure that the root cause is the instance tho. @BracketJohn

[DeusAvalon]

The instance has been moved to a twice as strong instance: 4 GB RAM, 2 vCPUs, 80 GB SSD

Based on the metrics available right now when opening https://nuxt-auth-example.sidebase.io the instance should be ridicolously overspec'd and the culprit for the longer loadtimes might not be the instance!

I also made sure to double check if any resource limitations are in place for the nuxt3-auth docker containter, which is not the case and based on docker stats the container has the full resource capabilities available.

[BracketJohn]

One important metric to look at for SSR is actually also RAM (:

The upgrade did the trick, the page is now much faster and we even got positive user feedback for it.

Closing this issue (: