M
MSmart
Guest
Hello,
The main problem description is the following: the more domains on the server the longer restore process is running. According to plesk administrator manual, restoration process makes two steps:
1. Determining possible conflicts
2. Running restore process with conflicts resolution rules and policies.
We investigated this problem and found that the first step run among others the process like this:
websrvmng.exe websrvmng.exe 20176 5.97 NT AUTHORITY\SYSTEM "C:\Program Files (x86)\Parallels\Plesk\admin\bin\websrvmng" --list-vhosts-vdirs "--vhost-names=C:\Program Files (x86)\Parallels\Plesk\PrivateTemp\tmp809.tmp" "--output-file=C:\Program Files (x86)\Parallels\Plesk\PrivateTemp\tmp20811.tmp"
It is running about 3 or 4 hours (with 650 domains currently on the server). websrvmng.exe process requires exclusive lock on IIS metabase. If in the same moment any customer makes changes in his domain hosting configuration then newly created instance of websrvmng.exe process that has to rerform this change is getting stacked in queue and waiting until that long process release the IIS metabase.
This waiting our customers evaluate as plesk slowness because their requests are not processed at the same time. And the whole restoration process of the account takes about 20 hours instead of 20 minutes on Plesk8 server.The size of such account is 50 Mb. It is very small account. It was just an example.
our environment:
Windows 2008 server R2 64 bit
Plesk 9.2.1 for Windows
it is loaded hosting server in production
Thanks
The main problem description is the following: the more domains on the server the longer restore process is running. According to plesk administrator manual, restoration process makes two steps:
1. Determining possible conflicts
2. Running restore process with conflicts resolution rules and policies.
We investigated this problem and found that the first step run among others the process like this:
websrvmng.exe websrvmng.exe 20176 5.97 NT AUTHORITY\SYSTEM "C:\Program Files (x86)\Parallels\Plesk\admin\bin\websrvmng" --list-vhosts-vdirs "--vhost-names=C:\Program Files (x86)\Parallels\Plesk\PrivateTemp\tmp809.tmp" "--output-file=C:\Program Files (x86)\Parallels\Plesk\PrivateTemp\tmp20811.tmp"
It is running about 3 or 4 hours (with 650 domains currently on the server). websrvmng.exe process requires exclusive lock on IIS metabase. If in the same moment any customer makes changes in his domain hosting configuration then newly created instance of websrvmng.exe process that has to rerform this change is getting stacked in queue and waiting until that long process release the IIS metabase.
This waiting our customers evaluate as plesk slowness because their requests are not processed at the same time. And the whole restoration process of the account takes about 20 hours instead of 20 minutes on Plesk8 server.The size of such account is 50 Mb. It is very small account. It was just an example.
our environment:
Windows 2008 server R2 64 bit
Plesk 9.2.1 for Windows
it is loaded hosting server in production
Thanks