question

ThusharaManchanayake-1496 avatar image
0 Votes"
ThusharaManchanayake-1496 asked KalyanChanumolu-MSFT commented

Resource Utilization in Database elastic pool

I have few web jobs, which run parallelly. When they run parallelly, I get time out error with below stack trace.

"Timeout expired. The timeout period elapsed prior to completion of the operation or the server is not responding."
at System.Data.SqlClient.SqlCommand. c. ExecuteDbDataReaderAsync b_122_0(Task`1 result) at System.Threading.Tasks.ContinuationResultTaskFromResultTask`2.InnerInvoke() at System.Threading.Tasks.Task. c. .cctor b_275_1(Object obj) at System.Threading.ExecutionContext.RunInternal(ExecutionContext executionContext, ContextCallback callback, Object state)

Assuming that it gets time out due to basic amount of resource allocation for elastic pool, I scaled up elastic pool from 50 to 100 eDTU and checked parallel run of web jobs. When it was running parallel jobs from 2021-06-10 11:00:00PM to 2021-06-10 11:59:59PM local time(UTC+5:30), elastic pool resource utilization and resource utilization from DB in green color as below. According to those reports it shows that while db in green color resource utilization is going 100%, at the same time total resource utilization from allocated 100eDTU is just 3%. My question is why it uses 3% resources only? There are 12 dbs in elastic pool. If it shared resources equally to each db it should be 100/12 = 8.33 at least. But according to idea behind the using of elastic pool, it should allocate more resources than that as it shares resources in between DBs.

Could someone please share any thoughts or tell reason behind that?

104695-elastic1.png

104713-elastic2.png



Thanks in advance
---Thushara---

azure-sql-database
elastic1.png (135.4 KiB)
elastic2.png (242.4 KiB)
· 1
5 |1600 characters needed characters left characters exceeded

Up to 10 attachments (including images) can be used with a maximum of 3.0 MiB each and 30.0 MiB total.

@ThusharaManchanayake-1496 Thank you for reaching out.
We cannot troubleshoot this remotely. Please contact Azure support so that an engineer can work with you and help you resolve the issue.

0 Votes 0 ·

0 Answers