We have problems deploying Sitecore update packages to our servers. Using Sitecore Update package wizard in a local machine to deploy master update package takes about 70-90 seconds, but in the development server, it takes 7 minutes at least, and in the production server, it could take more than 10 minutes getting a timeout sometimes.
We are concerned about so huge difference in time between our local machines and our servers, in consequence our deploy times take more time than desired, and we would like to reduce it.
Our Update package is small, it contains about 2200 items, its size is 5500 kb. We don't have large media items.
Our development/production servers are in Azure as a virtual machine and we use Azure Sql Database. We have been monitoring them while deploying update package and all resources are far from max capacity, CPU of VM is always under 30%, it has a lot of free RAM, hard disk I/O are low, network is low too and database DTU is around 20%. Our current Sitecore Version is 8.0 rev 1 50621
Any idea why is take so much time to deploy the update packages in our servers? Someone using azure as infrastructure has faster update packages than us?
We've been done several tests in azure, with different service tiers. We have tested With S2, S3, and P4 Azure Sql database and there is no difference in time between them.
Our DB Team has checked Database all it seems Ok, monitoring it they have seen that Sitecore opens two connections to Database and most of the time while Sitecore is doing deployment they are in awaiting command. As I said the VM is not out of resources. We have calculated that for our update package deploy Sitecore performs about 200.000 operations to Database (insert, deletes, updates,..).
We are starting to think about network latency problems, doing so many operations to the database if latency is not very low could take some time.