blazor – Azure SQL Elastic Pool Scalability Problem

I am a consultant on a project that has an elastic pool for multiple databases. Right now the pool is using Standard pricing with 100 DTUs. We are experiencing a lot of issues with the Sql client and timeouts. I’ve attached a picture of the resource utilization over the past seven days.

This is a Blazor Server application that uses EF Core and distributed SQL Server cache.

We have three databases in this pool. One is the distributed cache and that seems to be the one hogging the resources.

My question is what is the best method here to improve the scalability of the pool? Do we switch to the vCore pricing model or just increase the DTUs? We have major issues when ~100 people try to reach the site at the same time.