Slower MMPK loading performance after upgrading from ArcGIS SDK 100.13 to 100.15

[mmoosbac94]

Hello everyone,

we are currently experiencing an issue with loading MMPKs. We are using an MMPK with a file size of 335 MB, created with the latest ArcGIS Pro 3.6.0. We set up a very basic app using ArcGIS SDK 100.15, where the loading time is approximately 1.9 seconds. However, in another app created with ArcGIS SDK 100.13, the loading time is around 1.4 seconds. That prevents us from upgrading to the 100.15 SDK Version. 

Both tests were performed using exactly the same MMPK file.

Does anyone know why there is such a difference in loading time between these two SDK versions? Because with increased file size the loading time would increase a lot.

Thank you in advance for any insights.
Marvin

[Ting]

Hi Marvin, on your comment "Because with increased file size the loading time would increase a lot", do you have an example on the complexity and size of the mmpk you use?

If you can share the mmpk in question with me, that would be great. Otherwise, I'll try to create a dummy mmpk that resembles your usecase the most to better evaluate the problem.

Having talked a bit with our team, while 1.4s to 1.9s is a 35% increase in time, it might not be scaling proportionally for bigger mmpks. (e.g., It can be 5.4s vs 5.9s when the mmpk becomes larger)

So we want to understand

- if 1.9s vs 1.4s is a critical difference in your usecase, and why is it

- the typically size or complexity of the mmpk that may become the bottleneck

[mmoosbac94]

Hi Ting,

Thank you for the quick reply!

Unfortunately, I cannot share the specific MMPK with you because its content is client-side. However, it appears to be highly complex, with a size of 5 GB or even larger for a single MMPK.

The 1.9 vs 1.4 comparison I mentioned was based on a custom MMPK I created myself. I have now tested another MMPK (3.62 GB, created with ArcGIS Pro 3.6.0) using ArcGIS SDK versions 100.15.6 and 100.13.2:

• Custom MMPK (ArcGIS Pro 3.6.0 – 3.62 GB) / ArcGIS SDK 100.15.6: 6.5 seconds

• Custom MMPK (ArcGIS Pro 3.6.0 – 3.62 GB) / ArcGIS SDK 100.13.2: 4 seconds

As you can see, the loading times differ by 2.5 seconds. I imagine that with even larger MMPKs, the loading time may increase proportionally.

Our main question is: why is there such a difference between the two SDK versions? I would expect that with the newer version (100.15.6), the loading time of an MMPK would not be worse—especially when the MMPK was created with the latest ArcGIS Pro version (3.6.0).

I understand that splitting MMPKs into smaller pieces can improve loading times, but currently, the client requires a quick solution using their existing MMPK structure, so we cannot modify them.