High reported CPU using tedious (nodejs) after Azure SQL database switch

Question

High reported CPU using tedious (nodejs) after Azure SQL database switch

Rafał Jońca 26

Hello,

After Azure SQL database switch (because of internal upgrade of SQL engine/VM or configuration change like upgrade from S2 to S3), we observe a very big CPU spike after 3 to 10 minutes after the switch which will not go away unless we close existing connections and start new ones. Anyone observed anything similar to this using nodejs (we use 12.16.3 and tedious or node-mssql library)?

I ask here, because we can easily reproduce the issue, but we wonder why noone else is reporting this. We know that on production the maintenance switch is more or less once per month so it may not be very often but when it happens it is clearly visible, as consumed CPU jumps from 10% to 90%.

More details about the issue with example code to reproduce this can be found on https://github.com/tediousjs/tedious/issues/1136.

Best regards,

Rafal

Anonymous

2020-08-07T22:15:39.87+00:00

@Rafał Jońca

I agree with your approach in raising the support ticket as this would need access to your resources and support can do that.

Please do share the ticket number and we can keep an eye on the same and help with gaining traction as well if needed.

Thanks
Navtej S
Anonymous

2020-08-10T21:40:54.087+00:00

@Rafał Jońca
Please share the ticket number for this issue.

Thanks
Navtej S
Rafał Jońca 26 Reputation points

2020-08-11T06:33:44.653+00:00

Hello Navtej,

The ticket number is 120080725000347. The problem was reproduced in the remote session but we see that at the moment Azure is roling out new version of databae engine. We were able to reproduce the issue easily on version Microsoft SQL Azure (RTM) - 12.0.2000.8 Jun 18 2020 16:54:11, but we can't with just rolled out version Microsoft SQL Azure (RTM) - 12.0.2000.8 Jul 31 2020 08:26:29. We are still checking if high cpu won't show up.
Anonymous

2020-08-12T16:05:48.177+00:00

@Rafał Jońca Thanks for sharing the ticket number. We will follow the same for insights.
Anonymous

2020-08-17T16:24:52.77+00:00

@Rafał Jońca

As conveyed the issue is resolved for test server now by itself after the maintenance and you will wait till September to convey the resolution for the Production servers as that when the maintenance for production servers is.

Thanks
Navtej S