Forum Discussion

GrahamGB's avatar
GrahamGB
Brass Contributor
Jan 24, 2024

MSIX Packaging Tool - Package Analyzer

I was using the 1.2023.1005 release of MSIX Packaging Tool after the October and November announcements and trying to experiment with the new Package Analyzer capabilities with a packaged MSIX thr...
GrahamGB's avatar
GrahamGB
Brass Contributor

Thanks for this TIMOTHY_MANGAN, having checked the event viewer over, the last entry in the AppXDeploymentServer\Operational area highlights some information that there some remaining cost associated with the Deployment Add operation on my package that potentially un-accounted for?

I have something similar to the article mentioned here.

https://techcommunity.microsoft.com/t5/msix/what-is-the-quot-gap-quot-and-how-do-i-eliminate-it/m-p/2873569#M2758

Performance summary of Deployment Add operation on Package DemoApp_3.10.0.0_x64__xxxxxxxxxxxxx:
Overall time: 12984 ms
Enqueue cost: 531 ms
Dequeue delay: 78 ms
Bundle processing cost: 0 ms
Indexing cost: 625 ms
Resolve dependency cost: 31 ms
Check approval cost: 47 ms
Evaluation cost: 985 ms
Hardlinking evaluation cost: 31 ms
Gap: 15 ms
Stage required cost: 7203 ms
Flushing and closing files cost: 0 ms
Gap: 157 ms
Machine register cost: 265 ms
Stage user data cost: 78 ms
Gap: 47 ms
Registration cost: 1313 ms
Gap: 78 ms
Repository commit transaction cost: 1047 ms
Gap: 390 ms
Data flush cost: 16 ms
Post DeStage repository commit transaction cost: 0 ms
Remaining cost: 94 ms

TIMOTHY_MANGAN's avatar
TIMOTHY_MANGAN
MVP
Jan 30, 2024
The performance information you posted looks "normal". The "Gaps" seem to be just times that the performance logging knows were spent (by looking at telemetry timestamps that are recorded) but have no specific information about how it was spent.

You would be looking for warning/error events which would indicate potential issues..
  • GrahamGB's avatar
    GrahamGB
    Brass Contributor
    Jan 30, 2024

    That's what I expected to find, although there are no errors, and the only warnings appear in AppxPackaging/Operational related to Declared namespaces which are inapplicable, and will be ignored during manifest processing.

    I have some earlier errors prior to me starting the analysis related to AppExecutionAlias directory missing, with an an error code 0x8007010B, but appears at points where I had upgraded the MSIX Packaging Tool in the disconnected environment with the latest stable release.

      • GrahamGB's avatar
        GrahamGB
        Brass Contributor
        Feb 01, 2024
        @Fizaami, i've tried closing the MSIX Packaging tool down uninstalled the MSIX package that had been installed from the Temp folder but after re-launching MSIX Packaging Tool, the Package Analyzer still cycles at the same point suggesting it hasn't finished installing.

        I have also used the "Delete all temp files and logs generated" from within the Data and Settings options before re-attempting to no-avail.

        Does the Package Analyzer rely on internet connectivity in some way? Are there any considerations for disconnected environments?

Resources