VMware Horizon Community
jasonngteck
Contributor
Contributor
Jump to solution

Merge tvr file on second launch

I understand that the sandbox should help cache files for the ThinApps. I am noticing that on relaunch of the application, it is reloading the merge virtual registry file. Is there any way to configure and change this behavior? Basically due to the reloading of the merge registry file, there's a bit of a delay in launching the application. Relaunch of the application results in about the same loading time as a fresh new sandbox. Thanks.

Reply
0 Kudos
1 Solution

Accepted Solutions
pbjork
VMware Employee
VMware Employee
Jump to solution

The merge file is used for our AppLink functionality. We have to merge the AppLink package's environment on every launch or we couldn’t pick up changes made to the AppLink package.

Some child packages (AppLink packages) forces a large Merge file to be created. This can slow down the launch time, as you are experiencing. There is no workaround other than stop AppLink the child package and incorporate the bits into your main package.

Most of the times we don’t see large Merge files but IE is one bad candidate for being a child package. An indication can be to look at the virtual registry files in your project folder. I have not investigated it very deep but I suspect a large virtual registry causes a large Merge file.

Now when I think about it, sometimes there is a lot of rubbish captured in the registry. Try cleaning up the registry to see if that helps. The tool ThinAppHelper can be of assistance here. It lists the virtual registry in a nice tree view.

View solution in original post

Reply
0 Kudos
3 Replies
pbjork
VMware Employee
VMware Employee
Jump to solution

The merge file is used for our AppLink functionality. We have to merge the AppLink package's environment on every launch or we couldn’t pick up changes made to the AppLink package.

Some child packages (AppLink packages) forces a large Merge file to be created. This can slow down the launch time, as you are experiencing. There is no workaround other than stop AppLink the child package and incorporate the bits into your main package.

Most of the times we don’t see large Merge files but IE is one bad candidate for being a child package. An indication can be to look at the virtual registry files in your project folder. I have not investigated it very deep but I suspect a large virtual registry causes a large Merge file.

Now when I think about it, sometimes there is a lot of rubbish captured in the registry. Try cleaning up the registry to see if that helps. The tool ThinAppHelper can be of assistance here. It lists the virtual registry in a nice tree view.

Reply
0 Kudos
Cievo
Commander
Commander
Jump to solution

Are your virtual registries huge? What about count of items in virutal filesystem?

***Good question is half of the answer...***
jasonngteck
Contributor
Contributor
Jump to solution

Thanks for the information. Since this application requires several child packages including IE, that explains the size of the merge file (approximately 37MB - IE takes about 16MB with plugins).

I will have to go through and see if there are items that can be cleaned via the registry. One plugin I noticed that has a pretty large registry is Shockwave. I've repackaged this a few times, but it makes a lot of registry changes.

Reply
0 Kudos