InformationThis article describes how to prepare containers with .NET Framework installed for mass cloning in order to speed up the deployment process and improve density.
Each time .NET update is installed the mscorsvw.exe performs assemblies cache optimization.
That means, if container with outdated .NET binary cache is used for mass cloning, the CLR optimization service will recompile assemblies for each cloned container after its start.
The behavior can be observed when an existing container with Parallels Plesk Panel is cloned after several .NET updates were installed on the node.
To minimize the impact of this process it is advised to prepare a sample container for cloning.
ResolutionFollow these steps to prepare a sample container for mass cloning:
Enter to a container which will be used as sample for cloning
Run cmd.exe as Administrator
Go to directory with .NET 32-bit assemblies and rebuild the cache:
cd C:\windows\Microsoft.NET\Framework\v4.0.30319\Wait until the operation is completed.
Go to directory with .NET 64-bit assemblies and rebuild the cache:
cd C:\windows\Microsoft.NET\Framework64\v4.0.30319\Wait until the operation is completed.
Now this container can be used for cloning without the need to rebuild .NET cache upon each container start.
NOTE 1: Full .NET cache rebuild will require 2-3 hours
NOTE 2: On 64-bit nodes both 32-bit and 64-bit .NET caches should be rebuilt