0

We have Azure-based SQL server in the elastic pool and our application is connected to it. Today, I deployed my .net core Web API on my personal desktop (not even on the server) and response time and CPU usage I can see is much better. When the same application I deployed on Azure server (App service), I saw huge utilization of CPU even 100% for some request. I am a little curious why this is happening? even when we have database server on azure only in both the case. Is there anything wrong which I am doing.

P.S: each request have a bulky operation (inserting 100k records or comparing thousands of spatial points)

James Z
  • 12,209
  • 10
  • 24
  • 44
Dnyaneshwar123456
  • 70
  • 12
  • Probably locally you have few cores lots of memory, but when you deploy to azure you can have 1 or 2 cores. I would say the problem is somewhere in the code. Without context its like look in coffee and try to predict future :) – Vova Bilyachat Apr 17 '19 at 02:44
  • In addition because of cold start first request will use lots of cpu. and so on – Vova Bilyachat Apr 17 '19 at 02:45
  • I am new to Azure.Can you please help me to check from where I can check the number of cores for Azure server – Dnyaneshwar123456 Apr 17 '19 at 06:00
  • In pricing model it should say how much memory and how many cores – Vova Bilyachat Apr 17 '19 at 06:01
  • Now getting an error "Elastic pool limit is set to 100 and has been reached" with just 11 continuous users for my GPS tracking app. Any help, please my client will kill me otherwise – Dnyaneshwar123456 Apr 21 '19 at 02:38

0 Answers0