search

projectkudu / kudu

Kudu is the engine behind git/hg deployments, WebJobs, and various other features in Azure Web Sites. It can also run outside of Azure.
Apache License 2.0
3.12k stars 653 forks source link

Kudu suddenly taking a long time to deploy to temp #1693

Closed AlanParr closed 9 years ago

AlanParr commented 9 years ago

Normally, from pushing to build complete takes about 5 minutes. In the last week or so, it is taking between 15 and 30 minutes. Initially, I thought it was because I had overridden MSBUILD_PATH to use the C#6 msbuild, however I have removed this from one site and the build still takes the same amount of time. Reviewing the Kudu trace log shows it is taking nearly 20 minutes to copy the build output to temp, the solution isn't that big so it really shouldn't take very long.

Relevant snippet of Kudu Trace:

2015-09-14T11:40:23 Copying all files to temporary location below for package/publish: 2015-09-14T11:40:23 D:\local\Temp\8d2bcf7a334374d. 2015-09-14T11:57:47 KuduSync.NET from: 'D:\local\Temp\8d2bcf7a334374d' to: 'D:\home\site\wwwroot'

ssinno28 commented 9 years ago

how exactly do I apply the fix for this? I tried adding /p:UseSharedCompilation=false as one of the paramters for msbuild in the deploy.cmd file but the deploy still takes about 20 minutes.

ssinno28 commented 9 years ago

I've also added it as an app setting through the azure web app as well as setting the msbuild version back.. still having issues with the length of the deployment.. is there anything else I should be looking for?

davidebbo commented 9 years ago

Just look at your deployment output to see if the switch is getting passed to msbuild. If it is, then you are likely dealing with an unrelated issue.

ssinno28 commented 9 years ago

is there anything else that I should be looking for? I'm not really sure where to start.. it is an Orchard project which is a pretty big solution.. do you think that could be why it is taking this long?

davidebbo commented 9 years ago

Did you verify that /p:UseSharedCompilation=false was being passed? If so, please open a separate issue with more details about your situation. e.g. how long does it take? Did it use to be faster and then something happen? Where is the time spent in your deployment log? etc...

ssinno28 commented 9 years ago

I did, okay I will open a new issue now.

etm-admin commented 8 years ago

Is this issue resolved can we get rid of the /p:UseSharedCompilation=false?

davidebbo commented 8 years ago

Yes, you should not have to pass this flag now.

pacodelacruz commented 7 years ago

Hi @davidebbo, A similar behaviour is happening on our customer environment. Kudu Extension Version is 59.51212.2600.

We've been advised by Azure Support that Site Precompilation should fix the problem. Interestingly they provided instructions for .NET 3.0?. We are deploying ASP.NET Web Apis (.NET Framework 4.5.2)

We are going to try pre-compilation, however, the customer would like to get a definitive answer from MS regarding this. Based on what you've seen, is pre-compilation the best approach? Is p:UseSharedCompilation=false still a valid approach?

Thanks,

davidebbo commented 7 years ago

@pacodelacruz that is an old issue that is no longer relevant, so my guess is that you are running into an unrelated condition.

pacodelacruz commented 7 years ago

Thanks @davidebbo. According to MS support, the problem is that vbcscompiler.exe is taking more than 60 mins to complete, and it is also occurring randomly, it does not happen on every instance. We'll update the thread if we find out the root cause.