question-mark
Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

functions runtime slow to start after change deteceted

See original GitHub issue

After making a change to a file, the functions runtime is slow to restart.

Repro steps

Provide the steps required to reproduce the problem

  1. Install the functions runtime as part of an Azure Web App

  2. Make a change to a file

Expected behavior

I’d expect that the runtime would go from starting to running relatively quickly.

Actual behavior

It’s sometimes absurdly slow (15-20min), even when changing a single file.

Related information

I’m running functions written in Node on Functions 1.0.10690. I see this issue mainly if I need to debug and make a quick change through FTP. When I deploy using my CI server, which uses Web Deploy, this seems to happen less often.

I also tend to see this error in my logs during this change from starting to pending:

Failed to copy job files: System.Threading.ThreadAbortException: Thread was being aborted.
   at Kudu.Core.Infrastructure.OperationManager.Attempt[T](Func`1 action, Int32 retries, Int32 delayBeforeRetry, Func`2 shouldRetry)
   at Kudu.Core.Infrastructure.OperationManager.Attempt(Action action, Int32 retries, Int32 delayBeforeRetry)
   at Kudu.Core.Jobs.BaseJobRunner.CacheJobBinaries(JobBase job, IJobLogger logger)

Issue Analytics

  • State:closed
  • Created 7 years ago
  • Comments:12 (5 by maintainers)

github_iconTop GitHub Comments

1reaction
mathewccommented, Feb 3, 2017

I’ve updated the install step wiki with a note about this as well.

1reaction
jamesdixoncommented, Feb 3, 2017

@mathewc that appears to have worked perfectly! My jobs do have a number of NPM dependencies, so that would explain things.

I appreciate your help!

Cheers.

Read more comments on GitHub >

github_iconTop Results From Across the Web

Azure Function App is very slow, but only sometimes
AFAIK in Azure Functions,. After 5 minutes of inactivity, Function App goes to the cold state. To come out of it, 10 seconds...
Read more >
Improve the performance and reliability of Azure Functions
This article provides guidance to improve the performance and reliability of your serverless function apps. For a more general set of Azure ...
Read more >
How we improved the performance of our Azure functions with ...
Another way to improve the cold start time is to reduce the number of cold starts that occur. One way to do this...
Read more >
Cold Starts in Azure Functions
PowerShell functions are especially slow to start with values from 4 to 27 seconds. View detailed distributions: Cold Start Duration per ...
Read more >
Optimize Angular's change detection - web.dev
When facing runtime slowdowns in an Angular app: Profile the application with Chrome DevTools to see where the slowdowns are coming from.
Read more >

github_iconTop Related Medium Post

No results found

github_iconTop Related StackOverflow Question

No results found

github_iconTroubleshoot Live Code

Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free

github_iconTop Related Reddit Thread

No results found

github_iconTop Related Hackernoon Post

No results found

github_iconTop Related Tweet

No results found

github_iconTop Related Dev.to Post

No results found

github_iconTop Related Hashnode Post

No results found